3 ms·
You do not create clean code for others, you create it for your future self. And he/she will appreciate it.
by franze 3y ago
You do not create clean code for others, you create it for your future self. And he/she will appreciate it.
- 0xfab1 3y agoFuture maintainers, who could be you. It has happened to me a few times, and I thanked my past self every time. It doesn't even have to be clean code. Sometimes I'll even settle for understandable code. In my experience, however, few people care about this. My most common comment in code review is "add doc" or "add explanation"
- m000 3y agoTrue. But you should also write it for your fellow developers/engineers. If the culture among engineers in your job discounts the value of clean code, you're probably entering a world of pain. Sure, you should not obsess over clean code, as it does not directly produce value. You should also not expect your manager to understand its value. But if your fellow engineers frown upon efforts to improve code quality, start looking for your next job. The mental drain is just not worth it. Esentially, where the clean code is appreciated, mediocre engineers/developers will eventualy acquire "guru" status, just because they happened to be hired a year or two earlier than the better ones. And will often be unfriendly to anyone "threatening" their status.