Why Do NoSQL Devs Eat Lunch Alone?

Content ORACLE PostgreSOl SOL Server MySQL IBM. DB2. SYBASE A Microsoft Access Excel I PREFER A REAL DATABASE I SAID A REAL DATABASE PERFECTION

Frontend dev: "I can't center this div!" Backend dev: "Hold my coffee, I'll help." *5 minutes later* Frontend dev: "THE DATABASE IS GONE?!" Backend dev: "Well, technically you don't need to center that div anymore..." And that's why we don't let backend devs touch CSS. They'd rather nuke production than figure out display: flex; justify-content: center;

Content People that use Mac YUU GUTTA BE KIDDING ME RIGHT? People that use Android

Content There's a repo on Github containing some scripts used by a tech employee that his coworkers discovered after he left the company. Here's a summary of his shenanigans: xxx: OK, so, our build engineer has left for another company. The dude was literally living inside the terminal. You know, that type of a guy who loves Vim, creates diagrams in Dot and writes wiki-posts in Markdown... If something - anything - requires more than 90 seconds of his time, he writes a script to automate that. xXx: So we're sitting here, looking through his, uhm, "legacy" xxx: You're gonna love this xxx: smack-my-bitch-up.sh - sends a text message "late at work" to his wife (apparently). Automatically picks reasons from an array of strings, randomly. Runs inside a cron-job. The job fires if there are active SSH-sessions on the server after 9pm with his login. xxx: kumar-asshole.sh - scans the inbox for emails from "Kumar" (a DBA at our clients). Looks for keywords like "help", "trouble", "sorry" etc. If keywords are found - the script SSHes into the clients server and rolls back the staging database to the latest backup. Then sends a reply "no worries mate, be careful next time xxx: hangover.sh - another cron-job that is set to specific dates. Sends automated emails like "not feeling well gonna work from home" etc. Adds a random "reason" from another predefined array of strings. Fires if there are no interactive sessions on the server at 8:45am. xxx: (and the oscar goes to) fucking-coffee.sh - this one waits exactly 17 seconds (!), then opens a telnet session to our coffee-machine (we had no frikin idea the coffee machine is on the network, runs linux and has a TCP socket up and running) and sends something like sys brew. Turns out this thing starts brewing a mid-sized half-caf latte and waits another 24 (!) seconds before pouring it into a cup. The timing is exactly how long it takes to walk to the machine from the dudes desk. xxx: holy sht I'm keeping those Reply 4 10.3k J

When a colleague announces they're leaving, there are two types of developers: those who mourn the loss of institutional knowledge, and those who've seen Billy's SQL queries. Poor Billy committed the cardinal database sin: using a cross join with a group-by clause. That's like using a flamethrower to light birthday candles – technically it works, but the collateral damage is... extensive. The remaining team members aren't celebrating Billy's departure – they're planning his execution before he can push that monstrosity to production. Because nothing says "farewell party" like debugging someone's queries that would bring a database server to its knees.

Content straight up wrong info non-profit MDN web docs moz:a schools for-profit out-of-date misleading nam crappy site layout cool dragon logo helpful usage tips well-organized, clean layout cites the relevant standards no browser compatability info worthless paid certificates helpful browser compatability (aka not IE) very accurate info peer-reviewed