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.
Leave a CommentCategory: News
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…
Leave a CommentWhen 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.
Leave a CommentHerzlich Willkommen auf meiner Seite! Mein Name ist Benedict Roeser, was schon an der Domain klar geworden sein sollte. Auf dieser Seite sind die wesentlichen…
Leave a Comment