The Complete Version Of Modern Digital Infrastructure

Content Admin: grants me sudo privlages Me: sudo kill -9 RANDOM FU fuckin do it again

Content ctri C ctrl

Someone actually filed a GitHub issue because their cough crashed their program. Let that sink in. Their biological function literally corrupted memory somewhere and brought down code. This is what happens when you code so close to the metal that even your bodily functions can trigger buffer overflows. The real question is - did they try turning their throat off and on again before submitting the ticket?

The ultimate Linux desktop environment civil war, but make it wholesome! Nothing says "I'm a true open source hero" like using one desktop environment while financially supporting its arch-nemesis. It's like being a vim user who donates to the Emacs foundation—pure chaotic good energy. The Superman imagery is perfect because let's be honest, anyone running Linux in 2024 already thinks they're saving the world from the evil corporate empires. Meanwhile, Windows users are just trying to print a document without their computer deciding it's the perfect time for a 2-hour update. Fun fact: If all the energy spent arguing about GNOME vs KDE had been directed at actual development, we'd have had the year of the Linux desktop back in 2003.

Content . 3 3G 12:42 73 0 1 Job details Salary 25,000 - 28,000 a year Job type Full-time Permanent Number of positions for this role 1 Full Job Description Junior Software Developer Office Based) - Laravel - PHP - JavaScript - MySQL - HTML5 - Vue.js - React.js - React Native Due to rapid growth, we're looking for a Junior Software Developer with assisting the development on our mobile and web based digital products, technical improvements, testing software and even building digital solutions from the ground up. Apply now the company ProdrammerHumor.io

Content Based on a true story: 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 wellgonna 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 l'm keeping those