update
-
✅ The problem with software
I’m currently reading The Checklist Manifesto by Atul Gawande. Gawande is a surgeon who wants to find a way to reduce the mistakes and their catastrophic consequences during surgery. So he investigates other industries such as air travel a…
-
🔄 The business model for updates
In the old’n days, a project was shipped and done, and we moved on to the next one. However, with modern connected systems, we can deliver a lot of value after the initial release. Most of our engineering effort may be spent after the initi…
-
🔄 The biggest benefit to frequent updates
Perhaps the biggest benefit of frequent updates is that the changes are small, making them easier for humans to absorb and adapt to. The conventional wisdom in our industry is that frequent updates mean things are always breaking. This has …
-
🎲 Isn't it risky to update your dependencies?
This is a common objection I hear when building industrial systems: “We want to lock things down to a super stable/tested LTS (Long Term Support) release and then stay on that release for a long time – it’s risky to update dependencies.” Is…
-
🔄 What is the first thing you should implement?
When building a new system, what is the first thing you implement? There are a lot of approaches – one is to implement a minimal proof of concept. However, I think an easy way to update software in any part of the system (Linux edge device…