4 ms·
> Let clean code guide you. Then let it go. Nah, no offense to the react fans but I'd rather listen to Fowler than to this guy. Sure, there are very specific
by luord 7y ago
> Let clean code guide you. Then let it go.
Nah, no offense to the react fans but I'd rather listen to Fowler than to this guy.
Sure, there are very specific exceptions where repeated code is an asset instead of a liability (and many of them are, appropriately enough, when dealing with graphics), but they are that: very specific. For 99% of situations, we ought to follow the principles (obligatory IMO).
- seattle_spring 7y agoDo you have specific experience that suggests that hyper-generalizing code before you even know about multiple use cases is beneficial over carefully extracting shared logic only when needed? If I to pick one single practice junior engineers employ that ultimately bites everyone in the ass, it's a blind adherence to generic code and DRY at all costs.
- luord 7y ago> Do you have specific experience that suggests that hyper-generalizing code before you even know about multiple use cases is beneficial over carefully extracting shared logic only when needed? I've gone over my comment three times now and I'm yet to see where I even implied something like this. Could you tell me how you got this from my comment? I do want to see how I could send the wrong message so I can word myself better in the future. Just in case, one of the principles I follow is "premature optimization is the root of all evil".
- seattle_spring 7y agoThe article was literally about that, and your first line says "nah I'm good."
- deleted 7y ago[deleted]
- deleted 7y ago[deleted]
- _pmf_ 7y agoI think you're confusing Fowler and Uncle Bob.
- luord 7y agoWell, I mentioned Fowler because of this: https://martinfowler.com/tags/clean%20code.html https://martinfowler.com/tags/clean%20code.html Though he and Uncle Bob agree on many of these things so one could replace one for the other in my comment, I think.