The Art of Response
Imagine two different software engineers in job interviews. Both are asked for an algorithm that solves some programming puzzle, such as "identify all palindromes in a string of characters." The first candidate, Alice, reflexively enters problem-solving mode upon hearing the problem. She pauses for a few seconds as
Imagine two different software engineers in job interviews. Both are asked for an algorithm that solves some programming puzzle, such as "identify all palindromes in a string of characters." The first candidate, Alice, reflexively enters problem-solving mode upon hearing the problem. She pauses for a few seconds as she internalizes the problem, and then quickly thinks up a very inefficient algorithm that finds the answer by brute force. She decides to sketch this algorithm first (as a warm up) and then turn her mind to finding a more efficient path to the answer. The second candidate, Bob, res
Explore this link on the map →saved by
related reading
- The art of response — LessWronglesswrong.com
- Stop trying to try and trymindingourway.com
- Be impatient | benkuhn.netbenkuhn.net
- Willingness to look stupiddanluu.com
- Notes on Puzzles — Nabeel S. Qureshinabeelqu.co
- How We Hire Engineers When AI Writes Our Code | Tolans.comtolans.com
- Post 42: When You Already Know the Answer - Neel Nandaneelnanda.io
- On Really Trying · Gwern.netgwern.net
- How I Hire Programmers (Aaron Swartz's Raw Thought)aaronsw.com
- Standing Invitation | Kalzumeus Softwarekalzumeus.com
- The Guerrilla Guide to Interviewing (version 3.0) – Joel on Softwarejoelonsoftware.com
- Skills from a year of Purposeful Rationality Practice — LessWronglesswrong.com