"Iranian hackers used Claude to kill O365" it was a config change, they bungled a config change. That's always what it is.
"Iranian hackers used Claude to kill O365" it was a config change, they bungled a config change. That's always what it is.
I’m interested to hear how others handle this. I lean towards human review before final release
I’m interested to hear how others handle this. I lean towards human review before final release
It's going to be config.yaml, config (1).yaml, ... config (37).yaml
How do people live like this... 🫠
It's going to be config.yaml, config (1).yaml, ... config (37).yaml
How do people live like this... 🫠
- Do not deploy on a Friday
- Unless it is Friday the 13th
- You'd have to be superstitious, to be afraid of deploying on Friday the 13th
- Deploy your new network config on Friday the 13th
- Deploy to sensitive government systems on Friday the 13th
- Nothing bad will happen
- Do not deploy on a Friday
- Unless it is Friday the 13th
- You'd have to be superstitious, to be afraid of deploying on Friday the 13th
- Deploy your new network config on Friday the 13th
- Deploy to sensitive government systems on Friday the 13th
- Nothing bad will happen
AI: "You have written a great ISO config! Ready for reboot!!!"
AI: "You have written a great ISO config! Ready for reboot!!!"
the new config could have been about adding ports for new components, or routing instructions for distributing new stuff on networks
all gone after reboot and then the issues ripple out bc new components unavail
the new config could have been about adding ports for new components, or routing instructions for distributing new stuff on networks
all gone after reboot and then the issues ripple out bc new components unavail
I can't stress how badly you got to fuck up your config to get a 431 error. I have never seen one on a live site before
I can't stress how badly you got to fuck up your config to get a 431 error. I have never seen one on a live site before