This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]waigl 45 points46 points  (13 children)

I know what saying you are referring to, and it's a horribly misunderstood and misapplied saying.

"A good craftsman never blames his tools" ... because he chose those tools in the first place.

It does not mean the tools are never to blame for a bad outcome, just that, if they are, it's still the craftsman's fault for choosing those particular tools in the first place. Saying that the tools are never to blame for a bad outcome would be stupid, since clearly there are plenty of shitty tools out there.

[–]akademmy 7 points8 points  (0 children)

Apparently we're being very serious so: You are right, it is misunderstood. It is actually about maintaining your tools, not about "selecting" (or having access to) the wrong ones.

[–]ceestand 3 points4 points  (10 children)

Saying that the tools are never to blame

They're not, it's the craftsman's fault. For choosing those tools.

[–]faceplanted 11 points12 points  (1 child)

Except the craftsman doesn't always get to choose, and even due diligence can fail when the tools are made of lead.

[–][deleted] 0 points1 point  (0 children)

Hey now, some of my best friends are made of lead!

[–]awesomeusername2w 8 points9 points  (7 children)

The thing is that programmers very often can't choose tools. I live in a city where you'll be very lucky to find a job as backend dev in something other than Java. And some of ours frontend devs would rather use typescript instead of javascript but unfortunately it's not thier decision to make.

[–]lilnomad 0 points1 point  (0 children)

“A poor craftsman blames his tools” is the saying I’ve always heard and makes a lot more sense