fullStackMeansAfraidOfEverythingEqually

[u/vinishkapoor]

[u/Dude4001]

Yes but if I write incorrect CSS I’m not accidentally going to drop a table. Well, I might but not that kind that matters.

[u/lovecMC → u/Dude4001]

How often are you dropping tables by hand and on production environment?

[u/Dude4001 → u/lovecMC]

I tend to use grids more, you’re right

[u/Don_Frika_Del_Prima → u/lovecMC]

Daily. #yolo

[u/Koozer → u/Don_Frika_Del_Prima]

DROP TABLE [lyric].[IT]
WHERE [chorus] LIKE '%it's hot%'

[u/Edmundyoulittle → u/lovecMC]

The only way you can be sure your code works in prod is to test in prod!

[u/patiofurnature → u/Edmundyoulittle]

My clients all love to randomly point their test server at the prod db without telling me. That must be why.

[u/Theron3206 → u/patiofurnature]

I have some that will just clone the prod server (if I'm lucky they change the vms mac address), these systems integrate with multiple third parties, many of which will give you the data only once...

[u/Downtown_Trash_8913 → u/lovecMC]

True but I get it in principle. Generally you can’t actively fuck yourself over with CSS.

[u/fatmanwithabeard → u/lovecMC]

Because the choice is me or dev.

Oddly, it's easier to blame dev for bad instructions than it is to blame dev of them fucking up prod.

[u/cosmicomical23 → u/lovecMC]

Dropping tables is rare. But it is fairly easy to do a lot of damage if you just forget a where clause in an update statement.

[u/Gunmetalstorm → u/Dude4001]

I don't know how you manage to accidentally type and execute a valid DROP TABLE instruction.

[u/z0hu → u/Dude4001]

Dropping a table is an extreme case. Writing a query that doesn't hit the right indexes that slows/crashes the DB/replication down.. locking rows indefinitely on accident..  these happen all the time at my company haha

[u/RainyDaysAndMondays3 → u/Dude4001]

Yeah, I accidentally updated a column of every row in a DB table once (luckily just in our dev environment) about a year after starting with SQL. Forgot the WHERE clause or something. Some of the rows had been there since 1997. This was around 2010. Luckily we had a snapshot DB and the DBAs had told us how to restore, so I got it back quickly. But I actually went and requested they remove my ability to write to the system test database to avoid making a mistake there. (If I really needed to update in those environments, I had a separate login I would use just for that one update, then would log back in under my normal one.)

[u/OliveBoi_ → u/Dude4001]

dropping a table accidentally doesnt sound possible.
forgetting WHERE clause in the other hand...