I am a software architect and tech lead who found purpose at the intersection of code, people, and creation. After years searching for something that truly motivated me, I found it in entrepreneurship — the kind of challenge that makes me wake up eager to start the next implementation. My family is where I find the energy to keep going.
I’m 33 years old, based in São Paulo, and I lead engineering at 4Tech — a software company I built on the belief that technology exists to give people back their time and autonomy. Our customers trust us with complex software challenges; I lead architecture and delivery in healthcare and other regulated industries, which keeps me connected to the real complexity of enterprise software.
What I do
My work lives at the boundary between architecture and delivery. Before writing a single line of code, I want to understand the domain, the couplings, and the constraints. Architecture comes before implementation.
For most of my career I’ve written code. Today, my work is designing complex solutions that span multiple areas of knowledge. My focus is building architectures that optimize cost in environments where budget and constraints are real.
At 4Tech, I’m integrating AI into the engineering team’s workflow to improve productivity and delivery quality. The biggest challenge is training developers to use AI as a genuine tool without weakening their computer science fundamentals.
What drives me
I believe knowledge only has value when expressed. I learn through the CODE method — Capture, Organize, Distill, Express. A concept becomes mine when I turn it into something: a post, a project, a talk, a solution for a client.
I’m fascinated by systems that learn and adapt. AI agents, genetic algorithms, microservices that evolve with the business. I see patterns in nature and in technology as faces of the same logic.
My intellectual lens is that of a pragmatic architect. Theory disconnected from practice doesn’t interest me. Neither does practice without solid theoretical foundations. What drives me is the space between the two — the moment a concept becomes something that works.
Why I write
I want to sharpen my English and my writing in general, and this blog is part of that practice. I also hope to become a speaker one day, and the notes I keep in Obsidian are the foundation I’m building toward that.
This is where I think out loud. About architecture decisions, AI systems, leadership, and the lessons from building products that actually run in production. Not demos. Not theory for its own sake.
I write to organize my thinking. And when the thinking is organized, I share it.
“Writing is not about using difficult words to impress. It is about using simple words in an impressive way.”
— Sierra Bailey