From Senior Analyst to Systems Builder: 30 Years of Evolution
A reflection on three decades in technology, from corporate complexity to the freedom of building modular, simple, and sustainable systems.
Completing 30 years in technology is not just about accumulating programming languages, job titles, or certifications on a resume. It is, above all, an exercise in unlearning. I started in a time when infrastructure was physical, expensive, and heavy. Today, I see that the greatest sophistication is not in the most complex system, but in the one simple enough to maintain without pain.
In this article, I share how I stopped seeing myself only as a “senior analyst” and embraced an identity that better matches what I do today: Systems Builder.
The weight of legacy and the cost of complexity
For decades, the market taught us that “big” meant “better.” Big servers, big frameworks, big teams. In the corporate world, complexity often appears as a sign of maturity, but its cost can be paralysis.
I saw good systems become hard to evolve because of their own architecture. I learned that the code you write today can become the technical debt you pay tomorrow. Because of that, my view changed: instead of building monolithic cathedrals, I started preferring tools that solve real problems without creating new maintenance problems.
Technical maturity arrives when you stop being impressed by complex solutions and start admiring the elegance of simplicity.
Modularity as a life philosophy
Whether building Lego with my daughter, configuring a guitar pedalboard via MIDI, or structuring this content pipeline with Astro and n8n, the principle is the same: modularity.
A modular system lets you swap pieces without breaking the whole. If my editorial backend, currently Baserow, fails, the Astro site stays online. If I want to change how translations are done, I only change one automation module. This view of pieces that fit together reduces dependency, improves maintenance, and leaves room for experimentation.
The birth of the Systems Builder
The term “Senior Analyst” describes part of what I know. “Systems Builder” better describes what I do. A builder does not wait for the perfect environment; he builds the lab. He does not just consume tools; he creates the infrastructure that makes it easier to test ideas.
Being a Systems Builder in 2026 means mastering the art of orchestration. It is knowing when to use AI, when to use Docker, when to automate, and when to go back to the basics of HTML and CSS. It is understanding that technology must serve the purpose, not the other way around.
What I carry into the next phase
Technology will continue to change quickly, but some fundamentals remain: curiosity, faith, family, and the will to build. My current lab is the beginning of a phase focused on creative freedom, operational efficiency, and systems I actually understand.
The invitation I make, whether you are just starting or already carrying decades of road behind you, is simple: do not be only a user of systems. Learn to build your own.