Cloudflare’s Post

The real developer horror story? Opening an old project, changing just one line of code, and watching 47 other things break. Who needs a Halloween costume when you have legacy code?

The classic one every infra engineer fears: two terminal tabs open, one for staging and one for production. You type the scary command in the "staging" tab, hit Enter, and then notice the prompt says prod. 👻 That's why I love a big red prompt colour for production. It's a small thing, but it saves a lot of sleep.

UPDATE users SET status = 'inactive' WHERE last_login < '2025-01-01' DELETE FROM users;

Once I wrote Python bindings for a C SDK without ever having opened a single .py file. I did it procedurally, the way I was used to. On a stream the users said it was “C in Python skin,” and I had to redo the API to feel like proper Python. Ever since, any “just write a wrapper” request gives me a slight chill — I always check first how people will actually call it.

I'd say my publication in 2024 is a horror story 👍. Give it a read. Thank you Cloudflare for all your skilled and professional workers making the product excellent for developers. https://faun.pub/a-sad-reality-mislead-junior-developers-out-of-work-in-2024-aa23760e61ea?sharedUserId=srdbranding

one time i was using a new progressive rollout tool at my job. something went wrong with the deployment so after consulting with colleagues who wrote the tool, I hit the "rollback" button. Unfortunately this caused a major internet outage. Doubly unfortunate is the tool I was deploying was kind of a major substrate for the entire company, incl. the control plane, so remediating the problem itself became very hard.