I was recently asked, “When is it ok to add code comments?â. We then talked about explanation vs. justification.
Code should be self-explaining. What the code does, should be obvious by reading the code. If you have to add comments to the code, to explain what it does, then it is a code smell.
On the contrary, [...]
Entries from January 24th, 2005
Code comments: explanation vs. justification
January 24th, 2005 No Comments
Tags:
Test-driven development rhythm guide
January 18th, 2005 No Comments
Strict adherence to the TDD Mantra of Red-Green-Refactor generates a rhythm that makes programming fun and helps the design grow organically. This pictorial guide is a one-page cheat-sheet to keep reminding you of Test-driven rhythm. The guide also suggests the approximate time that should be spent on each phase of Test-driven rhythm.
You can download it [...]
Tags:
Test-driven development quick reference guide
January 18th, 2005 No Comments
Being test-driven requires lot of discipline. There are several questions that get asked frequently: “What is a unit test? What is not a unit test? What does being test-driven mean? Should I test private methods?”. This one-page guide attempts to provide a quick reference to several of these common questions. It also includes quick references [...]
Tags: