Browse by Tags
All Tags »
refactoring (RSS)
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. ______________________________
Read More...
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
Read More...
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
Read More...
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
Read More...
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:
Read More...
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
Read More...