The Inevitable Return To Windows

Content Hacker Scripts 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 I'm keeping those

Content NO MORE COUNTING DOLLARS WE'LL BE COUNTING STARS

The Linux GPU driver experience is like walking through a minefield while juggling chainsaws. Beginners think it's just a simple "sudo apt install nvidia-driver" command, only to be greeted by the void of a black screen. But veterans? They're performing an elaborate interpretive dance routine - disabling SecureBoot, finding compatible kernel versions, dealing with Nouveau drivers that hate your existence, and praying to the open-source gods that X11 doesn't completely implode. The best part? After a decade of Linux experience, you're not better at installing drivers - you're just better at predicting which specific flavor of catastrophe awaits you this time.

Content 8:13 4 rimm. rean i'm seeing on Youture there is a way to erase it from the disk while installing Ubuntu. Is that how you did it? It should offer to intall ubuntu with a "dual boot" (side by side with windows) or to delete windows, but I would recomment that you do a dual boot. I'll check messages in the morning. good nite. Love you. okay, I'II see what I can figure out. Goodnight, love you too! 8:11 PM Just thought of why it's not working for you (I just had to get up and post this). The thumb drive that I gave is a boot-able drive. You'll have to find how to get pc to boot from the us. The setting is in the "Bios." Look up how access the Bios, usually by pressing one of the "F" keys while the pc is booting up (F2 maybe). Once this is done, insert the thumb drive in the us and start, or restart the pc I'll check in morning. Aa ProarammerHumor.ic

Content ProgrammerHumo

When your developer friend says they're "just customizing their boot screen" but actually they've replaced the UEFI splash with an anime girl calling them "senpai." Nothing says "I'm a serious professional who writes mission-critical code" quite like having your computer address you as a "good boy" during startup. The duality of programmers: can architect complex systems by day, creates waifu boot screens by night. The real reason they never let IT support touch their machine.