Origin
ARC emerged from practice. Not as a product, but as a name for a pattern that kept repeating.
After years of working in and leading engineering teams, certain patterns kept appearing across the industry: systems that start clean but drift into chaos. Speed was the goal, but coherence was the casualty.
I tried every methodology, every framework, every best practice. Agile gave us velocity but no direction. Clean architecture gave us theory but no practice. Something was missing.
When AI coding assistants arrived, they amplified everything: both the good and the bad. Without explicit architecture, AI just accelerated the chaos. That's when I realized what was missing.
ARC wasn't designed in a vacuum. It emerged from watching what worked and what failed. Align, Realize, Consolidate: a recursive pattern that operates at every scale.
Beliefs
Patterns Over Processes
Methodologies should reveal patterns, not impose processes. The best frameworks help you see what's already there. They don't force you into boxes.
Explicit Over Implicit
The biggest source of technical debt is implicit decisions. When architectural choices live only in people's heads, they leave when those people do.
Coherence Over Completeness
A smaller, coherent system beats a larger, fragmented one every time. It's better to do less with intention than more without direction.
AI as Amplifier
AI doesn't create problems or solutions. It amplifies what's already there. Give it chaos, get more chaos. Give it coherent patterns, get coherent code.
Speaking
Available for conferences, meetups, podcasts, and technical interviews.
Topics include post-Agile thinking, AI-assisted development, software architecture, and neurodivergence in tech.
Languages: English, Spanish, and Galician.