NoBackups

It worked in staging…

Category: Automation & Tooling

  • [ 0.000005] // 0x006: VOLATILE

    Imagine The Company’s report worker has accepted a request for April’s totals. It hasn’t started the report. Fine. Pending is a useful state. It means I can interrupt the worker without having to interrupt April.

    The request is a small file in the worker’s runtime directory. Its only copy. I have nevertheless described this queue as persistent, because the files were still there every time I looked. An impressive run of observations, all made while the service was running.

    I liked the directory. The service manager created it for us and removed it when the service stopped. No abandoned pid files, no archaeological layers of temporary rubbish. Somewhere to put things without eventually having to decide what they were.

    I have a drawer like that. It contains three display adapters and a key to something that was decommissioned before the adapters were manufactured. If the drawer tidied itself whenever I left the room, I would consider that progress. I would also stop putting my passport in it.

    Back to April. One accepted request, still pending. I stop the service normally, then start it again, expecting the worker to pick up where it left off.

    Fresh runtime directory. No request. No report either.

    I read the removal setting. Then I read the queue’s persistence requirement. Then I check that they refer to the same path, which is the sort of checking you do when you would prefer two correct sentences to be somebody else’s problem.

    The service manager has kept its promise. I gave the application a different one.

    For a moment I consider leaving the worker running forever. No more normal stops.

    April’s report can wait indefinitely. Preserving its place in the queue requires a service that must never stop, even while it isn’t doing the report.

  • [ 0.000001] // 0x002: EAGAIN

    Say you give the chatbot a shell script that exits successfully after failing to copy the backup.

    The script was written by someone whose account still owns half of /opt, despite having left before the company acquired its current name. Nobody has removed it. Nobody knows what breaks if they do. This is called institutional knowledge.

    The bot spots the missing error handling. It starts explaining pipelines, exit statuses and why the last command succeeding does not mean the preceding commands achieved anything useful.

    Then suppose the allowance runs out.

    Lovely. The backup script and its replacement sysadmin now share a failure mode: neither has finished the fucking job.

    The demo never seems to reach this bit. An agent builds an application while a man in expensive trainers stands beside a plant. Nobody shows you, twenty minutes later, working out whether the last block of code is complete or merely optimistic.

    People say their week’s allowance ran out days early. The man selling abundance explains that the service costs more than it earns, asks whether more usage costs too much, and calls it sensible.

    I’ll tell the missing files.

    You could compare plans to establish which tier includes reaching the end of a sentence. Or open the manual. It continues existing after you read it.

    I open another terminal to automate the allowance checks. Start sketching something to watch the checker. Catch myself choosing a name for its service account.

    Close the terminal.

    I don’t object to computers having limits. I object to being sold emancipation from tedious work and finding another dashboard to tend. If your miraculous digital colleague needs rationing, put that in the demonstration. Show us who gets to finish.

    You fix the script yourself. Run it against a test directory. Check the exit status. Check the files. Only then do you touch the scheduled job.

    The morning’s automation breakthrough is complete.

    You are now doing your job and its job.