Why assessing inner software quality is bad for decision-makers (and why customers don’t care anyway…).
Technical debt? Who cares?

Why assessing inner software quality is bad for decision-makers (and why customers don’t care anyway…).
Some months ago, I did some redocumentation work of a mid-sized legacy system (~1 Mio. LOC). Among other things, the system lacked homogeneity, that means there were many terms that were differently interpreted from different teams over the time…
At the BarCamp “DevOps Camp compact 2017” last weekend, I moderated a discussion round based on the question
“What prevents you from doing software development effectively?”
The original reason for this question was that I wanted to know…
Michael Feathers describes how to safely remove code aligned with the business’ needs. Here is what I took away…
In preparation for a talk about performance optimization, I needed some monstrous amounts of fake data for a system under test. I choose the Spring Pet Clinic project as my “patient” because there are some typical problems that this application does wrong. But this application comes with round about 100 database entries. This isn’t enough at all…