Why do we need technical interviews at all?
Do other technical jobs work this way?
Do care mechanics take home a vehicle and prove they can replace brake pads?
Do accountants log in to some online environment and deposit a paycheque or pay an invoice?<p>Oddly enough, if we don't do our job, we get fired, just like everyone else. Other businesses actually apply this to their interviews and don't require applicants to demonstrate something utterly bloody trivial, as if they could somehow do their job for a decade and not know the basics.<p>Invariably, every dev writing these kinds of articles is simply stroking their own way of thinking - usually these discussions do not contain:<p>a) a modicum of common sense.
b) an understanding your brain does not work the way everyone elses does.<p>Just because you find a certain debugging method works for you, doesn't mean it works for me - your most effective technique is not necessarily my most effective technique, because I don't think the way you do.<p>Some programmers may be slower at debugging, but faster at determining a good solution to a complex problem. They may be slower at writing Jenkins jobs, but faster at solving Maven problems.