I'm Alexandru Dancau, a software engineer focused on backend systems, and beyond.
Still curious
Software engineering is a passion for me, especially the architecture behind it: how components fit together, where responsibilities belong, and how a system evolves.
I enjoy thinking through those decisions and their trade-offs, from keeping a module simple to handling dependencies and failures.
AI helps me explore ideas faster. I still want to understand why a design makes sense and what it will mean for the people maintaining it.
This blog is a place to explore those questions and share what I learn.
Thinking in systems
I'm especially interested in the decisions around the code.
Where should a module's responsibility end? Which parts of a system need to change together? What happens when a dependency fails?
Sometimes a clear boundary inside one application is enough. Sometimes a separate service makes sense. I want to understand the reasons and the costs behind those choices.
Those are the architecture questions I'd like to explore here, with concrete examples and a look at the trade-offs involved.
Why this blog
I'll share notes on Java, Spring Boot, Frontend, DevOps, software architecture, and beyond.
Expect practical examples, decisions, and lessons from things that didn't work.
Writing helps me understand things better. I hope these notes help someone else, too.