BLACK BELT.
ENGINEER.
HACKER.
AUTODIDACT.
I have worked as a software engineer for more than fifteen years. I have practiced Brazilian Jiu-Jitsu since 2013 and have held a black belt for five years. None of those titles is what matters most. What matters is what happened between them, and why I ended up building what you are reading now.
I did not plan to build an editorial project. It emerged after years of asking the same question in different ways, until the question forced me to build an answer.
The question is simple: why do two committed practitioners, with the same time on the mats, develop at radically different rates?
The answer took me years to reach. It is more uncomfortable than most practitioners want to hear, and it became the thread running through everything I study and document.
The blue belt was where I almost quit
I was the kind of student every instructor wants. I showed up consistently. I arrived early and stayed late. I took notes, studied video, and competed when I could. Effort was not the problem.
But I was going backward. More honestly, I was stuck in a way that looked like slow progress, the worst kind of stagnation because it gives you enough evidence to keep avoiding the diagnosis.
What pulled me out was not a wise instructor, a revelation from a lecture, or a book that found me at the right time. It was a question I asked myself in the locker room after another round in which I “lost” to the same training partner, in the same way, for the third consecutive week.
If I repeat exactly what I am doing for the next five years, where will I end up?
The honest answer was: probably in the same place. Perhaps slightly better. Perhaps worse, because the body does not reward dedication when the method is structurally misaligned.
That was when the distinction became clear. The problem was not how much I trained. The problem was what I did inside that training time. More importantly, I had no way to diagnose the failure because no one had taught me to treat learning as a technical problem.
At work, this process has a name: debugging. Reproduce the problem, isolate the cause, change one variable, and test again. I had never thought to apply the same discipline to the mats.
There was an entire body of research no one had shown me
I began studying the neuroscience of learning with the same seriousness I brought to distributed systems architecture. Cognitive neuroscience. Sport psychology. Evidence-based pedagogy. Motor learning.
What I found was both clarifying and infuriating. There was a large, serious body of research on how humans acquire complex skills. Yet almost none of its distinctions had reached the ordinary conversation on the mats.
Across decades of research, Anders Ericsson studied deliberate practice and expert performance. Robert Bjork showed how desirable difficulties can reduce immediate performance while strengthening retention and transfer. Matthew Walker documented the role of sleep in motor-memory consolidation. Carol Dweck examined how beliefs about ability shape the response to error and long-term persistence.
None of them wrote a finished method for Brazilian Jiu-Jitsu. Their work exposed distinctions that the standard conversation ignored: performance versus learning, repetition versus transfer, information versus action, and effort versus practice architecture.
What followed was what happens when an engineer decides to treat a problem with method. Build. Test. Adjust. Document. Apply the ideas in training and observe what changes. Apply them in teaching and compare them with the standard model. Read original papers instead of popular summaries. Accept no conclusion without a mechanism.
The confirmation came from the students, not from me
The first serious indication that I was moving in the right direction did not come from my own development as an athlete. It came when I started teaching.
I rebuilt the structure of my classes. Fewer new techniques in each session. More structured variation inside every drill. Specific sparring with calibrated constraints. Mental debriefing beside the technical work. A practice architecture informed by what research shows, not maintained only because it is traditional.
The difference became visible over the following months. Students working with the method progressed at a rate that seemed out of proportion to their time on the mats. Not because they trained more, but because each session was designed to produce retention and adaptable skill.
That was when keeping the work private stopped making sense. If the method works, the honest response is to document it openly. For the practitioner trapped in the same plateau I faced. For the instructor who sees the limits of the standard model but cannot yet name them. For anyone who treats learning as a serious discipline, not as entertainment.
START WITH THE METHOD.
The story explains why the work began. The reading path starts with the diagnosis, then connects it to the three pillars of Protocolo da Mente do Tatame.
FOLLOW THE READING PATH →