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 …
Tag: refactoring
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 …
Redmine Refactor #96: Merge Method in IssuesController
To wrap up this week’s refactoring of IssuesController, I used merge method to merge the #update_form action into #new. The #update_form method is an Ajax endpoint that is used to refresh an issue form’s fields. For example, when an issue form changes from Bug to Feature it needs to load the fields for a Feature. …
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, …
Redmine Refactor #95: Extract ContextMenusController from IssuesController
Using extract class on the IssuesController, I was able to create another controller called ContextMenusController. This controller will handle Redmine’s right click context menu that is used on the issues list. Before 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 …