The best Trek ever!

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.

One might call it a prime directive?

So stoked!