When Apple made a phone, it turned out it wasn’t really competing in the handset business; it was competing for the next dominant personal computing platform.The more I think about an Apple car, the more I think that it might be the basis of their future “computing environment”: a space that is completely aware of and responsive to its occupant(s).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.Did not expect anyone to be able to pull of a “tree” theme this well. It is related to the “Fallacy of False Cause” and to the “Illusion of Control” bias.(Returning the first point, I suppose the implication is that driving a nail is the fizzbuzz of carpentry.) Let’s just cover the first few questions: If the only way you can describe your work is “I’m a programmer. Yes it would be friendlier if the interviewer led a bit with “What kind of work have you been doing? As an interviewer I’m open to the idea that someone good at any one of these probably has great potential for any of the others, but if you’ve got nothing more to say about your career than that you’ve done general things in a general sort of way, you can’t exactly blame me for taking my own direction on what details I’m going to dig into. And all those kinds of brown would seem to be of major interest to a carpenter: if something is being stained instead of painted then I’d think that would affect the choice of wood. If you’re building a software library that will be called by a UI, then responsiveness matters.” or “Tell me about some of your favorite projects.” but you’ve got to meet a weak interviewer in the middle. If you’re writing an order processing system open to the public, then you need to consider denial-of-service issues.If a programmer walked into an interview and gave answers this evasive about how many projects he’d done in Java, he’d be an obvious no-hire.Not having certain experience is one thing; not even knowing what experience you have is another matter entirely.
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.Inevitably the media seizes upon a single person, or a cohesive group all of whom are described as conspiring together to cause the event.Blame seldom (if ever) falls on multiple villains: the finger should point in one direction and one direction only.If learning this stuff is so easy, then I’d rather hire someone who understands what the goal is of finish carpentry.And ideally someone who showed some interest in the project and the skills required to do it, not just the job.