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).In that sense it might be more of a long-term competitor to the Amazon Echo (and whatever Android variant Google is pitching at the same space) than to Tesla’s cars. Three points for clarification: The old “What if they hired carpenters they way they hire programmers?From this perspective, maybe the thing that’s kept the Apple TV on hold for so long is that they were trying to go down this road, but they kept failing to pull it off (to their standards) in the living room. ” joke/commentary didn’t sit right with me the first time I read it, and after stumbling across it again I now see why.(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.
No need for a full play-by-play; we can skip straight to the awards. Slightly overplayed the hockey theme by turning her vagina into the goal… And for hedging her bets by qualifying for the hat-hobbling category. More nudity going on here than you notice at first glance. A little more skin next year and you’ve got a chance, Kazakhstan.
The exceptions—coders who really want nothing more than to follow some formula and take no responsibility for the result—are exactly who interviewers are trying to weed out.
Of course, there are carpenters who are creative craftsmen of the first order.
Among other things: I’ve never met anyone in the software industry who is happy with the hiring process, and that includes everyone who’s designed the process.
Nobody seems to have a solution to separating the potential stars from the mehs, and anyone who claims they do either doesn’t have enough perspective to understand the difficulty of the problem (young interviewers who have been trained in one particular hiring style seem to be blessed with the arrogance of blind faith), or they’ve perfected the art of hiring the mediocre (a sufficiently rigorous process can probably rule out almost all the disastrous hires, but will likely also lose a few stars…and it’s finding the stars that is the problem).
I call it the fallacy of causation, or the fallacy of the single cause.