You may have noticed that I haven’t written anything new lately… So instead of leaving you there, wondering what may have happened, I have decided …

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!
When a team of developers works on projects, they need to agree on code conventions, standards, best practices… Wait, do they have to? What are the developers giving up on in order to deliver uniformly-formatted code? In this post i defend the idea that code conventions and standards come with a high price, and that there might be a different way of working together.