A programmer's blog offering advice on code quality, unit testing, team decisions, and non-technical skills for software developers.
HN commenters link it in debates over TDD and code comments, including its post arguing that comments are evil.
My point is: If TDD leads you to bad design you're doing it wrong. You are probably not listening to your tests and you are probably not taking care to refactor towards a better design. Maybe you are even writing bad unit tests [1].
BTW, if any technique in software development leads you to bad design, and you don't stop and try to improve something, you're doing software development wrong. If a technique does not help you, you have two possibilities: Trying to do it better (maybe with outside help), or trying something different.
[1] http://www.makinggoodsoftware.com/2012/01/27/the-evil-unit-test/
#1: Definitely agree, I'm surprised I don't hear this more often.
#2: ...Make him code using the same tools he would use in the position he is applying for....
What sort of tools is he referring to? I've always been given free reign on my work box, and I put what I want on it. It has to be interoperable, of course.
#3: Good idea, but why leave and come back? Why not just have them talk you through it? I much prefer interactive interviews.
#4: Make sure their personal website doesn't have a link to their Google Apps verification page.
http://www.makinggoodsoftware.com/google50f905a7cdbdd588html/
Please read this other post for details in what I mean when I say that "comments are evil" http://makinggoodsoftware.com/2009/06/06/comments-are-evil/