What I've been building

Most of the work went into making the cloud development environment reliable enough to run unattended.

• The automated end-of-session cleanup now closes finished work it used to leave listed, so the backlog reflects what has actually shipped.
• Fixed cloud browser screenshots and UI checks that would not start, permission prompts repeating on every action, and a broken security review in new sessions.

A deploy still running could be wrongly marked failed if you stepped away for over 15 minutes, which no longer happens.

A day on the workspace’s own tooling and plans, so nothing in any live app looks different.

• Finishing a work session now updates the task backlog itself, marking items started and closing them once their changes merge, instead of relying on memory.
• Design mockups no longer carry stray explanatory sentences unless each is approved first, so labels and layout must be clear on their own.
• The standard way to ask a question, a numbered list rather than a pop-up picker, is now always in force so it can’t be skipped.
• The plan for a new error-tracing setup was fleshed out, so a fault can be traced to the request and the release that caused it.
• The trading app’s move to live market data was split in two, so the old system is dropped only once the new one proves out.

None of this touched a live app; it was behind-the-scenes tooling and planning.

• Connected the tools that let an automated work session read the live apps’ logs, so a change can be checked against real behaviour instead of guesswork.
• Scoped a redesign of how the Polymarket app stores its market list, to cut how often its database is written to.

The preview of animation options for the Polymarket settled-positions reveal is now published to a public page, linked from the index of design mocks.

None of this reached a live app; it was groundwork for changes still to come.

• The plan to stop the paper-trading app silently dropping near-term prediction markets was worked out, so a market you look for won’t go missing.
• A new product idea, software for running local kids’ dance competitions, was researched and written up as a possible future project.

The Polymarket paper-trading project got its current state and the plan for its next feature written down, for a later work session to continue from.

A new project idea took shape, a sandbox for practising bets on Polymarket prediction markets with fake money, settled against real outcomes.

• You can now open interactive mocks of the five key screens in a browser, so the idea can be clicked through before any code.
• The mocks now reflow to fit a phone screen, so the idea reads on mobile and not only on a wide desktop.

Most of the work went into habits, with a handful of weekly-review fixes.

• You can now mark a habit done on a day it isn’t scheduled, from Today or the habit’s page, so a make-up counts.
• A make-up fills in the day you missed so it shows in the habit’s history, while an extra one is logged as a bonus.
• Any off-schedule mark can be undone with one tap, in case you picked the wrong habit.
• Fixed the weekly review listing chores on the wrong weeks, a placeholder ‘Every N weeks’ label, and a bounce home after committing a plan.

The pieces worth showing were all interactive, built to be understood by clicking around rather than by reading.

• GlamCam, a new makeup mirror for kids, tracks your face through the camera so painted-on makeup stays put as you move and turn.
• An interactive explainer argues for composable software architecture, with simulations you can drive to see how batching and busy teams pile work into queues.
• A separate tool lets you compare two team structures side by side and watch where work sits waiting under each one.

The work was two web-based guides that teach a way of building software from swappable parts, explained by clicking rather than reading.

• One guide introduces the idea for a general audience, from executives to engineers, with a playground for swapping a part out to see what happens.
• The other tailors the same ideas to one organisation’s real setup, with animated infographics and a board you click to plan retiring an old system.
• Separately, a review of the development workflow was written up, flagging gaps to close in its automated safety checks.

A grab-bag day of standalone experiments and product research.

• You can now try a face-tracked virtual makeup mirror in the browser, so a child can play with makeup live without installing anything.
• You can now click through design mocks of a skills-based hiring tool, so partners can see both sides of it before anything is built.
• A ranked list of twenty software business ideas for a solo founder was written up, each with evidence of real demand.