Progressive Development

Zany Adventures in Software Engineering with Maven and Motley

Browse by Tags

Tagged Content List
  • Blog Post: Motley says: "Code comments are for sissies"

    Summary Motley: My code is so readable and self-documenting that comments are unnecessary. Maven: Comments should address the intent (the why ) behind the code, not the how . Extraneous comments around how may indicate refactoring opportunities. ______________________________ [Context...
  • Blog Post: Motley says: "Refactoring means no more up-front design"

    Summary Motley: Refactoring keeps my design clean from the start, so no more up-front design! Maven: Up-front design is still necessary to achieve clarity on the overall approach (preventing rework later) and needs to be documented to allow others to review your thinking. ______________________________...
  • Blog Post: Motley says: "Test both private and public methods"

    Summary Motley: To get high code coverage, we should be testing both public and private methods Maven: Only test public methods. Testing private methods gets in the way of refactoring ______________________________ [Context: Maven checks in on Motley's unit testing practices and...
  • Blog Post: Motley says: "Refactoring is too hard - it's not worth the effort"

    Summary Motley: Every time I make a change in refactoring I either cause compile problems or break functionality. Refactoring is slow and not worth the effort. Maven: Use tools to refactor and leverage unit tests to improve your confidence that your refactoring does not break functionality...
  • Blog Post: Motley says: "I don't have time to Refactor - I need to get it right the first time"

    Summary Motley: Refactoring takes too much time - I have to ship you know! Maven: Refactoring leads to much more maintainable code, and if you have tests in place, the return on investment far outweighs the cost. ______________________________ [Context: Motley has just embarked on...
  • Blog Post: Motley says: "I can't write tests before application code - there's nothing to test."

    Summary Motley: You can't possibly write tests before code - there's nothing to test. Maven: Writing tests for a method before coding it has all kinds of design advantages. ______________________________ [Context: Motley has been writing unit tests for a week. Maven wants to take...
Page 1 of 1 (6 items)