Dare. Reason. Build. — Why This Blog Exists

I've watched brave founders bet everything on ideas they couldn't build, and brilliant engineers ship flawless solutions to problems that didn't matter. Same outcome, opposite causes: something was missing.

Dare. Reason. Build. is my name for what was missing — and the reason this blog exists.

This isn't a welcome post. It's a thesis. Most people treat courage, reason, and craft as three separate virtues — be bold, think clearly, execute well. I don't. I think they're one discipline, and the moment you drop any one of them, the whole thing tips over.

I've spent over a decade building software — React and TypeScript on the front, Node and GraphQL behind it, cloud and CI/CD underneath. Then I co-founded HiTerra, an AI-powered agri-tech platform working on carbon markets and MRV — measurement, reporting, and verification — for farmers. So I live this at the seam: the engineer who has to ship, and the founder who has to choose what's worth shipping. Three-as-one isn't a slogan for me. It's Tuesday.

Dare

Courage is a prerequisite, not a personality trait. You don't need to be fearless — you need to be willing to bet before the outcome is obvious.

I left comfortable fullstack-for-hire work to build in climate, a space where I was the new guy. That bet only looks smart in hindsight; on the day, it just felt like risk.

Dare is the courage to start. But courage pointed at the wrong target is just expensive noise — which is why it can't stand alone.

Reason

The hard part of building was never the building. It's choosing what deserves to be built.

This is the moat, and it's why I'm here and not somewhere with a shorter runway. Climate is the problem I think is worth a decade. MRV is unglamorous, data-heavy, trust-dependent plumbing — and it's exactly the kind of unsexy problem where software earns its keep.

Reason is the leg that aims the other two. It's also the one most builders skip, because asking "should this exist?" is slower than asking "can I build it?"

Most of what I write here will live under Reason — the intersection of climate, carbon, and code. It's the rarest thing I have to say.

Build

Ideas are cheap. The people who can actually ship are rare.

Craft is what turns a brave, well-aimed idea into something real — and without it, the first two legs are just a manifesto. (Yes, I see the irony of saying that in a manifesto.)

The fix is the same one it's always been: ship the thing, learn from contact with reality, ship again. I'll write the engineering here in specifics — architecture decisions, NestJS and GraphQL patterns, AI in production, the DevOps that keeps it boring — because craft doesn't transfer through abstractions.

One system, not three

Here's the whole argument in one line: courage finds a hard problem, reason confirms it's the right hard problem, and craft makes the answer real.

Pull any one leg and watch it fall. Dare without Reason is recklessness. Reason without Build is a really good opinion. Build without Dare is busywork — polishing the wrong thing beautifully.

The loop only works whole. That loop is what I mean by dayrlism — a personal "-ism", a way of building, not a brand.

What you'll find here

Three kinds of posts, mapped to the three legs:

• Dare — the founder journey, the hard lessons, building two companies in public.
• Reason — agri-tech, carbon markets, MRV, and the decisions behind them. The differentiator.
• Build — engineering deep-dives: architecture, GraphQL, AI integration, DevOps. Real code, real tradeoffs.

No theory for its own sake. No fabricated numbers. If I haven't confirmed a detail, I'll say so.

The takeaway is the same advice I'd give myself ten years ago: pick the right hard problem, and build it well. That's the entire game — the courage to choose it, the reason to know it's right, and the craft to finish it.

If you're building at the seam where climate meets code — or just trying to point your skills at something that matters — you're who I'm writing for. Stick around.