xaedes
Joined 12 years ago
Joined 12 years ago
When reading about nemawashi I immediately thought about its usage in software refactoring.
This is something you often intuitively do when making bigger refactors. Lay the foundations before actually doing it. Affected code parts and stakeholders should not be surprised by one big change. Instead they should be consulted before hand, building consensus, modify the planned big refactor itself and preparing the individual parts for it by small changes. Otherwise you will encounter a lot of friction, introduce bugs, etc.
It is very nice to have a proper term for this.
- unconscious incompetence
- conscious incompetence
- conscious competence
- unconscious competence
At first you are unable to do something, but you don't even know it. Then you learn about your incompetence and begin to work on it. Eventually due to conscious effort you achieve conscious competence. Doing it long enough you don't need to spend conscious effort to be competent - you just do it, and you do it well.
I think this unconscious competence is very similar to Wu Wei.
Maybe I am old-fashioned, but I still think humans should be able to do basic life actions without a smartphone.
Only 11.5% barely notice them or can completely tune them out. 88.5% are annoyed by them with varying degrees of annoyance.
But maybe I am confusing "Deutschlandtakt 2070" and the electrification of the tracks.
But remembering Battlestar Galactica, cutting the interconnectivity was the prominent defense against cylons.