3 ms·
And why would the user care about your clean code on the frontend? It's usually minified anyway. Clean code is not for the user, it is for you as a developer.
by fishnchips 10y ago
And why would the user care about your clean code on the frontend? It's usually minified anyway. Clean code is not for the user, it is for you as a developer.
- exclusiv 10y agoYes you are correct, but I'm not talking about clean code on frontend. The user doesn't care about any code. If it works, it works. I understand clean code is for the developer(s). That's precisely my point. You don't always need to go through a SOLID checklist with your project. Sometimes you have deadlines, sometimes you're the only dev and you know the project will die post-launch. So if it works; you're good. I'm not sure why this part of my original comment is confusing or controversial: "sometimes it's a trade-off in deciding your approach knowing the lifetime requirements and maintability needs of a project which only comes from experience" A purist push for design patterns and paradigms for every project is not based in the real-world.