HN user
Unit test are not just for people who write bugs (parent comment), a good start would be to test for the 9th row the problem was asking for. Since you can't test all possible values a representative sample would be good enough.
Just to be pedantic: It's not TDD if he already wrote the functional code ;)
Code Complete has 960 pages, not in the short book category
I beg to differ. There is always design work, you made design choices and even if they were careless choices you always have a final work that might be great or just poorly designed.
Practice helps if you can learn from the good and bad moves on both sides of the board. The article mentions analysis, have you tried that? Great players draw from a big pool of previous experiences and not only their own.
That's why it is very important to touch the company culture topic during the interview and find out if it's a good match.
This could be improved with natural language processing but I guess it is just a quick and dirty "15 minutes" kind of solution
He is called out right there in the post: Andy Clarke.