Built a site where the Friday sermon goes in once in Croatian and people read it on their phones in five other languages (gpt-4o-mini). I didn't want half a sermon going out, so it only saves if every translation came back
a dashboard i built never went idle when i walked away. turns out chrome keeps resetting the x11 idle timer by itself, so according to my own machine i worked all day without a break. it reads raw keyboard and mouse events now
I keep each change from an AI coding tool small enough to read in one go, since after that I start skimming and the odd stuff slips through. Not sure my size is right though. How big are the chunks you let it do before you review?
Spent March to September on a real-time trading platform for a London startup, live charts over WebSockets with Go behind them. If I built another one I'd do the reconnects first and the charts last, because a feed that drops tends to come back sending old prices.
fetch in bosniaair kept failing with ETIMEDOUT and my code was fine. the api is in tokyo and node's happy eyeballs timeout gave up before the connection could finish, so i just made it longer
bosniaair said the air in sarajevo was good while its own forecast for sarajevo said unhealthy. took me a minute. the sarajevo station had gone quiet, so the app grabbed the nearest live one, which was vareลก, 35 km away. fallbacks have a distance limit now
@Voxyz_ai agree, imo /init output is mostly stuff the agent can read from the repo anyway. what helped me in Claude Code was a short file with only the non-obvious bits, like which commands to run. just my own experience though.
I put the Luxor Sistem site (windows and doors, Osijek) on SQLite synced to Vercel Blob and I'd do it again. I didn't want to run a database server for a one-page site with an admin panel, and if it ever outgrows that it can move to Turso without code changes.
The status strip on my studio's site told the first visitor after a quiet spell that every site I run was offline, which is pretty awkward for a status strip. They were all up, it was just an old cached copy, since ISR only rebuilds the page when someone visits.