Independent product engineer / field notes 2026

Justin Wilds builds practical software for complex real-world work.

I spent twenty years close to operational work—implementing systems, helping people use them, and seeing where software fails the people doing the job. Now I turn that experience into products of my own.

ObserveDecideBuildVerify

Selected work

What I'm building

Three products, each grounded in a real problem and tested through actual use.

Project Desk

Live product

A shared work desk for people building across projects with AI agents. It keeps decisions, queues, handoffs, and proof in one durable place.

Live desk / queue trace Synced
01AttentionDecision capturedHuman
02AgentWork dispatchedRunning
03ProofResult verifiedGreen
One durable thread from question to proof.

MindServe

In development

A connected cafeteria operations suite shaped by twenty years of firsthand workflow knowledge—from inventory and purchasing to ordering and service.

Operations / connected loopMindServe
  1. 01Import
  2. 02Map
  3. 03Stock
  4. 04Produce
  5. 05Serve
Inventory truth carried all the way to service.

ShelfFinder

Live pilot

Voice-first grocery navigation that turns a natural shopping list into a useful, store-aware route.

Voice surface / trip sketch Pilot
Heard“milk, coffee, bananas”
  1. 01
    BananasAisle 1 · Produce wall, lower display
  2. 02
    CoffeeAisle 4 · Third shelf
  3. 03
    MilkAisle 12 · Dairy case, middle shelf
Intent first. Keywords become a useful trip.

How I work

Domain judgment first. Modern engineering underneath.

I start with the work.

The awkward handoff, the exception nobody planned for, the screen that asks an operator to think like a database—those are usually where the real product begins.

I build in tight loops.

I use AI agents as engineering partners, then test the result in the running product. The tools move quickly; judgment, security, and proof still belong to me.

Field note 01 The useful detail is usually hiding in the exception.

For a closer look

Technical proof

These are intentionally public, sanitized views of how I structure and reason about software. Production source stays private.

Let's talk

Found me through a forum, a project, or a conversation?

I'm always interested in thoughtful engineering roles, useful product work, and people solving difficult operational problems.

justin@wilds.us