What are we going to do next? Lots of teams are asking this question every day. I've certainly been part of planning sessions of every shape and form. Be it just a quick check-in or a planning WEEK. They all had one thing in common: the plan rarely worked out.
This would all be way easier if we would just throw everything away and build it ourselves.
You might have overheard people saying or said some of the following phrases yourself. "I work better on my own," "Pair programming just doesn't work for me," "Other people just don't think the same way I do." Usually, when I hear people say these things, we discuss whether we should spend more…
In the past months, I have learned something about myself. I learned that I value a good development process a lot. One thing, in particular, seems to spark the most discussions: when to make decisions. Some people also call this "When to converge". This topic needs some unpacking.
This article is loaded with my personal opinion on how to do things. The baseline I'm going to describe is derived from my personal experience. If you have a different view on some topics, please let me know. I'm not claiming that what I'm doing is perfect!
Lately, I've come across a couple of blog posts like "Most Technical Debt Is Just Bullshit" and "Technical Debt Isn’t Real". They're discussing whether we twisted the initial definition of technical debt to mean anything and thus nothing. People have since then asked me about my opinion on the…
Here are two sentences that I sometimes hear from developers.