Software Engineer
In pursuit
of good systems.
I'm Manuel Desole — software engineer focused on the whole picture: the problem, the architecture, the product, the craft. Built end to end, with intent.
Selected Work
Problems I've owned.
Case studies coming soon.
How I Think
Four principles.
The problem before the stack.
Tools change every year. The discipline of understanding what you're actually solving doesn’t. I start there — using domain discovery, value mapping, and mental models to define the real problem before touching code.
The system before the feature.
A feature shipped on a fragile foundation creates two problems instead of solving one. I build with vertical slicing, horizontal decoupling, and the 4-tier architecture — so every feature lands on a system that scales, tests, and evolves.
Ownership is end to end.
Product, architecture, and craft are not separate disciplines handed off between roles. They are one practice — and I treat them as such by owning the feedback loop: from user story to deployment, from test to production.
Craft is non-negotiable.
How something is built shows in how it ages. I care about the parts no one will ever see — encapsulation, composition, subject verification — because eventually, they always do. And that’s where maintainability lives.
Writing
Notes on the craft.
Nothing published yet — check back soon.
About
The person behind the work.
I'm Manuel. I started writing code because I wanted to solve problems, and I kept doing it because I discovered the problems I cared about weren't really about code at all — they were about systems, decisions, and craft.
Today I work as a software engineer with a deep interest in product ownership and architecture. I believe the best software is built by people who refuse the artificial boundaries between thinking, designing, and building.
When I'm not at a keyboard, I'm usually reading about systems — software, organisational, or otherwise — or somewhere outside, walking.
Contact
Working on something
worth building?
I'm always open to conversations about systems, products, and craft — whether it's a role, a collaboration, or just a good question.
info@madnol.dev