Agile programming
Sure, the TDD cycle is red-green-refactor but what exactly are we refactoring? We just wrote the code, it’s green, and it seems reasonable to us. Let’s move onto the next test. We’re have a deadline, remember? Whether we’re working with code we just wrote or opening up a project for …
“Fat models” cause maintenance issues in large apps. Only incrementally better than cluttering controllers with domain logic, they usually represent a failure to apply the Single Responsibility Principle (SRP). “Anything related to what a user does” is not a single responsibility.
Though refactoring tools have been available for more than a decade, research has shown that programmers under-utilize such tools. However, little is known about why programmers do not take advantage of these tools.
Most developers know enough about refactoring to write code that’s pretty good. They create short methods, and classes with one responsibility. They’re also familiar with a good handful of refactorings, and the code smells that motivate them.
Have you ever wondered if there was a better way to learn refactoring? Martin Fowler’s Refactoring book was a great introductory book on how to clean up legacy code bases, but over the years, what I have found missing in that book is one a set of guidelines that links …
All too often programmers get into a productive rhythm where they receive their requirements, write tests aligned to those requirements, and then look for the green and red. While this process is proven to be highly effective, it can lead to developers missing the mark, as they aim for functional …
