I recently published a personal reflection about something I did not expect to connect so strongly:
Karate and engineering leadership.
As of writing the article, I have practiced karate for more than 20 years. For a long time, karate was karate, and work was work.
But over time, especially around architecture, migrations, incidents, and team leadership, I started seeing the overlap.
A few ideas from the article:
Pressure reveals training
In engineering, incidents and migrations do not usually create the real gaps.
They reveal them.
- Ownership gaps
- Missing context
- Hidden assumptions
- Unclear flows
- Places where people are afraid to say “I don’t know”
That reminded me a lot of training.
Under pressure, you do not always get to choose how you react. You fall back to what was actually practiced.
Simplicity is not shallow
In karate, a basic movement can look simple from the outside.
But after years of practice, you realize that simple does not mean easy.
I think good architecture is similar.
The best architecture is not always the most advanced one. Sometimes it is the one people can actually understand, operate, and improve.
Always be a student
One sentence my sensei often says stayed with me:
תמיד תהיה תלמיד
Always be a student.
For me, this became a leadership lesson.
Being responsible for something does not mean pretending to know everything.
It means caring enough to keep learning.
And it also means creating enough trust so others can say:
I do not know.
I am missing context.
I need help connecting the dots.
Because if I do not know what is missing, I cannot help.
The full article
I wrote the full reflection here:
Would love to hear how other engineers think about this.
What is something outside of software that shaped the way you write code, lead teams, or think about systems?
SOCIAL SHARE CARD GENERATOR