Pimp My IDE / Garage Dispatch
Back to the garage
October 5, 2026 | personal software / AI coding / product craft

Build for one. Budget the afterlife.

Cheaper software makes tiny, personal tools worth building. The audience can be one person. The maintenance bill, data path, and failure mode still exist.

The take: use the coding agent to erase the setup tax, not the product judgment. Name the annoying job, build the smallest route you will use, and decide what happens when the dependency changes or the tool stops earning its keep.

A sales funnel is not the only reason to ship.

Colin Armstrong wanted a clean domain lookup tool. Search results kept sending him to pages built to sell domains or hosting. He writes that he used Claude Code to get the first working version of heade.rs online in three prompts and about an hour. He spent the rest of the day on the interface.[1]

That is one builder's report, not a measured productivity study. The interesting part is the changed threshold. A tool does not need a large market when it costs a weekend and solves a recurring irritation for its maker.

The audience can be one. The operating contract cannot be zero.

Personal software still has a public edge.

The live heade.rs page accepts a domain, IP address, or autonomous system number. It also shows recent and popular lookups.[2] That turns a personal annoyance into a networked service with visible activity. It is a useful product choice to inspect, not a criticism of this particular site.

Before sharing a personal tool, decide what leaves the browser, what gets stored, what other visitors can see, and how abuse is limited. A tool that only you use can keep data local. A tool with a public URL needs a public-service threat model.

Cheap hosting does not remove cost shape.

Armstrong says his service costs less than a cup of coffee each month. Cloudflare's Workers documentation lists a limited free plan and a paid plan with a five-dollar monthly minimum. It prices dynamic requests and processor time separately, while static asset requests are free and unlimited under the documented plan.[3]

Do not turn that schedule into a universal budget. A domain lookup can also depend on upstream services, rate limits, storage, logging, and abuse controls. Record the first cost that would make you shut it down. A personal tool deserves an exit route before it becomes an unpaid obligation.

Polish is use under pressure.

The Hacker News thread challenged the word "polished." Commenters split between visual finish, stable behavior, and actual use by someone who understands the job.[4] The thread is opinion, but the disagreement points to a good test.

Use the tool for the annoying job several times. Keep the broken shortcut, stale result, confusing state, and recovery step. A glossy first screen can be generated quickly. A tool becomes good when repeated use removes friction without hiding a new burden.

Interactive makeover / personal utility brief

Audience-of-one ignition bay

Traditional purpose replaced: a blank project prompt. Better version: choose the intended lifespan, close four planning fuses, and copy a brief that keeps usefulness beside data, upkeep, and exit.

Choose lifespanClose planning fusesCopy the brief
Intended lifespan
Planning fuses

Selected means the section belongs in the brief. It does not mean the requirement is filled or tested.

ONE-SHOT / 4 FUSES OPEN

One-shot selected. Define the answer you will save before writing the tool.

Sources read, claims separated

  1. Colin Armstrong, "Worth building", October 5, 2026. First-person account of the annoyance, build path, time, cost, and product motive behind heade.rs. It is not a controlled comparison of human and agent development.
  2. heade.rs, inspected October 5, 2026. The live page accepts domains, IP addresses, and autonomous system numbers. It displays recent and popular lookups. We inspected the public interface. We did not audit its code, data retention, upstream services, or security.
  3. Cloudflare Workers pricing, updated October 2 and read October 5, 2026. The page documents the free plan, the paid plan minimum, request and processor-time pricing, and static asset treatment. Armstrong's own cost statement applies to his service.
  4. Hacker News item 49971952, resolved through the Hacker News API and read October 5, 2026. The comments contain competing opinions about polish, personal software, and repeated use. They are discussion, not product evidence.

Source boundary. No source above proves that agent-built personal tools are cheaper, safer, faster, or easier to maintain as a class. This dispatch turns one builder's account and one live artifact into a planning method. The ignition bay creates a template. It does not create or inspect software.