I was thrown in a project, that was a big mess. They told me the guy who built it was a pro, but it...

Dixit Ram

Browsers

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

A developer's perspective on moving away from obsessive clean code practices after experiencing both extremes - working with messy legacy code and a colleague who over-refactored. The author argues that perfectionist code cleaning can become procrastination, drawing parallels to inbox zero mentality. Instead, they advocate for pragmatic improvements: fix code when you're already working with it, focus on functionality first, and accept that some messiness is acceptable if it doesn't hinder productivity. The key is finding balance between writing maintainable code and delivering value.

The Moment I let go of Clean Code

The in my opinion, most important word is mentioned already a lot in the comments below the article - balance. 
Going too far in any extreme is basically always bad. 
But I also learned that even small shortcuts and “code smells” can quickly accumulate and grow into big problems. 
Also, working towards perfection right from the start can and will lead to a lot of unnecessary work.
So, make it work first, then make it pretty. But - and that is crucial - don’t ship it before the second step! And that also involves testing, too.
This “pretty” also doesn’t mean perfect. Add enough abstraction to make it testable, but don’t over-engineer towards something you anticipate that it might come later. 
It is difficult to explain, and one has to learn this through experience. 
Having a mentor to show how to do this can help to reduce the learning effort, but not replace it.

I have 30988 mails in my inbox 📥
- after the recent cleaning of spam
What’s your Score !

Based. Balance is key, I tend to aim for readability and maintainability, and those do not take priority over getting the feature done (especially if the feature is also a new domain you’re exploring).

remember remember uncle bob hahahahah

The article is fine, I guess. Speaks of two extremes but failes in a major way. It speaks of a clean coder who cleans code and makes bugs. That isn’t clean code. Not even close. That is just stupid.
You make tests. Run these tests. Make sure you don’t reintroduce bugs and keep your code working even after refactoring.
Lot of nonsense to speak about clean code and not mention tests. Big fail.