Latest Posts

Legacy Is Sexy

Hi,

Unpopular Opinion Warning: Legacy is Sexy!

To be honest - I didn’t always see it that way.

You probably felt similar.

My first (big) professional project was a legacy application

It wasn’t actually that old. If I remember correctly, it wasn’t even a decade old.

But it felt much older.

This was mainly due to the many inexperienced developers who worked on the application.

I was green behind the ears as well.
The central architectural pattern: The God Class


How a Release Failed

Hi,

After 9 hours, the decision was clear: We had to roll back.

The first release in almost 1.5 years had failed.

And it was going so well. The meticulous preparation of the past weeks had paid off. Everything was going according to plan. The necessary changes to the VMs went as expected. The major migration was successfully completed after one hour of runtime. The new content files were successfully deployed with the new system. The new CD pipeline ran for the first time on production – and it was successful.


I ❤️ Releases

Hi,

After almost two years without a release, this Saturday marks the big day.
One of my clients hasn’t released for two years - incredible 🤯

Why? There are many reasons.

The team got entangled in complexity. Significant (and necessary) changes were made.

But these led to numerous side effects. And the goal was to do everything “right.” So, development continued. With one topic completed, five new ones emerged.

Breaking out of this cycle was challenging.

When I joined the team in July, we decided: We need to break this vicious cycle.


Panic

Hi,

Nervousness sliced through the room. I saw it in the eyes of all attendees.

It was supposed to be just a routine meeting.

Once a week, the development team meets with the admins to discuss current topics.

This meeting has been held for years.

Same time, same people, (almost) the same topics.

But something was different this time.

A new colleague participated for the first time. An external.

We brought him in to work on “DevOps”. Mainly automation. CI/CD, provisioning, tooling, compile-time optimizations. Everything that improves the developer experience.


Broken Windows

Hi,

A week ago, during my talk on “Pragmatic Programming with Kotlin” , I discussed the Broken Window Theory.

Originally, it’s from criminology.

In criminology, the broken windows theory states that visible signs of crime, anti-social behavior, and civil disorder […] encourage further crime and disorder […].

~ Wikipedia

Dave Thomas and Andy Hunt have applied this concept to software development.

Whenever there’s poor design, an unclear class, inadequately tested code, or unused assets in the repository, it becomes more likely that more “broken windows” will follow.


Top