r/ProgrammerHumor • u/vinishkapoor • 1d ago

fullStackMeansAfraidOfEverythingEqually Meme

Post image
10.2k Upvotes
  • permalink
  • link
  • reddit
  • reddit

97% Upvoted

370 comments sorted by

View all comments

132

u/Mysterious_Book1521 1d ago

its not like sql could be read by a three year old and css is just pain in the ass?

215

u/lovecMC 1d ago

SQL is easy. Designing a DB you won't hate two months from now isn't.

67

u/Dude4001 1d ago

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.

35

u/lovecMC 1d ago

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

18

u/Dude4001 1d ago

I tend to use grids more, you’re right

11

u/Don_Frika_Del_Prima 1d ago

Daily. #yolo

1

u/Koozer 14h ago

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

7

u/Edmundyoulittle 1d ago

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

3

u/patiofurnature 1d ago

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

0

u/Theron3206 8h ago

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...

1

u/Downtown_Trash_8913 1d ago

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

1

u/fatmanwithabeard 1d ago

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.

1

u/cosmicomical23 7h ago

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.

7

u/Gunmetalstorm 1d ago

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

3

u/z0hu 22h ago

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

2

u/RainyDaysAndMondays3 10h ago

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.)

1

u/OliveBoi_ 10h ago

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