I'm a software engineer who traded hard hats for hard bugs. I build backend systems, service integrations, and tools that make complex workflows feel simple.
Before code, I worked in mining and construction. That background taught me to think in systems, respect constraints, and always have a fallback plan.
I'm always learning, always tinkering, and occasionally talking to my code like it owes me money.
Languages & Frameworks
Data & Databases
Tools & Integrations
Creative
- π APIs & Integrations β designing resilient service connectors, rate-limit handling, retry strategies
- ποΈ Backend Architecture β clean patterns, system design, and making things scale
- π§ͺ Automation β if I do it twice, I write a script; if I do it three times, I write a good one
- π Always learning β currently going deeper on system design and performance optimization
A bit more about me
I went from mining rocks to mining data - now I craft with code instead of concrete.
My path into software wasn't the traditional one. I came from an industry where things are heavy, slow, and very physical. That contrast is exactly what drew me to programming: the ability to build fast, iterate faster, and ship something that exists purely as an idea made real.
Things I enjoy outside code: 3D modeling in Blender, tinkering with automation for everyday life, and the occasional existential conversation with a stubborn bug.
Ask me about: Python, Flask, API integrations, automating repetitive tasks, or how many cups of coffee it takes to debug a race condition.
