How I
actually work
The methodology behind the results. These aren't buzzwords — they're the principles that have delivered real-time pipelines, prevented illegal operations, and built teams that run without me.
Why your problems keep coming back
Imagine your accounting department only kept the final balance. No transaction history. No audit trail. Just a number that changes mysteriously every month. When the auditors ask "why did this change?", nobody can answer. That's what your IT department does. Every day.
CRUD / Traditional
→ When something breaks, you're blind.
→ "What changed?" → Nobody knows.
→ New employee → 5 weeks of John's time.
→ Same bug, different costume, every quarter.
Event-Sourced
→ When something breaks, you replay the tape.
→ "What changed?" → Here. Exactly this. At this time.
→ New employee → one link.
→ Bug found once. Fixed permanently.
At Hornbach, I improved their pipeline 1000x. But the real tragedy? The right architecture would have been 1,000,000x — and 100x cheaper than my fix. That's not hindsight. That's 13 years of pattern recognition.
Engineering Principles
Observability before optimization
Never optimize what you haven't measured. I instrument systems first — latency, error rates, resource saturation — then fix what the data reveals. Guesses are expensive; metrics are cheap.
Strong types, not runtime prayers
I design systems where impossible states are unrepresentable. If the compiler can catch a bug, it should. Bugs that can't exist don't need fixing.
Composition over inheritance
I build from small, composable pieces that can be tested independently and replaced when needed. No deep class hierarchies that become maintenance traps.
Contracts at every boundary
Strict, typed interfaces between systems and modules. Internal implementation is free to evolve; the contract is the stable surface that consumers rely on. Breaking a contract is a deliberate, versioned act.
Idempotency and explicit state
Operations are safe to retry. State transitions are visible and auditable. No hidden side effects, no "it depends on timing" bugs — just predictable, reproducible behavior.
Your systems have no memory
Imagine your accounting department only kept the final balance — no transaction history, no audit trail. That's what most IT departments do. When something breaks, your team is a detective in a dark room with no witnesses. Event-Sourcing turns on the lights: every decision recorded, every state change auditable, every bug traceable.
Depth is the moat, AI is the amplifier
13 years of deep engineering, architecture, and infrastructure knowledge across Fortune 500 engagements. AI doesn't replace that — it amplifies it. Together with Event-Sourcing thinking, that's why one person can deliver at the speed of a 10-person team.
Credentials
Experience
13+ years of professional software engineering
AI-amplified engineering workflows for 10x delivery speed
Started programming at 10 years old
7+ countries led teams across
Certifications
Certified Professional for Software Architecture — Foundation Level
iSAQB® · Mar 2023
Oracle Certified Associate Java SE8 Programmer
Oracle · Apr 2019
Education
Autodidact (Homeschooled)
2014 – 2018 · France
Full-time self-directed education covering software engineering, system architecture, geopolitics, finance, and law. Built a deep, cross-disciplinary foundation that informs architectural decisions today. No degree. No apologies.
Focus: Computer Science, Finance, Law, Geopolitics