Steve Yegge has published a new essay about technical interviews, and developers are already arguing about it.
The post, titled “The Last Technical Interview,” appeared on Yegge’s personal writing feed and quickly drew attention in a developer discussion thread. The listing provided shows 108 points and 79 comments, which is not internet-scale chaos, but enough to signal that the topic still has teeth. The source summary does not include the essay’s full argument, so the safe read is narrower: another well-known engineer has reopened the long-running fight over how programmers get hired. That fight tends to flare up because almost everyone in software has either given, taken, failed, or resented one of these interviews.
Why it matters is not that one essay will kill the whiteboard, the take-home project, or the algorithm quiz. It is that technical interviewing remains one of the industry’s least settled rituals, despite decades of companies treating it as if it were a measurement instrument. Hiring teams want a signal; candidates often see a performance test shaped by luck, anxiety, and whatever question happened to be in rotation that week.
The durable lesson is boring, which probably makes it useful: if your interview process claims to predict real engineering work, it should look less like theater and more like real engineering work.