At work

I'm a Solutions Architect and hands-on technical lead at Siemens.

Most days I move between architecture diagrams, .NET code, Azure infrastructure, APIs, identity systems, and the occasional production problem that suddenly becomes everyone's priority.

Lately, I've been spending less time thinking about individual services and more time thinking about how software gets built. I'm particularly interested in reducing the distance between an engineer having an idea and that idea safely reaching production.

Thinking about

AI-assisted software development, platform engineering, event-driven architecture, and developer experience.

I've been experimenting with workflows where AI agents can understand a codebase, implement changes, run tests, investigate failures, and explain what happened.

I'm not convinced this is the future of software engineering yet. I'm convinced it's worth exploring.

More broadly, I'm interested in the gap between generating code and building good software. The two are not the same thing.

Building

I keep building small things.

Some become products. Some become experiments. Some become GitHub repositories that quietly collect dust for a few months.

One of the projects I'm exploring is MIGRAPATH, an experiment focused on helping people evaluate immigration paths and understand what moving to another country might actually look like in practice.

I'm also investing more time in writing and documenting what I learn, using this website as a place to think in public.

Outside work

I live in Portugal.

I'm trying to spend more time building things that are interesting, not just things that are useful.

These days I'm learning, writing, experimenting with AI, and figuring out what the next chapter of my career should look like.