Pragmatism over perfectionism
Ship working software, iterate based on real feedback

I build systems, pipelines, and cultures that let engineering teams move fast with confidence. Starting as a self-taught developer with a business background, I've learned that speed without safeguards is reckless, but safeguards without initiative is gridlock. I create the conditions for both—psychological safety, automated testing, clear ownership—so teams can ship, learn from failure, and improve continuously.
Building modern web applications with cutting-edge technologies and best practices
Implementing CI/CD pipelines and infrastructure as code for reliable deployments
Designing and deploying scalable, resilient cloud solutions across major platforms
Mentoring developers and fostering engineering excellence in collaborative environments
Ship working software, iterate based on real feedback
New tools are exciting, but solid engineering principles endure
The best engineers create environments where others succeed
Technology changes constantly; staying curious is essential
I learned to code by building things—websites, applications, and tools. My Business Administration degree in Marketing gave me the business perspective to balance my passion for web development and open-source tools. As Seth Godin wrote in Poke the Box: “All it takes is initiative. Even just a bit.” I grounded this phase in XP and agile principles, creating environments for rapid iteration and experimentation—where automated testing and safeguards enabled teams to move fast with confidence and keep learning.
As I grew, I became obsessed with how organizations consume technology. Instead of contributing to projects, I focused on translating powerful open-source tools for teams who needed them—establishing patterns, writing documentation, mentoring engineers. This shift from “do the work myself” to “help others do the work” multiplied my impact.
My role evolved into system-wide concerns: designing platforms for scale, building reliable deployment processes, establishing SRE practices that improved uptime and reduced incident response time. I led initiatives like:
Today I’m at the intersection of traditional engineering and AI. I’m working with AI-powered development tools—exploring how LLMs can augment (not replace) skilled engineers, building AI features into production applications, helping teams adopt these tools without losing sight of reliability and maintainability.
I’m excited about AI’s potential, but I’m more interested in fundamentals: Can we still reason about systems? Can we write maintainable code? Are we building something that lasts?
Let's build something amazing together!