When I first started developing software, I was often lured in by flashy marketing claims of tools or programming languages. “You can display ‚Hello World!‘ in 5 minutes!” claims on the front pages of tools or programming languages. While the claim is often true, it isn’t honest. Yes, it took only a couple of minutes, but I just copied example commands without understanding what I am doing. I had to trust the default settings. I had to accept the shortcomings of the tool I picked. What about security? And of course, I could not sell ‚Hello World!’ to a client. I would have wished for honest courses teaching me what I really need.
Benedict Roeser Posts
Documentation guidelines in most teams seem to be repeating obvious truths: “Documentation is important!” or “Don’t forget about documentation!” A good IT team establishes clear…
A good CSV import or spreadsheet import experience is rare. Here are some hints and best practices that will make your users happy as well as your developers.
When I started leading a team, I defined what I expect from each software developer and how I see the role of a team lead. At that point, I did not know about Engineering Ladders yet, otherwise I would have build upon that framework. Instead I created this diagram.
The diagram shows the three areas I expect every software developer on the team to put work in. Of course the bar is set a bit lower for trainees. As a bare minimum, I expect a trainee (after the onboarding phase) to deploy working code to production.
I’ll explain every area and the effects remote work can have on them.
As startups evolve, their product changes frequently. Instead of focusing on the best possible product though, they should focus on awesome teams. A truly agile, passionate and intelligent IT team can quickly adapt to changed objectives and create different products over time. Through this lens, the software that is created can be considered as a mere byproduct of a well-functioning team. A team that has fun working and builds high-quality software on the side. Here’s how.
Integrating PayPal Plus (a German PayPal integration that supports payment via invoice) can be hard with a modern tech stack. The PayPal Server SDK does not include TypeScript types and the PayPal Plus code rendering payment selection is vanilla JS. Here are some hints how to integrate it.
Software developers sink a tremendous amount of time into boilerplate code. Code that does not bring any business value and is just there to “make things work”. Over the years, in some areas our community managed to reduce boilerplate code significantly. Projects like Spring Data Rest for instance remove the hassle of writing boilerplate code to access data from a database and map it to entity objects. It even removes the need to write controller code. But is that enough? This article implores more radical steps to avoid or remove boilerplate code.
Teams use microservices and microfrontends to reduce mental load, decrease accidental coupling of unrelated code, to deploy independently, for fast feedback loops and CI runs, to isolate issues or to scale with team size. In a microservice architecture, you should avoid shared dependencies or a common core library. To be more precise, don’t share libraries that increase coupling.
As IT professionals, we know that. However, despite our best intentions, shared dependencies sometimes creep in and cause issues. From what I’ve seen, here are the most frequent occurrences in the backend:
For every problem, there is a multitude of solutions. Helping clients to find the ideal solution for their issues, is what a consultant does. In this article, I’ll tell the tale of a very German printing problem, that may or may not have really happened. I’ll present three possible solutions, one of them I consider worthy of the ‘perfect consultant’.
Printing…? Like most IT professionals I have a love-hate-relationship regarding printers. These machines seem expensive, loud, slow and often unnecessary, on the other hand, finding a solution to the arcane art of printing (article in German), is always fascinating.
While working on an IT project, thousands of decisions are made. One of the most important tools to handle the project, are decision logs. Most articles praising the benefits of decision logs focus on how they help to make, remember or fine-tune a decision. The biggest value I see however is, that decision logs can prevent repeating costly mistakes. Consider them as a safety net as powerful as 100% automated test coverage. In order for that to work though, you need to write proper decision logs. I’ll tell you how.
There’s an old saying in Tennessee — I know it’s in Texas, probably in Tennessee — that says, fool me once, shame on — shame on you. Fool me — you can’t get fooled again.Georg W. Bush