Yes, it makes sense to granularize when you are first learning, and when you run into problems (troubleshooting), but not once you’re already familiar with the process. When you’re not in learning mode, you want to consolidate as much as possible.
The software analogy is the difference between trying to run a program line by line in a debugger (pressing F8 for Step Into or what have you) versus just running a compiled or bytecode optimized version. Even worse is trying to type every line from hand into an interpreter every single time.
I understand your point, but a seemingly ridiculous amount of granularization can still be very useful if you can group certain steps. That way, you can collapse and expand sections of hierarchies as needed. You can also find new ways of doing things.
Yes, it makes sense to granularize when you are first learning, and when you run into problems (troubleshooting), but not once you’re already familiar with the process. When you’re not in learning mode, you want to consolidate as much as possible.
The software analogy is the difference between trying to run a program line by line in a debugger (pressing F8 for Step Into or what have you) versus just running a compiled or bytecode optimized version. Even worse is trying to type every line from hand into an interpreter every single time.
I understand your point, but a seemingly ridiculous amount of granularization can still be very useful if you can group certain steps. That way, you can collapse and expand sections of hierarchies as needed. You can also find new ways of doing things.
Here is a more positive example of granularization and reconsolidation applied to everyday actions.