kaidon

Even if it all worked out, it would still be a shitty job.

It probably had an internal name like "winix" or "lindows" - but PM took the reins and came up with a much worse name, as is tradition.

Great story! I've always programmed, but went through the same nonsense in Calgary as you!

If this caught your interest, I highly recommend the Kim Justice youtube series on Molyneux.

https://www.youtube.com/watch?v=DAuvaAGnqQw

This is why we cannot have nice things!!

'trunk' should be fine. It is what I use to refer to the main/master branch when speaking in SCM-agnostic terms.

Maybe a bit tangential, but still interestin:

https://cacm.acm.org/magazines/2010/2/69354-a-few-billion-li...

live and let live

I usually just deploy "GKE clusters, node pools, AWS route 53, S3 buckets, etc" in terraform. Then take the terraform output and convert it to command line options that I pass to helm when deploying a kubernetes cluster.

I'd be very tempted to just use terraform. But helm, with our forked charts, extensive values.yaml files, etc. has permiated the deployment.

So... rather than try to break up the helm beast; I leave it and keep the separation of concerns (infrastructure vs k8s) as described at the beginning. It works pretty well to be honest is rarely the source of problems.

That was painful to read!

It kind of feels like cheating with all the shrinking/expanding of vertical/horizontal cells.

“Success is stumbling from failure to failure with no loss of enthusiasm.” - Sir Winston Churchill

You have an incredible amount of experience that is invaluable to wherever you go. The success of a company is built on the learnings from failures of its employees.

Take a breather, look around, and embrace new opportunities!