Rip Code 🕊🕊

Content G Closed miku-chan03 opened this issue on 18 Oct 2017 2 comments miku-chan03 commented on 18 Oct 2017 Contributor Hil I fixie wixied the JSON-api fucksy wucksie!!! xp I repwaced the Prototypes. func wiff a more -streamlined- kawaii Pwototypiee. funkywunks object that make the JS go sooper dooper fast!! XD starts twerking Can u pwease merge my pwull wequest senpai?!! UwU gaearon commented on 19 Oct 2017 Contributor what in the name of fuck O gaearon closed this permanently on 19 Oct 2017

OH. MY. GOD. The absolute TRAUMA of debugging for 12 HOURS only to discover it's some obscure cache issue with "Gumbies 3.0" (whatever the heck that is) and then trying to figure out what Gumbies actually does! 💀 The sheer AUDACITY of tech documentation that makes you scroll through 17 pages of meaningless buzzword salad! "Lean expressive sharding sandcube" and "watersliding phases" and "Woodchips playgrounds"?! WHAT DOES ANY OF THIS MEAN?! It's the perfect representation of modern tech - fancy words that tell you ABSOLUTELY NOTHING while name-dropping big companies to seem legitimate. And after all that scrolling, you're still left thinking "I have no idea what this thing actually does, but I guess I need it?" The circle of tech hell is complete! 🔥

Content Debugging is like being the detective in a crime movie where you are also the murderer. -Filipe Fortes Debugging ProgrammerHumor.to

The expectation vs. reality of coding is brutal. In your head, you're Captain Jack Sparrow - swashbuckling through elegant algorithms, conquering complex problems with panache. Then your fingers hit the keyboard and suddenly you're the bootleg knockoff version, struggling to remember basic syntax while Stack Overflow becomes your only friend. The transformation from imagined coding genius to "why won't this compile?" happens faster than you can say "missing semicolon."

Content WHEN MY CODE DOESN'T WORK AFTER HOURS OF DEBUGGING Kyle kvleve Computers. What a mistake 11:11 AM Sep 20, 2022 from San Francisco, CA Twitter for Mac

Content Roman Sharkov admin Downloaded a virus for Linux lately and unpacked it. Tried to run it as root, didn't work. Googled for 2 hours, found out that instead of uslocalbin the virus unpacked to usr bin for which the user malware doesn't have any write permissions, therefore the virus couldn't create a process file. Found patched . configure and . make files on some Chinese forum, recompiled and rerun it. The virus said it needs the library cmalw-11b-2.0. Turns out cmalw-lib-2.0 is shipped with CentOS but not with Ubuntu. Googled for hours again and found an instruction to build a . deb package from source. The virus finally started, wrote some logs, made a core dump and crashed. After 1 hour of going through the logs 1 discovered the virus assumed it was running on ext4 and called into its disk encryption API. Under btrfs this API is deprecated. The kernel noticed and made this partition read-only. Opened the sources, grep'ed the Bitcoin wallet and sent 5 out of pity. 19-50