I'm on Clean Code right now. And the reason for it was simply an event that happened on my work. I left a few days because of a mission and one of my colleagues was in charge of implementing a feature. I could have done in almost one day, because I am familiar with that particular pieces of the code. But one week passed and the feature was half implemented. I asked myself why this happened and the answer for me was bad code and bad architecture.
The bad code made hard to my colleague understand what exactly was happening there. The bad architecture made hard to my colleague to understand where she had to make the changes.
So, Yes! Clean Code ALSO matters!
And remember that this is not the only book from Uncle Bob. He has another called Clean Architecture. So it is not the end of your journey to right better code.
Another experience that I had is pretty much what Uncle Bob describes in his book. We had a product where the code simply rot up to a point that it was not possible to add any other feature. If that were the main product of our company, we would be broken by now. Fortunately, it wasn't.
Our job isn't just solving a problem. If you are really professional, you will solve the problem on an economically, responsible and sustainable way.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm on Clean Code right now. And the reason for it was simply an event that happened on my work. I left a few days because of a mission and one of my colleagues was in charge of implementing a feature. I could have done in almost one day, because I am familiar with that particular pieces of the code. But one week passed and the feature was half implemented. I asked myself why this happened and the answer for me was bad code and bad architecture.
The bad code made hard to my colleague understand what exactly was happening there. The bad architecture made hard to my colleague to understand where she had to make the changes.
So, Yes! Clean Code ALSO matters!
And remember that this is not the only book from Uncle Bob. He has another called Clean Architecture. So it is not the end of your journey to right better code.
Another experience that I had is pretty much what Uncle Bob describes in his book. We had a product where the code simply rot up to a point that it was not possible to add any other feature. If that were the main product of our company, we would be broken by now. Fortunately, it wasn't.
Our job isn't just solving a problem. If you are really professional, you will solve the problem on an economically, responsible and sustainable way.