“Programmers” are the architects and structural engineers who design the buildings; they get programming languages and frameworks and IDEs to hammer the nails.I have no doubt that the industry is full of coders banging out one CRUD app after another, but their work bears a lot more relation to architects customizing a house design to a particular site (or, a better analogy, 19th-century railroad engineers applying the standard truss designs to design bridge after bridge) than it does to contractors framing house after house based on the designs they’re handed.Throwing on a beret does not a national theme make. Could we be witnessing the start of a generation-long leadup to contention in the hat-hobbling category? Finally, we have a couple of new awards for 2015: There’s a specific form of logical fallacy or cognitive bias that I’ve never seen explicitly listed in collections of such fallacies or biases.
Blue-collar credentials and being treated like a unique, creative, and highly-paid professional just aren’t compatible.
Those aren’t the guys you’re going to bend over backwards to hire to frame your walls.
The whole story seems to be built on the premise that the only skill a carpenter has is the ability to drive a nail straight, making any notion of an “interview” farcical. There’s a hell of a difference between a framer, a cabinet-maker, and a furniture-maker. There is, however, a lot of brown stain, and brown shingling, and brown brick. Questions like this are exactly how a good interviewer separates a blinkered newbie from an expert with perspective.
I call it the fallacy of causation, or the fallacy of the single cause.
I don’t think we’re wired very well to reason about outcomes that result from many different inputs.