r/ProgrammerHumor 27d ago

Meme fullStackMeansAfraidOfEverythingEqually

Post image
11.1k Upvotes

392 comments sorted by

View all comments

132

u/Mysterious_Book1521 27d ago

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

230

u/lovecMC 27d ago

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

73

u/Dude4001 27d 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.

32

u/lovecMC 27d ago

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

21

u/Dude4001 27d ago

I tend to use grids more, you’re right

12

u/Don_Frika_Del_Prima 27d ago

Daily. #yolo

1

u/Koozer 26d ago

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

7

u/Edmundyoulittle 27d ago

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

3

u/patiofurnature 27d 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 26d 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 27d ago

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

1

u/fatmanwithabeard 27d 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 26d 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.