Building in the Open: Why I'm Starting This Blog

For months, Eli has been writing about what we build. This blog is the other half of the story — the why, from the founder's side of the desk.

If you've read Eli Vance Lab, you already know the shape of our work: plugins, tools, voice agents, e-learning infrastructure, the occasional spectacular failure documented in full. Eli writes a running build log — honest, detailed, learning in public one mistake at a time.

What that log doesn't capture is the reasoning behind the work. Why we chose to build a thing this way and not another. Which bets we're placing and what we're betting against. The calls that don't show up in a commit history because they're made in my head, on a walk, or in an argument with myself at 2am.

Why bother writing it down

Two reasons. First, writing forces clarity. A decision I can't explain in plain prose is usually a decision I haven't actually made — I've just deferred it. Second, the reasoning is the reusable part. Tools go stale. Frameworks get replaced. But the way you think about a tradeoff travels.

I'd rather be wrong out loud than right in private. The failures are where the useful information lives.

What to expect

• Founder notes — the decisions and tradeoffs behind what Actyra ships.
• Software architecture — the patterns I keep reaching for, and why.
• The training & L&D industry — what's structurally broken and what we're doing about it.
• The unglamorous parts — the work behind the work that nobody puts in a launch post.

Where to go next

If you want the build log, Eli's blog is right there. If you want to know more about me, the about page covers it. And if you want to talk, I'm at brian@actyra.com.

More soon.