Random Thoughts

Replacing Agile with the Studio Model?

The Agile Manifesto was written over 20 years ago and according to some it's age is starting to show. After all, 20 years in IT should be a good approximation of eternity given the rate of change in the industry...

How to stay DRY doing Microservices

This post is also avaialble on GitHub together with all the source files! When using Jenkinsfile and Dockerfile with Microservices you are typically repeating the same boilerplate code over and over again. Initially this is not a problem but as the number of Microservices - and Git branches - start

Exception handling using enumerations in Java (II)

In the first part of this blog post I discussed how Java Enumerations can be conveniently used as 1. Fault codes in exceptions; and 2. Provide formatted and localized error messages The major drawback with the approach is that the fault codes make exception handling more complicated for cases when

Exception handling using enumerations in Java (I)

When I first read about Swift I quite liked its error handling. In Java checked exceptions have gotten quite a bad rep but instead of throwing out the baby with the bathwater and getting rid of checked exceptions altogether, the way they do it in Swift seems to strike a

Toyota and Waterfall methdology for developing software

As you may know Agile software development is inspired by the principles of Lean Manufacturing which in turn is derived from the Toyota Production System (TPS). One Agile methodology, Lean Software Development even borrows the name Lean to make the connection explicit. Since the principles in Lean and TPS have

Random Thoughts © 2026