culture

There's a powerful idea here: I'm not saying "this is who I am", I'm saying "this is what I practice".

Values aren't certificates hanging on the wall. They're forces that pull you when you're tired, stressed, or in a bad mood, right when we lose our way, when it's hardest to be the version of ourselves we want to be.

So this isn't just who I am. It's who I want to become, what I'm building in myself.

The way I work didn't appear out of nowhere. Early in my career I paid close attention to teams that built software the way I wanted to build it. Small, focused groups that proved engineering excellence, thoughtful design and a great product are not opposites. They pull in the same direction.

But borrowing a list of values means nothing until you've actually lived them. These four aren't quotes on a wall. They're the ones I keep coming back to, in my own work:

• default to transparency

  I'd rather say "I don't know yet" or "I broke this" out loud than hide it. Clear beats comfortable.

• be a no-ego doer

  The best idea wins, even when it isn't mine. I'd rather ship the right thing than be right.

• improve consistently

  Not heroic sprints. Small, repeated steps. The frontend I write today should embarrass the one I wrote last year.

• show gratitude

  Good products are built by people. I try to name them, thank them and remember that none of this is solo work.

These values show that I don't just care about building software. I care about how I build it and who I become while doing it.

This isn't an "about me" section. It's my way of defining how I want to work, how I want to treat people, and how I want to grow while building software for the real world.

Shaped early on by teams I admire like Buffer (opens in new tab) and Unsplash (opens in new tab), then made my own since.