![](/static/23fb711/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/db7182d9-181a-45e1-b0aa-6768f144911a.jpeg)
⚠️⚠️⚠️ Bunch of new accounts posting articles from this site. Be warned! ⚠️⚠️⚠️
⚠️⚠️⚠️ Bunch of new accounts posting articles from this site. Be warned! ⚠️⚠️⚠️
⚠️⚠️⚠️ Bunch of new accounts posting articles from this site. Be warned! ⚠️⚠️⚠️
Ben Garrison, gross…
Totally right! You must set yourself up so a fool can run in prod and produce the expected result. Which is the purpose of a test env.
Replied hastily, but the way to run db statements in prod while dealing with sleep deprivation and drinking too much is to run it a bunch in several test env scenarios so you're just copy pasting to prod and it CAN confidently be done. Also enable transactions and determine several, valid smoke tests.
Edit: a -> several
Fuck that, get shit housed and still do it right. That's a pro.
This is a hilarious and prescient read. Really enjoyed it. The grug mindset seems to fit well with a lot of infrastructure/Cloud automation.
My dom has some
systemctl
issues. Clearly there’s somehistory
…