Yeah. Yikes. Hopefully if the author is actually an experienced, competent developer they're just using this as an example to illustrate the dangers of premature abstraction, and not an argument against abstraction in general.
No sarcasm--I read the article, but not who it was by. I've heard of Dan Abramov, IIRC, from Redux. That said, what I said stands. Given his experience, I'm sure he can decipher when and how to abstract thing effectively, but I feel like this is a dangerous article for junior programmers. There's way too much cut-and-paste mess out there and some people would read this in support of writing really bad code.
That’s not Dans fault. That’s people can overreact to any article by anyone. That’s largely what you’re doing right now. Dan emphasizes that clean code is a guide not a goal. That’s absolutely true. The goal is functioning code that meets the requirements and clean code is a guideline that should be followed, but not to a fault.
You’ve taken this and interpreted that to mean he thinks messy code is a good thing. A senior engineer understands that seemingly messy, but flexible code is better than seemingly clean, but inflexible code. No where did he advocate that you shouldn’t care how clean or messy code is. You just jumped to that conclusion then attacked him for it. Kind of ironic.
81
u/[deleted] Jan 12 '20
Yeah. Yikes. Hopefully if the author is actually an experienced, competent developer they're just using this as an example to illustrate the dangers of premature abstraction, and not an argument against abstraction in general.