Why is clean code still the exception and not the norm? An intriguing question I read recently. Most of the answers are so human, but also so wrong. It's them! The project managers, the junior developers...

Project managers care only about delivering more and more features, while they don't even understand what technical debt is, not to mention clean code. At the same time, the number of new developers doubles every five years, they don't learn how to code in a clean way, and obviously, there cannot be enough senior developers to mentor them.

These answers are so human but so wrong. Blaming others is never the answer. They lack any responsibility. We have to find a way to warn the stakeholders around us that if they continue like that, they'd shoot themselves in the leg. Even as an individual contributor, we have to raise awareness. Sometimes we have to say no, or even sometimes we'll have to step aside and look for another project. After all, if management doesn't trust you to do your job, why would they keep you?

Clean Code is hard. It requires serious effort in the beginning and discipline. At the moment, it's easier to be lazy. You need a framework, you have to push yourself and others to be better, to improve all the time. We have to drive these changes, we have to step up.

What we have to keep in mind is that the responsible party is always us. Never them. We have to raise our voices, we have to explain and educate. And just in case, we have to step aside. That's the only way towards more maintainable and reliable code bases. You might think it's an exaggeration today, but tomorrow you might understand that it can be a matter of life and death, not just professional pride!

Embedded software bus: platform-agnostic pub/sub library for real-time embedded systems

Speakers

Ivan Makarov

Invited experts

Kirill Tikhonov