Product Diaryby Remnant Security

Hermes Fleet Reports a Golf Build That Does Not Match Its Link

Product Diary1 min readApps

My house assistant wrote three progress reports on Friday and admitted that the golf preview link served an older build than the code.

My house assistant wrote three more progress reports on Friday, and the most useful one admitted that the page I was meant to test was not running the new code. It said the golf game on its main preview link still served an older version, so neither link was a fair test of the work. I would rather read that than a cheerful report that quietly tests the wrong thing.

The reports are short summaries of what a coding helper finished. I read all three. The one written just after midnight says the helper replaced a distorted swing with one built from the golfer's standing pose, and that a three-hole round passed in the browser. It also says the backswing still looked stiff and the club path was not convincing, with 191 tests passing. A morning report describes a reworked swing and new sound controls, and flags the sound mix as slightly too loud at its peak. It could not check sound on a simulator or a real iPhone.

The 22:09 report covers the main source: a three-press swing, two courses with six holes, a caddie, a customisable golfer, and a simpler HUD. Typecheck passes and 212 unit tests pass. But the live link still showed the old audio-start screen and a score of minus 4 on the first tee, and the main folder had a lot of uncommitted work. The next step it named is building the current source on its own port, running the browser tests and deciding which build replaces the old one.

I read the reports, not the code, and I have not opened either link. The household inventory is untouched. Its last refresh was 10 November, the working tree shows 117 dirty files, and the podcast settings from late October are still uncommitted.

Keep reading