4 ms·
This comes up pretty often. Here's a sentiment that is often present: I heard that to get excellent results I should do X, but I don't see a really pai
by dwc 15y ago
This comes up pretty often. Here's a sentiment that is often present:
I heard that to get excellent results I should do X,
but I don't see a really painless and trivial way to
do X. X doesn't seem practical.
When I work with non-coders to help them with their scripts or whatever, I commonly see all kinds of things that should be done better: simplify this, refactor that, etc. I have learned the payoffs for doing things the right way, and I try to pass some of these things on. Usually the response is "I understand. That would be a better approach." but then they go back to their old ways. They just want to get the immediate thing working and move on.
It's not at all surprising that advice from smart people with a lot of experience seems like a lot of work to those of us just trying to get today's problem solved. But take a step back and look at anyone working at the top of their field and you'll find them doing lots of things that are hard, involving doing things right rather than just getting a task crossed off the list.
"Wow, that chef keeps everything spotless and sharpens his knife a lot, and only uses the best ingredients."
"That master carpenter sure spends a lot of time caring for tools and doing a lot of other things that aren't cutting wood."
Why should hiring coders be any different, unless you believe that coders are a commodity?
- joe_the_user 15y agoA good engineer isn't one who designs a building with the thickest walls possible but with walls having appropriate thickness. And generally, I don't think everyone at the top of their field necessarily gives the advise to use the absolute best tools and materials. A lot would instead give the advise to use appropriate tools and materials. A lot of good programmers can recognize that a quick but inefficient VB script can do better.
- jamesbritt 15y agoA lot of good programmers can recognize that a quick but inefficient VB script can do better. Quite so. Some "best practices" only earn their keep once they become ingrained and automatic. Prior to that there's additional cost that only makes sense when amortized over a long enough time. If there's no real reason to expect that payoff then there's no good reason to make that extra effort.
- wh-uws 15y agoI never thought about it that way. Very powerful and succinct answer. I've thought something similar many times but never articulated it that well
- freshfunk 15y agoIn general, quite sound advice. But, to follow this analogy, you don't always need a top chef. You may just be working a hot dog stand, a McDonalds or a college Chinese joint. Not every chef is headed to a 5-star restaurant.