I last talked about how wild estimates affects a team with unfactored code. Now I want to look at another impact on the team that is even more dangerous. Lowered morale In order to produce a great application, every team needs to work as a team. They should want to help each other and go …
Redmine Refactor #98: Extract method from IssuesController#bulk_edit
After thinking about how IssuesController#bulk_edit works, I decided to leave it in IssuesController. It doesn’t match Rail’s REST conventions but it does match the REST principles for resource representations. IssuesController returns representations of issue collections and issue objects. Since #bulk_edit works on an issue collection, keeping it in the IssuesController makes sense. There still is …
Redmine 1.0.1 released
Redmine 1.0.1 has been released this past weekend.
Redmine Refactor #97: Move method from IssuesController to JournalsController
Starting a fresh week, it’s time to finish up refactoring IssuesController to remove the last of the extra actions. Using move method I was able to move the #changes method to the JournalsController. Before 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 class IssuesController …
Problems when you don’t Refactor Rails: Wild Estimates
I’ve looked at two problems that are caused when you don’t refactor, code duplication and test duplication. Both of these are mainly technical problems that affect developers. Today I want to look at a problem that affects project managers and everyone else on a team, wild estimates Wild Estimates When an application is well refactored, …