Builder & Maker

I try to understand
things deeply
before building them.

I build software. But more than that, I try to understand the problems people actually have — and build things that genuinely help. Slowly, carefully, with intention.

How I think
A quiet, thoughtful moment

How I think

A few things I actually believe.

  1. 01

    Understand before you build.

    The most expensive mistake in software is solving the wrong problem well. I spend more time than most in the question — reading, talking to people, sitting with the discomfort of not knowing — because the best solutions emerge from real understanding, not from rushing to code.

  2. 02

    Failure is information, not verdict.

    I've shipped things that didn't work. I've made bets that didn't pay off. Each time, I learned something specific — about the problem, about people, about my own assumptions. I try to hold failure lightly enough to learn from it, and seriously enough to not repeat it.

  3. 03

    Build things that are genuinely useful.

    There's a kind of software that impresses at demos but doesn't help anyone. I'm not interested in that. I want to build things that actually change something in someone's day — that make a hard thing easier, a confusing thing clearer, a lonely thing feel less so.

  4. 04

    Confidence comes from evidence, not posture.

    I don't claim expertise I haven't earned. When I know something well, I'll say so. When I don't, I'll say that too — and then go figure it out. Real confidence isn't about having all the answers. It's about trusting yourself to find them.

Work

Cimientos — building foundations, step by step

Cimientos

Ongoing

People can change when they start building evidence that they can trust themselves.

Cimientos started from a belief I kept returning to: the hardest part of building new habits isn’t motivation — it’s identity. People struggle to change because they don’t yet have proof that they’re someone who can.

I built Cimientos to help people collect that proof. Small actions, tracked honestly, over time. Building it taught me as much about human psychology as it did about software — which was, I think, the point.

Visit Cimientos →

What I learned

Simplicity is earned, not assumed.

Status

In active use

I work on other things too — some public, some private, some still half-formed. If you want to talk about what I'm building, just reach out.

Let's talk

About

Understanding people and understanding systems are more connected than they seem.

I grew up curious about how things work — not just machines and code, but people, decisions, organizations. That curiosity never went away. It just found a home in software, where understanding the human side of a problem is as important as the technical one.

I learn best by doing, and doing badly first. There's something in the stumbling that sticks — the lessons you earn through failure are the ones that actually change how you think, not just what you know.

I care about building things with integrity — things that do what they promise, that respect the people using them, that I'd be comfortable defending in five years.

Contact

If you think we could build something interesting together, I'd love to hear from you.

Not a pitch. Not a brief. Just a conversation.

Say hello