Thinking about how @KentBeck wrote Smalltalk Best Practice Patterns — he went meta at every step of real work and asked “What did I just do? Have I done this before?”
Trying the same on some shaping work. Not just sketching, but annotating each false step and corrective measure.
-- Ryan Singer
For me, these two questions are not enough.
The ability to reflect correlates with the skill of a person.
How to gather information?
Do micro-steps and micro-commits in Git. Reflect on every commit on the questions above and link them with the commits. If it is a side-project I may want to write directly in the commit messages.
This exercise is useful in a side-project AND katas AND especially the real world.
It will slow me down in the short run but accelerate me in the long run.
Trying the same on some shaping work. Not just sketching, but annotating each false step and corrective measure.
-- Ryan Singer
For me, these two questions are not enough.
- Why do I do the task and nobody else - like a library programmer?
- What am I doing right now?
- Why now?
- What did I do it before, what next?
- Why I am doing what I am doing right now?
- How do I do it?
- Why does it the way I do it? Would an alien do it other?
- What would the alternatives be?
- What is the broader context of the current step?
The ability to reflect correlates with the skill of a person.
How to gather information?
Do micro-steps and micro-commits in Git. Reflect on every commit on the questions above and link them with the commits. If it is a side-project I may want to write directly in the commit messages.
This exercise is useful in a side-project AND katas AND especially the real world.
It will slow me down in the short run but accelerate me in the long run.
Comments
Post a Comment