As professional developers, we constantly try to make our code readable for all to understand. We use the term “fluent code” to describe that line of thought. But beginners may find that a bit of an abstract notion… In this post I propose you to examine a concrete case I have recently encountered, and one solution for turning that bit of code into something I am proud(er) of.
After years of developing software by (incorrectly) applying the Scrum methodology, I have come to this conclusion: Scrum is the new death march. Or rather, Scrum does more harm than good when it’s mindlessly requested by managers who are merely trying to show how modern and trendy their development teams are.
Scrum: this single word triggers heated debates, passionate evangelization and tales of horror stories. But whether you think it works or not, there is this one thing I’ve seen some Scrum adopters do, which defies the whole purpose of the methodology. And in my opinion, that is one of the factors that might lead to… epic failures!