Wasting time in tech interviews
&gt; Despite a long and storied career in software development, I have few abstract problem-solving skills. I proceed through problems in increments, getting slightly better each time. The beneficial thing for you that my experience brings is that I can do it really fast. Fast enough to deliver a working piece of software in a timeframe that won’t bankrupt you.<p>&gt; Never in my entire career have I whiteboarded a solution that even remotely survived contact with software frameworks, APIs and hardware constraints. A hundred different gotchas and restrictions lay in wait. The only way through them to a resilient solution is one step at a time. So, I can’t show you anything meaningful with Leetcode challenges unless I practice them as a discrete skill.<p>This, 1000x. This whole piece nails it, but this really jumped out.<p>I succeed and excel because I actually get things done, rather than &quot;mostly done&quot;. No interview methodology ever can hope to screen for this. Or any of the other things mentioned above.<p>The process is getting worse, not better, and this piece rightly points out why.