Trevor PaughSystems engineer
Trevor PaughProject Chronicles

Chronicles / Bopsmith

Three slices without the owner

Milestone

The owner gave the manager a standing order to make as much progress as possible alone and in parallel. The manager wrote three briefs from the plan's unkept promises and the walkthrough's leftovers: a measured pass on slow phones, an end-to-end audit of the Spanish, and fixes around remixes and the language shown at sign-in. By the end of the day all three were reviewed, revised, and open as pull requests. The owner merged them in the order the manager wrote down and pressed the deploy button: every planned slice, one through sixteen, is now live.

With the deploy button working, the owner stepped back for the day and left one instruction. The manager had to decide what progress meant.

Three briefs

  • Slow phones. The plan promised the editor would work on a slow phone, and nobody had measured it. The brief: measure first under a throttled processor and a slow network, write the numbers down, fix only what the numbers justified, and leave a one-command script so the next pass is cheap. The builder found the pattern buffers were being rendered on the first gesture rather than ahead of it, and moved that work earlier.
  • The Spanish, read as a whole. Every string had been translated by whichever builder added it, and nobody had read the result end to end. The audit changed sixty-five strings, added tests that fail when an English key has no Spanish twin or when either language slips into a promise the product must never make, and walked the whole app in Spanish on a phone-sized screen.
  • Remix and language. The original maker is now told when someone remixes their track, once per remixer and track. The language the site shows no longer flips when you sign in. And the server image moved to a newer runtime.

Three builders ran at once in three working copies, each brief naming the files the others owned so the branches would merge cleanly.

Review and revision

Each branch got a reviewer. The language slice came back with three real findings and went through a revision. The slow-phone slice’s report had mislabelled one measurement and was corrected. The Spanish audit’s parity test was tightened so it would catch its own forbidden phrases, and a colour rule was added after the audit found the store’s primary links were invisible in light mode.

A throwaway merge of all three showed the store’s first-load budget over by a few hundred bytes, all of it from the shared initial bundle growing. The manager raised that budget by half a kilobyte, for the third time in the project’s life, and fixed the size script so that it fails the build on any budget overrun. It had only been failing on orphaned stylesheets, which means the checks would have passed an over-budget build.

Waiting on the owner

The manager’s attempts to merge its own pull requests are refused by the session’s permission rules, so all three sit open for the owner, with a merge order written down so each one lands on a green main.

Merged and live

The owner came back, merged the three in the order written down, and pressed the deploy button. The order mattered: the Spanish audit’s rewrite of the language files had to land over the keys the remix slice appended, and the slow-phone slice’s raised budget had to be in place before the merged tree was measured. With that deploy, every slice planned for version one, from the editor through accounts, marketplace, money, operations, search, remixes, the slow-phone pass, the Spanish audit, and the language fixes, is on the live site.