Approach
I work as a systems integrator. I come into complex, often messy technical environments, diagnose problems quickly, and build robust, maintainable solutions.
How I think about the work
Understand before building.
I don’t apply pre-made solutions or frameworks blindly. I invest time in understanding the real problem, the constraints (technical, human, and organizational), and what “success” actually looks like two or five years from now.
Simplicity as a deliberate choice.
I’m strongly influenced by Unix philosophy: small tools that do one thing well, composability, and avoiding unnecessary complexity. The most elegant systems I’ve seen are usually the ones that stayed simple enough to be understood and modified years later.
Long-term maintainability over short-term wins.
Quick hacks that “work now” have a compounding cost. I prefer solutions that remain understandable and changeable by future developers (including future me). This often means clearer code, better documentation, and resisting the urge to over-abstract too early.
Pragmatism, not purity.
I love clean architecture, open source, and well-designed protocols. But I’m not dogmatic. If Odoo, Django, or another established tool is the pragmatic choice for a real client with real constraints, I’ll use it properly, extend it cleanly, and integrate it thoughtfully with the rest of the ecosystem.
Root cause focus.
Many problems that look like “software issues” are actually symptoms of deeper architectural, process, or communication problems. I try to address the cause, not just patch the symptom.
This approach has served me well across many different projects — from ERP integrations and custom backend systems to security tooling and, more recently, sovereign digital infrastructure on IOTA Rebased.
I don’t position myself as a specialist in one narrow technology. I’m good at connecting technologies and making them serve actual human and business needs reliably over time.