One of the big values Deep Roots provides organizations is the ability to target the exact need a development team has with a non-disruptive habit shift of very specific behaviors.
This saves days and even weeks of production time for putting teams through technical training that universally teaches concepts that may or may not apply to the team’s impediments.
Team simply choose based on the technical problem they are experiencing. Even though you could have 10 teams taking the Fix God Classes Change Series, each team could be focusing on a different habit within that Change Series, depending on the team’s god class issue.
This video walks through a series of those painful results from when developers receive universal training on a technical solution, and a way that teams can get the learning that is relevant to their immediate problems.
No Bundling Policy
Because Deep Roots recognizes the need for relevancy, we absolutely do not bundle habits to be in a particular sequence or requirement before the technical need is understood. Each team is likely to need a set of habits, but that set is dependent on each team’s needs, and may not be relevant to the next team.
So Why Bundle the Insight Loop?
Every developer benefits from the practices of The Insight Loop. These fundamental shifts in coding behavior make reading easier and reduce your bugs regardless of the code or problem. Once that has been established, then other more problem-specific Change Series can be adopted by teams. This is the one and only pre-requisite before teams select the habits that are relevant to their needs.
Insight Loop: Habit 1
This particular habit is necessary as a foundational way for developers to ensure any code change is cheaper to make and reduces bugs … immediately.
Direct results of Habit 1: Start Refactoring Safely
- team can review your code in minutes instead of a day
- team will know which code reviews require attention
- you will introduce fewer bugs on the most common refactorings
- you become more aware of the risks that lead to bugs
- you will start building trust with managers and product owners that refactoring can be cheap and safe
Insight Loop: Habit 2
This habit builds on Habit 1 by making the names more effective. As a result the costs and bugs for any story continues to reduce.
Direct results of Habit 2: Naming as a Process
- you will be able to trust the names in your team’s code
- you will spend less time coming up with names
- you will waste less time hunting for experts on code you don’t understand
- you will have less code to read and understand for each story
Insight Loop: Habit 3
And finally, this third habit integrates all of the technical practices developed so far by fine-tuning those practices to the point where developers can be trusted to do just enough of the right refactoring in each story, thereby minimizing the story cost.
Direct results of Habit 3: Knowing When to Stop
- you will finish code reviews more quickly
- you will be less impacted by interruptions
- you will complete stories more quickly
- you will establish trust with your product owner that you are refactoring the right amount
- you will find it safer and easier to work with code you do not understand
- you will find yourself struggling less to keep everything in mind