It is not enough for code to work

In my remaining spare time, I'm reading the book Clean Code by Robert C. Martin.

At the end of chapter 14, the Conclusion states:

"It is not enough for code to work. Code that works is often badly broken. Programmers who satisfy themselves with merely working code are behaving unprofessionally. They may fear that they don’t have time to improve the structure and design of their code, but I disagree. Nothing has a more profound and long-term degrading effect upon a development project than bad code. Bad schedules can be redone, bad requirements can be redesigned. Bad team dynamics can be repaired. But bad code rots and ferments, becoming an inexorable weight that drags the team down"

It happens that some programmers are motivated only by money and aren't really interested in doing a good job. As a result, these people are a kind of cancer for every project they work on: everytime they solve problems in quick and dirty ways, producing a lot crap and hiding themselves behind a lot of excuses. The truth is they are just unprofessional.

Also, it happens that some project leaders are just ignoring these aspects and focusing mostly on evident short-term results, because only here and now count for them, as they are only interested to get a good appearance now: they don't solve problems really, they just paint a thin technological layer over problems and delude people with good-looking masquerades. As the time goes on, their projects become messes and they reveal themselves either blind or unprepared at all, trying to carry on, day by day, without facing problems seriously.

Personal considerations aside... Clean Code is a must-read-book for all programmers and project leaders who want to invest in their professionality .