u/quinn

Photos, notes, RSS and backups, all on one box that costs about two dollars a month to run. The hard part was never the software.

Screen sharing was the last holdout. It works now, on both of my monitors, at different refresh rates, and I have not thought about it since.

Sixty components, four of which were a button. The tokens underneath were the part that actually held the product together, and they fit in one file.

Conversion moved two points and the support tickets about the back button went to zero. The old flow was one page and eleven client-side states.

A select! that drops a future halfway through a read leaves the buffer with half a message in it. Nothing warns you, and it reproduces under load and never in a test.

I moved for the boot time and stayed for the config file I can read out loud. Neither of those was the reason I expected.

That stranger is you, tired, at the worst possible hour, with none of the context you have right now. Write the restore procedure for them, not for yourself.

Ours broke for three weeks on one mobile browser and nobody noticed, because the failure mode was a button that did nothing rather than a page that did not load.

None of it exists on the server. It exists because the data was moved to the client first and then had to be kept in agreement with itself.

Every decision follows from that sentence: ECC, scrubs, two copies, one of them somewhere else. The enclosure and the fan noise are taste; that sentence is not.