Browse by Tags
All Tags »
quality (RSS)
Summary Motley: Checklist? We don't need no stinking checklist! Checklists are for anal people with short memories. Maven: Checklists are very useful for activities like code reviews, where it is difficult to remember everything we need to look for. Good
Read More...
Summary Motley: I'll deal with performance issues when I have something to test. Then I'll run the profiler and just optimize the slow methods. Maven: Think about performance early in the development cycle. Set goals. Design for performance. Measure,
Read More...
Summary Motley: I'm not sold on this inspection thing. There were too many problems during our session. Plus, everyone just picks on the author and they hate having their code reviewed. Back to informal peer reviews for me. Maven: Follow inspection best
Read More...
Summary Motley: Inspections seem a bit heavy. They suck up too much time for little gain. Maven: Inspections are actually a fairly light-weight structured process that find more issues compared to ad-hoc peer reviews and team reviews. ______________________________
Read More...
Summary Motley: Quick ad-hoc peer reviews are sufficient to nail bugs early in the development cycle. Maven: A more structured team-based code review process can lead to more issues found. ______________________________ [Context: Maven overhears a code
Read More...
Summary Motley: Unit testing is the test team's job! I am not paid to write tests. Maven: White box (unit) tests help with code quality and give you confidence to change your code. ______________________________ [Context: During a previous conversation
Read More...