On growing into leadership
I learned to program by moving fast. For a long time, speed was how I solved problems, learned new things, and got results.
In group settings, that same speed started to have side effects.
When speed becomes influence
When people have different levels of experience, the fastest person often takes the lead without meaning to. Decisions get made quickly. Problems disappear. The work moves forward.
At first, I saw that as a strength.
Over time, I noticed what it took away:
- Others had less space to think
- Learning happened unevenly
- Ownership slowly narrowed
- The team worked, but depended too much on one person
The turning point
That was the turning point.
I didn't need to slow down because I became less capable. I needed to slow down because the goal changed. From finishing things myself to building something others could grow in.
That meant learning restraint:
- Explaining instead of fixing
- Letting someone struggle a bit longer instead of stepping in
- Accepting slower progress when it led to stronger people
The work still gets done. But now it moves through the team, not around it.
The shift
Feedback I've received over time reflects that shift:
- That I work well in groups
- That I help others learn
- That I think along and support the team where needed
I don't read that as praise, but as confirmation that the balance is improving.
"Keke is a great developer. He enjoys helping others and demonstrated excellent teamwork during our collaboration at Fontys."
"Keke is a good developer. In group settings, he works very well together and ensures everyone learns from each other."
"I have worked with Keke multiple times on school projects and a hackathon, and he is a strong developer. His knowledge of backend and web development is broad, and he knows how to come up with efficient and scalable solutions. Additionally, he is a pleasant colleague who always thinks along and helps the team where needed."
"Keke is a 10x developer, always thinks along and comes up with good solutions. Through his work, we were able to deliver a particularly comprehensive project at Fontys!"
Building alone rewards speed. Building with others requires patience and trust.
If a team only works when one person pushes, it isn't finished yet. Real progress is when things keep moving even after you step back.