Loading...
I build products that work under real-world constraints. Here's what that means in practice.
Most of my work happens in environments with limited time, unclear requirements, or unreliable data. I've learned to make decisions that are good enough to move forward, while leaving room to adjust.
See how I handled bad data in DólarGaucho →Before building, I understand how pieces connect. This means fewer surprises later, better architecture decisions, and systems that scale without rewrites.
See my approach to technical systems →Writing code is the easy part. Understanding what to build, why it matters, and how to validate it—that's where I focus. The goal is impact, not output.
See how I think about product decisions →Every decision has costs. I make those visible, so stakeholders can make informed choices. No hidden tech debt, no 'we'll fix it later' without a plan.
See real trade-offs I've documented →I'm open to interesting projects where I can own outcomes, not just write code. If you have something that needs building under real constraints, let's talk.