Software-Architektur
April 15, 2024
SMEs, Steer Clear of Microservices!
Small and medium-sized enterprises (SMEs) often attempt to mimic large corporations and may not realize the harm they inflict on themselves through overengineering.
Marcus HeldEntwicklungspraxis
March 29, 2024
Daily Practice
Hi, Have you ever tried closing vim? You probably know the meme. Even after decades, I still find it funny 😁 But what I haven’t managed to do in all these years is to seriously learn how to use vim. Sure, I press i to enter insert mode and then I can type. And I’ve also learned dd to delete a line. And yes, of course, I was one of the three million viewers who were helped by Stack Overflow to close vim 😉
Software-Architektur
March 22, 2024
The Cost of Accidental Complexity in Development
Discover how Accidental Complexity in software development can lead to increased time and financial expenses and learn strategies to mitigate it. Understand how unnecessary complexities creep into IT projects, distinguish them from Essential Complexity, and explore how efficient team management can boost productivity.
Entwicklungspraxis
March 14, 2024
Two More Billion Dollar Mistakes
Hi, You might have heard that null was referred to by its creator, Tony Hoare, as the “billion-dollar mistake.” In 2009, he publicly apologized at QCon for taking the easy path in 1965 by inventing null: “I call it my billion-dollar mistake. It was the invention of the null reference in 1965. At that time, I was designing the first comprehensive type system for references in an object-oriented language (ALGOL W ). My goal was to ensure that all use of references should be absolutely safe, with checking performed automatically by the compiler. But I couldn’t resist the temptation to put in a null reference, simply because it was so easy to implement. This has led to innumerable errors, vulnerabilities, and system crashes, which have probably caused a billion dollars of pain and damage in the last forty years.”
Software-Architektur
March 5, 2024
My War on Kubernetes
Hi, I need to make a confession right off the bat: I’m at odds with Kubernetes. It’s not Kubernetes’s fault, though. It’s my projects. Or rather, the teams I’m part of. These are teams with a maximum of 30 software developers, plus a few business people and designers on top. But there aren’t that many developers. These teams don’t need Kubernetes! No. To put it more bluntly: These teams can’t handle Kubernetes!