The most common answer I got was that reproducible builds were desirable in case of rollbacks.

If you build your software now, will the result be the same if you build it again in 10 minutes? 10 days? 10 weeks?

Often the best thing for the situation is some method or technique that has been generally accepted as superior to known alternatives.

Purely technical problems are as rare as unicorns.

A set of principles does not make a strategy. Though it’s certainly better to have a set of principles than to have no principles and no strategy.

“What the large language models are good at is saying what an answer should sound like, which is different from what an answer should be.”

Jillian and Jonathan talk about ChatGPT. They begin by sharing their thoughts and experiences when using it. Additionally, they tackle its benefits and how it helps them write and understand code.

“To my surprise, most of the team was quite motivated to improve things but they didn't really know how.”

Working this way is a skill. It takes practice. But I believe anyone can get there.

When I work on a project that relies on manual verification, I'm never confident. I never feel sure of the work I'm doing.

Don't forget to measure your problem