M
Making Good Software
makinggoodsoftware.com · Personal blog · on HN since 2009
A programmer's blog offering advice on code quality, unit testing, team decisions, and non-technical skills for software developers.
What HN saysHN commenters link it in debates over TDD and code comments, including its post arguing that comments are evil.
17HN people shared it
3linked it in comments
80stories submitted
471story points
11 years agolast shared
2009people per year2026
Most-shared posts
- 1The evil unit test.2 people · 77 points · first shared 2012 · 52 comments on HN
- 2The four golden rules to be a better software developer.2 people · 31 points · first shared 2009 · 8 comments on HN
- 3Programmers top 10 sentences2 people · 9 points · first shared 2009 · discussion on HN
- 410 commandments for creating good code2 people · 7 points · first shared 2009 · 7 comments on HN
- 5How to rate your code from A to F2 people · 6 points · first shared 2009 · 1 comments on HN
- 67 best practices for taking decisions in the development team2 people · 5 points · first shared 2009 · discussion on HN
- 73 non technical tips to be a better software developer2 people · 4 points · first shared 2009 · discussion on HN
- 8Non-technical mistakes made by programmers1 people · 39 points · first shared 2009 · 13 comments on HN
- 9The best bug tracking system. Don’t raise bugs, write an automated test1 people · 37 points · first shared 2010 · 41 comments on HN
- 10Things they never teach in college about programming.1 people · 34 points · first shared 2010 · 22 comments on HN
- 11How to write readable code? 5 Tips to improve your code readability.1 people · 27 points · first shared 2009 · 17 comments on HN
- 12How to judge the candidate you are interviewing1 people · 24 points · first shared 2009 · 33 comments on HN
- 13Demystifying agile, top 7 myths.1 people · 19 points · first shared 2010 · 16 comments on HN
- 14Tips for naming variables1 people · 11 points · first shared 2009 · 22 comments on HN
- 15How to write efficient unit tests. 5 principles for unit testing.1 people · 10 points · first shared 2011 · discussion on HN
What HN people wrote when they linked it
struppi · 2015-11-24
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/
mattyb · 2009-07-16
#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/
albertoG · 2009-06-06
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/