Architecture & System Design
You have requirements, constraints and a vague idea of where you're going. I turn that into a system with clear boundaries, explicit trade-offs and decisions you can actually build on.
I TURN COMPLEXITY INTO STRUCTURE
Complex systems rarely fail because they're too complex. They fail when nobody understands what actually matters.
I help engineering teams make sense of difficult systems, make hard technical decisions, and build software that holds up in the real world.
↓ KEEP READINGWHEN EVERYTHING IS CONNECTED, NOTHING IS OBVIOUS
Requirements. Constraints. Legacy decisions. Distributed systems. Real-time data. Hardware. Protocols. Performance.
Everything affects everything else.
And that's where things usually go wrong.
The hardest engineering problems aren't solved by writing more code.
They're solved by understanding the system well enough to know what code should exist in the first place.
I HELP TURN TECHNICAL UNCERTAINTY INTO SOMETHING YOU CAN BUILD
Systems Diagnosis
Something works. But nobody really knows why. I dig into difficult existing systems, find the real constraints and separate symptoms from the problems underneath them.
Engineering Rescue
The system has become painful. Changes are risky. Performance is unpredictable. Nobody wants to touch certain parts anymore. I help make it understandable again — and give the team a way forward.
I DON'T START WITH TECHNOLOGY
Ambiguity
Understanding
Structure
Decisions
Engineering
Reliable System
Because choosing a technology is easy.
Knowing what the system actually needs is the hard part.
REAL SYSTEMS. REAL CONSTRAINTS
I don't believe architecture should be discussed in a vacuum. These are some of the systems I've actually built and evolved.
AKVAKT
Designing a platform from zero.
Industrial edge systems running at customer sites. Real-time data. Constrained hardware. Industrial protocols. Remote operation.
A platform had to emerge from all of those constraints — without turning every new customer into a new codebase.
Read the story →CIXOR
Making a difficult system incremental.
Large workloads. Distributed processing. Operational complexity.
The challenge wasn't simply making it faster. It was changing how the system processed work without breaking everything around it.
Read the story →I WRITE DOWN THE DECISIONS BEHIND THE SYSTEMS
Not tutorials. Not lists of technologies. Not “10 things I learned this week”.
Technical stories about real systems — what made them difficult, what decisions were made, what went wrong, and why the architecture ended up the way it did.
Explore the Engineering Notebook →ABOUT
José María Sánchez Salas
Software Engineer & Architect
Around eight years building and evolving complex systems — from backend platforms to industrial edge environments.
I tend to end up where the system has become difficult to understand.
That's usually where the interesting engineering starts.
More about me →HAVE A DIFFICULT SYSTEM?
Good. That's usually more interesting than starting from scratch.
If your system is hard to understand, your architecture needs direction, or an engineering problem has become difficult enough that someone needs to take ownership:
Let's talk.
Send me an email →