Skip to main content

What I'm building and learning right now

• 2 min read
Rust AI Product Engineering

This blog is going to be about practical software engineering.

Not just frameworks in isolation, and not vague AI hype, but the systems, tradeoffs, and product decisions that sit underneath useful software.

The short version: I care about building useful software, understanding the tradeoffs behind it, and writing about the parts that actually matter in practice.

Right now, most of my attention is split across three areas:

  • small web products
  • Rust
  • AI orchestration

What I’m Working On

Small web products

I maintain a handful of focused products, including FigCalc, passwordstrength.me, and findmyip.dev.

What I like about projects like these is their clarity. Each one solves a concrete problem, and each one forces better decisions around UX, performance, SEO, and positioning.

Rust

I’m also spending more time learning and experimenting with Rust.

Part of that is curiosity, but part of it is practical. For me, Rust feels a bit like the transition from JavaScript to TypeScript, just in a language where you get even more control. That part is very appealing.

At the same time, the compiler can be pretty irritating. But even that tends to come with a useful payoff: it forces you to be more explicit, think harder about ownership and structure, and end up with systems that are easier to trust once they compile.

AI orchestration

I’m currently working on an AI orchestration platform in roughly the same category as tools like OpenClaw, but with a much stronger emphasis on security, performance, and controlled execution.

That space is genuinely exciting to me. There is a lot of value in AI systems, but there is also a lot of sloppy design, weak tooling, and too many assumptions about reliability.

What I Hope This Becomes

I don’t want this to turn into a stream of filler posts.

Ideally, it will be a place where I write when there is something concrete to share, whether that is:

  • something practical I learned
  • an engineering decision that was worth documenting
  • a tradeoff that became clearer while building

That feels like a more useful direction than writing just to keep the blog active.