In 2017, David Heinemeier Hansson sparked a viral discussion on Twitter about the inadequacies of whiteboard coding interviews, leading to a broader conversation on the relevance of interview practices in the tech industry.
Abstract
The article discusses the humorous and critical confessions of programmers regarding the whiteboard coding interview process, which began with a tweet from David Heinemeier Hansson, the creator of Ruby on Rails. His critique of the interview method sparked a wave of responses from the tech community, highlighting the disconnect between these interviews and real-world coding skills. The piece also references a blog post by Quincy Larson, who likens the necessity of recalling algorithms without resources to a post-apocalyptic scenario. Various tweets from software engineers and tech personalities are embedded, further illustrating the skepticism towards whiteboard interviews. The article concludes by mentioning the shift towards more practical interview methods, such as pair programming, and suggests that these changes are more reflective of a developer's actual capabilities.
Opinions
David Heinemeier Hansson's initial tweet sets the tone, suggesting that whiteboard coding challenges are not indicative of real-world programming skills.
Quincy Larson's blog post implies that expecting developers to recall algorithms without reference materials is unrealistic and not reflective of actual coding environments.
Tim Dierks, a Lead at Google, and other software engineers express similar sentiments, mocking the artificiality of whiteboard interviews.
The article cites Four Square's decision to abandon whiteboard interviews in favor of take-home assignments, which they argue provide a more accurate assessment of a candidate's abilities.
Aline Lerner, the Founder of interviewing.io, is quoted to underscore the arbitrary and non-deterministic nature of technical interviewing processes.
The consensus among the various opinions presented is that the tech industry needs to reevaluate its interview practices to better align with the practical skills required for the job.
Coding Sins: Hilarious Developer Confessions
How ‘whiteboarding’ got mocked
Pic credits — Pinterest
In the year 2017, David Heinemeier Hansson, a well-known programmer and the creator of the popular Ruby on Rails coding framework, started a Developer Confessions thread on Twitter with this post:
In no time, it went viral. He ranted about interview practices in large companies — kicked off a number of tweets across many technical professions.
If you are interested, you can join my newsletter through which I send tech interview tips, techniques, patterns, hacks — Software Development, ML, Data Science, Startups and Technology projects to more than 30K readers. You can subscribe to Tech Brew :
Being a software engineer myself, to some extent I concur with David.
Famous coding instructor Quincy Larson wrote in a blog post:
“The only world where you would actually need to be able to recall an algorithm would be a post-apocalyptic one, where the hard drives of all the computers connected to the internet were fried, and all copies of foundational academic papers and computer science textbooks had been reduced to ashes”
In this post, I’m going to cover the hilarious confessions of the programmers as tweets.
While the veracity of whiteboard interviews is still debatable — people think that whiteboard interviewing is a discrete skill, much like being able to remember Pi to a thousand decimal places, Aline Lerner, the Founder of interviewing.io once said — “After drawing on data from thousands of technical interviews, it’s become clear to us that technical interviewing is a process whose results are nondeterministic and often arbitrary”.
We were concerned that [the whiteboard interview] process filtered out many other great engineers for reasons other than their abilities. Some possible reasons include variation between interviewers, candidate nervousness, or the unnaturalness of whiteboard coding generally.
As a result, Four Square has gotten rid of the random false negatives that can result from the “algorithm question lottery.
To conclude, most of the companies now rely on the pair-programming-centric interview to weed out bad candidates. Well, that makes sense. Isn’t it?