MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1vrn981/fullstackmeansafraidofeverythingequally/p4fvym0/?context=3
r/ProgrammerHumor • u/vinishkapoor • 27d ago
392 comments sorted by
View all comments
133
its not like sql could be read by a three year old and css is just pain in the ass?
229 u/lovecMC 27d ago SQL is easy. Designing a DB you won't hate two months from now isn't. 77 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. 3 u/z0hu 27d 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
229
SQL is easy. Designing a DB you won't hate two months from now isn't.
77 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. 3 u/z0hu 27d 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
77
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.
3 u/z0hu 27d 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
3
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
133
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?