Learn and share my knowledge rather than produce naively
This is the 5th post from my sincere dev manifesto series.
Dev requires dozens of practices.
- Mental models like cynefin or wardley mapping.
- DDs, like DDD, BDD, and TDD.
- Patterns and design smells.
- Refactoring techniques, from shortcuts to nanosteps.
- Activities for retrospective, event storming, example mapping, tres amigos.
- Postures, like ego-less programming.
- Mobbing and pairing.
- Communication patterns.
- Patterns for evolving designs.
- Limitations and features of the languages, libraries, frameworks, and tools, we use or don’t use yet.
These are just examples, and I’m far from being able to list, or even know, everything I need to learn.
In some American army I can’t find anymore, they say that under stress, soldiers don’t increase their capacity to a transcendent level, but decrease it to their training. Everyday, all of us need to improve our knowledge, and our muscle memory for our tools. We must repeat and multiply katas. We must read, view, discuss, share, or explore, knowledge, discoveries, points of views, experience from others, in similar or different contexts. We build great things on top of tiny bricks. We stand on the shoulders of giants.
Improving is part of our job. We must improve, for our collective mission and our employer, on our working time. We only learn a tiny bit of what we need to know in school, because what we need to know is huge, learning sometimes requires experience, scars, or previous knowledge, and technology and practices evolve at a terrifying and exciting pace.
Our employer must participate in this, because they need us to be good. If no company helps their employees get better, they won’t get magically better… and no company can hire good candidates, including yours. “But what if we train employees who then leave?”, they say. What if they don’t progress and they stay?
When I’m blocked at work, I read books, view talks, repeat katas, explore. Oh, from time to time I also write about what I learn, it helps cementing knowledge, mainly by putting words on thoughts. And I try to do all these so that everyone can see I’m not working on something else than the backlog. I encourage anyone doing the same.
I commit to taking the time to discover and share, and showing a good example in a way everyone can see.
AAAgile 
One comment