Hi Jan!

Some time ago, I wrote an article explaining how the same bad decisions that make the Global Warming worse, are the same that make the code quality worst.

TL;DR There is something called the tragedy of the commons: if several people share one resource, but if one depletes it faster than the other achieves a private benefit, everything will become worse.

In the Global Warning you have to pay more (in time, commodity, ...) to be greener, but when everything come worse, your inversion would be diluted among everyone. So, those who did nothing have a net return.

Another example is sharing the bill in a restaurant. If you do not have too much money, and you want to skip deserts, you will pay the other deserts, and the others will get a discount thanks to you.

So, the same happens with software. All the team share, and suffer, the same code repository. Every new mess slows everyone, every cleanup accelerates everyone. If someone intends to seem better than the others, just skips cleaning. When everything slow down, everyone else will slow down, and he can keep ahead by making more mess.

The challenge is great. And there is another thing that you may want to consider: is the functionality that you have implemented necessary? Or you can remove it?

Software tends to be bloated, in every aspect.

Thanks for the article and for the fabulous final vision. And congrats!