Software development

An internal tool. A quoting engine. A booking system. A dashboard that pulls your numbers onto one screen. A portal your clients log into. Anything where the off-the-shelf option covers 80% and the missing 20% is your actual business.

It runs in a browser. Nothing to install, works on a phone, and it is deployed as a container on Google Cloud Run in europe-west1.

On the Custom Timber Decks build there is a timber species table with Janka hardness in it. Composite decking has no Janka figure. So the field is typed number-or-null and that cell prints nothing, because printing "0 lbf" would have been a lie.

That one field is the whole discipline. Most bad software is bad because a missing value became a zero, a blank became a default, an unknown became a fact on a screen someone then acted on. I design the data first and decide what every field does when there is nothing in it.

Four of the five websites I have built are live. No standalone software project is. I am not going to dress that up.

So look at how I check my own work. On the CamelPhat build I audited 25 stock images and destroyed four: three carried tiled rawpixel watermarks, and one keyed "solar-farm-rows", live in two places, was a photograph of a Japanese torii gate. Breadcrumb text across seven page heroes measured 1.49:1 and went to 5.04:1. Overflow gets checked in headless Chrome at 320, 390, 768 and 1440. I find the things nobody would have reported.