Just Not My Day Today

Content I contribute to open source projects on GitHub Professional README writer

Someone made a Spotify playlist called "Songs About Vim" and it's basically a cry for help disguised as music curation. The track titles perfectly capture the Vim experience: "What Am I Doing Here" (opening Vim for the first time), "How Did I Get Here" (accidentally entering insert mode), "Can't Get Out" (the classic :q struggle), "Asdfjkl;" (panic mashing keys), "Shut It Down" (desperately trying to exit), and my personal favorite - "Rebooting" (the nuclear option when all else fails). Every single song title is a mood that represents a different stage of the Vim learning curve. The playlist creator really said "I'm in pain but make it aesthetic." The fact that this playlist has 1,198 saves means there's a whole community out there bonding over their shared trauma of being trapped in a text editor.

Content have computer issue google issue reddit thread recommends program that does the exact thing i need github link oh no "open source" OH NO no exe install instructions are 1000 words can only be run via cmd download doesn't include dependencies "how to use" is even longer than install instructions ten million commands that does shit no one has ever needed name of program is "issue fixer" to fix issue you need a 200 word command fuck this go back to reddit thread "just change this registry key" go to reg.edit change a single "enable" to "disable" problem instantly fixed why the fuck is every single github program so bloated and non-user friendly? if your program doesnt have a UI or at the very least a fucking exe your degree should be revoked

Content What are the 7 deadly sins of programming? John Purcell. Creator of CaveOfProgramming.com Updated Dec 2, 2017 Upvoted by Les Howie, Software professional for 40 years. and Hasib Al Muhaimin, IOl participant '13, '14, '15, ACM-ICPC World Finalist 2016 Author has 5.9k answers and 9.3m answer views 1. Using spaces instead of tabs. You should always, always use tabs, not spaces. 2. Using tabs instead of spaces. You should always, always use spaces, not tabs. 3. Not using auto-formatting. Forget all that tabsspaces rubbish, what's wrong with you - auto-format your code and then people won't have to look at vour weird ideas about brackets and spaces. 4. Using IDEs, which have features such as auto-formatting and nicely- coloured buttons. All code should be written in vi or Emacs, thus ensuring the purity of the programming experience. 5. Not using IDEs. No-one wants to pay for all the time it's going to take you to type things that you could have done at the click of a button, or scroll up and down using some ridiculous key combination invoked using LISP. 6. Failing to learn C and C. It's really important to learn the two absolute essential languages. You think Java is just as good? Fine, write me a real- time control system for racing cars in Java and I'll believe you. 7. Learning C or C when you could be using something modern like Java instead. Admit it - all your schedules involving C or C overrun by five years. And even then the software turns out to have critical flaws that Java would not even have allowed you to create. 8. Overrunning the end of an array. 356.1k views View 11.9k Upvoters View Sharers

Content not a real user 1 IDGAF about your pronouns, I just want to know if you use "" or "we" when documenting a bug that you caused. 10:46 AM Mar 30, 2021 Twitter Web Client

OH. MY. GOD. The AUDACITY of trillion-dollar companies balancing their entire digital empires on the backs of sleep-deprived programmers who code for free in their underwear! 💀 Picture this: a MASSIVE elephant (that's our global tech infrastructure) standing on a beach ball (open source software), which is somehow being held up by two tiny ants (those poor, unpaid open source devs who survive on ramen and Stack Overflow karma). Next time your bank app crashes or your favorite website goes down, pour one out for the unsung heroes maintaining that random Python package your ENTIRE FINANCIAL SYSTEM depends on. They're probably fixing critical bugs between Zoom meetings at their day job!