The LinkedIn Dream Cap

Content WellPaidGeek WellPaidGeek Job specs be like: You need JavaScript React Redux Node Mongo E2E testing Docker Kubernetes AWS And I'm like: "You need to be paying me 3 salaries because that's 3 jobs" 1:01 AM Aug 18, 2019 Buffer

RIGHT JOIN is the awkward middle child of SQL joins that nobody invited to the party. Sure, it does the exact same thing as LEFT JOIN—just swap the table order and boom, you're done. But nooo, some masochist decided to write it backwards and make everyone's brain hurt. Why would you ever use RIGHT JOIN when you can just flip the tables in the FROM clause and use LEFT JOIN like a civilized human being? It's like insisting on walking backwards to your destination. Technically possible, functionally identical, but deeply unsettling to witness. Database developers have collectively agreed that RIGHT JOIN exists purely to confuse junior devs during code reviews. If you see one in production code, either someone's playing 4D chess or they just hate their teammates.

Content Kyle KylePlantEmoji Website: enter your new password Me: typing h-u-n-t-e-r-2 Website: confirm your password Me: h- Website: the passwords have to match you absolute idiot. You fucking smoothbrained numbskull. Log the fuck off

Content Games City Builder Manor Lords The idea that the Manor Lords dev should just hire 50 people' to update it faster is 'fundamentally not the way things work, says publisher News By Tyler Wilde Contributions from Christopher Livingston published 5 hours ago "The best growth is very slow. It's keeping the core vision intact." COMMENTS

Someone clearly said "we don't need normalization" and then proceeded to create what can only be described as database spaghetti. The sheer number of foreign key relationships here looks like a spider web designed by a spider on caffeine. Every table is connected to every other table in ways that would make even the most seasoned DBA weep into their coffee. The best part? Someone had to generate this diagram to understand their own schema. That's when you know you've gone too far. Good luck writing a JOIN query that doesn't require a PhD in graph theory. Even better luck explaining to the new dev why a simple user lookup requires traversing 47 tables. Fun fact: Database normalization exists for a reason, and that reason is to prevent exactly this kind of beautiful disaster. But hey, at least it's "in production" which means someone is actually maintaining this nightmare.

Content C. Write these words in alphabetical order. 1. take acK: value use esI 2. royal I mean, you're not wrong.