The list of TZs should sort naturally, not on order of TZ addition.

I disagree, I want them shown in the order I add them, not in order of how far from the UK they are.

Modify your schema through migrations that go through code review :p

Your reply is dismissive of the OPs grievances they shared with us all.

Suffering, and life, is a relative experience.

I think the poster wanted to be encouraging.

"We all know it could be considered as something, but, that given, let us just turn perspective and say: it's nothing".

Yes, my goal in sharing my story is not to garner pity but to give hope that it is possible to recover from even great loss and come out on the other side stronger. Blessings to everyone suffering right now.

So you agree: "From the point of view of the scientist, it is something. From the point of view that matters, it is nothing".

If I could have my time again I'd focus on enablement of the broader engineering group through an incident management process, readiness exercises, some aggregate incident analyses for the org to learn from and leaning into observability.

Infrastructure is kind of a solved problem for common use cases today, just requires the expertise.

With our ducks in a row I'd next have look to a GRC function for the compliance bits whilst splitting the platform engineers time between embedding engagements and tooling investments.

You're on the right path man, I'd love to know what I know now back then but unfortunately time doesn't work like that.

> Infrastructure is kind of a solved problem for common use cases today, just requires the expertise.

This is the problem however for many (older) companies. They either don't care, or quite literally don't know the infrastructure solutions out there which can save literally thousands of hours per year of headache. Sure, for many companies with legacy systems they have a "dont fix what isn't broken" mindset, but from what I've seen, I always ask, if shipping and modifying new versions of a system takes hours or even days to complete, is the system really not 'broken'? I guess I never realized it, but having automated and clean infrastructure with tests and uptime metrics is a must-have for me on anything I build going forward. Take 2-3 weeks to save months of headache.

Thanks. Means a lot, particularly coming from you.

Glad to see it's NATS and not Kafka for the pubsub system.

... because?

Yeah this is in line with my experience. However there are concerns about the accuracy of quartz clocks as temperatures fluctuate, this poses a problem for some orbital patterns.

Thanks to both answers - I've asked couple engineers of my generation and "that would be an interesting concept" was the best response I got. I have so much to learn!

Recipes are basically flame graphs, but for food.

Interesting, I always translate recipes into a mental GANTT chart and use multiple timers because I like everything to be finished at the same time.

As opposed to just running it ad-hoc when a change is made?

People do all sorts of things with terraform, if you need to is down to what you're doing and the context of your problem.

I've even run terraform on a cron like schedule before to ensure configuration of a web service matched what we defined rather than the constant small edits people were making in the console. Eventually the behaviour stopped but no reason not to.

> As opposed to just running it ad-hoc when a change is made?

Yes. I worked at a shop that made a terrible mess (at least IMHO) of things by using Terraform from Jenkins for everything. So build and rollout new Docker image -> `terraform apply` entire infrastructure from Jenkins.

To me use Terraform for Day-0 to build your infrastructure and CI/CD pipeline then occasional updates. CI/CD for the day-to-day, if you can get away with it.

I have read lots of people are doing Terraform from Jenkins. I guess there is a use case, just saying, probably best to think first.

Absolutely does depend on what your use case is. I find for very self contained terraform code it’s fine just to use the VCS-driven workflow, but when you have either a lot of inter-dependency or template driven terraform code using something like API/CLI-driven is ideal.

I'm sure nixpkgs will accept your PR (: truly though I've found the community pretty great and if a pkg is already in place it's not a quantum leap to add additional options to it.

Spoke to the founder recently chasing a job there, great team and a great attitude. Talented people should reach out!