The thing I had before was a cron job that ran a bash script every minute, checked a directory for new files, and curled them somewhere. It worked, mostly, until it didn't, and the failure mode was always silence. No file moved, no error, nothing in a log. I'd find out three days later when someone asked where their upload had gone.
So I rewrote it in Go. About ninety lines. It uses fsnotify to watch the directory, posts each new file to a webhook, and retries with a backoff when the endpoint is down. The whole thing compiles to one static binary I can scp onto a box that has nothing else installed. No runtime, no pip, no apt repository to argue with. That part still feels slightly magic after years of dragging interpreters around.
What sold me wasn't the language so much as the deployment story. GOOS=linux go build, copy the result, run it under systemd, done. It's been up for a fortnight without a hiccup, and when it does fall over it'll at least have the decency to log why. Small wins, but the silent failures are gone, and that's the bit I actually cared about.