Skip to content
Matthew Blode
Writing
Product & craft2 min read

People can sense carelessness, even when they cannot see the code

The floor for shipping something competent has never been lower. The work that decides quality moved to editing, and editing is where most teams stop.

Based on my February 2026 Next.js Melbourne talk about care, craft, and product quality.

I can tell when a product was shipped without a second pass. The page is slow to settle, the copy is vague, a form makes me guess. I’m reacting to the experience, not inspecting the source.

AI makes competent output fast. It also makes it easy to stop too early and ship the first plausible version: something that works but feels generic. The closer a product sits to the user, the more obvious the careless details become. I’ve shipped enough of both kinds to feel the difference in my own work.

The editing pass

I cut the awkward steps, rewrite the vague copy, tighten the motion, simplify the hierarchy. AI is great at momentum. It’s less reliable at deciding what should matter most. That call is still mine.

I’ve made this pass on every product that lasted. The first version gets you in the room. The second and third versions are what people remember.

A thousand small iterations

At Fingertip, care was deliberate improvement after the MVP shipped. I kept coming back to the same surfaces. The page editor went from a static list to a drag-and-drop grid. The default share preview went from the Fingertip logo to a live screenshot of the user’s page. Stock shadcn became a considered system with central icons, custom typography, taller inputs and a curated colour palette. Each change was small.

Together they changed the whole thing. I could feel it when I opened the product myself, before any metric moved.

Page editor before: a static list of sections
Page editor before: a static list of sections

Page editor after: a drag-and-drop grid with visual hierarchy
Page editor after: a drag-and-drop grid with visual hierarchy

Social share before: generic Fingertip logo
Social share before: generic Fingertip logo

Social share after: live profile screenshot
Social share after: live profile screenshot

Form inputs before: default shadcn styling
Form inputs before: default shadcn styling

Form inputs after: polished event settings with structured hierarchy
Form inputs after: polished event settings with structured hierarchy

Between product and design

My work sits between product, engineering, and design. VenueSafe under time pressure, Fingertip growing into a broader SMB platform, LinkApps at Linktree: the question stays the same. Does this feel right to the user?

At VenueSafe I was shipping under a clock, and still the forms and flows had to feel intentional or venues wouldn’t trust them. At Linktree the surface area was bigger, but the same habit applied: I kept editing until the careless edges were gone. Nobody thanks me for that pass. They just stop feeling like something is off.

I stop when it feels deliberate. Past that, I’m usually decorating.

Get new posts by email

New writing on shipping with AI agents, sent when it is published. Nothing else, and you can leave any time.