7 ms·
that doesn't really make sense, does it? being a good programmer includes not creating useless abstractions, so what you're actually saying is "when i last wor
by andrewcooke 14y ago
that doesn't really make sense, does it?
being a good programmer includes not creating useless abstractions, so what you're actually saying is "when i last worked with poor programmers they weren't very good". and, in response to that: well, duh.
- rhizome 14y agoWell, these poor programmers who weren't very good sure knew a lot about how to make code worse! You're right though, it's a struggle to characterize people who know too much.
- jiggy2011 14y agoYou could argue they "Knew too much" but equally they could know too little. In other words they know enough about X to understand how to implement X but not enough but not enough about why to implement X.
- rhizome 14y agoYou can quibble with what side of the fence I'm describing, but the facts (and my sense of them) remain. Yes, they didn't write good, maintainable code AIUI, and whether that's due to inexperience in writing maintainable code or to shoehorning CS training and metaprogramming into a web developer role is fairly irrelevant to me. As it happens, I think the latter is the bigger problem.