Field notes on engineering decisions, projects and what I learn along the way.
I could see the freedom in a custom backend, but still had questions about time, maintenance and who would take it on later. This is how I chose where to spend my own effort.
A phone menu did not fit on screen, but the checks went beyond that screenshot. This week, the checks before handing over a website, an admin entry point, a colour revision, a release record, demo dashboard metrics and copy review all exposed things that needed to be verified separately.
I’d put together a flowchart and a reference sheet beforehand. Once a queue formed, I got nervous about mistakes. Afterward, I still couldn’t work out why my head had struggled to keep up at the counter.
If a simulation stops when its page closes, where does the intervening history come from on reopening? Three fictional interactive examples explore how shared state, clocks, reconstruction, random streams and stable IDs keep simulated data coherent.
A small question about a Copy button led me to examine how people find controls, how pages keep their content, and how future editors can update the site.
Could someone who never worked on a product tell what it does on site? This looks back at putting nine demo events into one illustrative construction site, and at why the viewing pace had to be rethought.
From recalculating a table to comparing website structures and reviewing prototypes page by page, I kept asking what problem each judgement or change actually solved.
Some source material needed to be recovered, some figures could not be compared directly, and a finished report still needed to be rewritten.
