What Canisay

Content Hey man, you see those guys over there? Hey man, you see those guys over there? They use Vim They use Emacs

Content Jakub Kozlowski kubukoz okay github, I know my builds are shit but no need to be passive aggressive about it Build Failed X The build failed, just like the previous build. 5:03 PM Apr 2, 2020 Twitter Web App 2,295 Retweets 186 Quote Tweets 13.6K Likes

The bell curve of intelligence strikes again! The graph shows the classic IQ distribution where both the lowest and highest intellects prefer GUI, while the average "galaxy brain" in the middle insists on using command line. It's the perfect representation of programming elitism. The beginners use GUI because they're scared of the terminal. The absolute geniuses use GUI because they value their time and sanity. Meanwhile, the "I-read-half-a-Linux-book" crowd is frantically typing commands they memorized from Stack Overflow, convinced they're superior for doing things the hard way. The true enlightenment is realizing both have their place—but where's the fun in being reasonable?

Content boo boo ProgrammerHumor. boc sudo boo CO !!!

Content What are the 7 deadly sins of programming? John Purcell, Creator of CaveOfProgramming.com Answered OCt 30 : Upvoted by Hasis A Munaimin, IOl participant 43, 44. 45, ACM. ICPC World Finalist 2016 and Jessica Su, CS PhD student at Stanford 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. 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 your 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 vou to create. 8. Overrunning the end of an array. 124.8k Views 3.448 Upvotes

Oh, so we're calling it "Seven Laws" when there are EIGHT rules? Already off to a brilliant start. But honestly, this is the most sacred scripture ever written in the tech world. Rules 1-5 are basically just screaming "BACKUP YOUR STUFF OR PERISH" in increasingly desperate ways, like a paranoid sysadmin having a meltdown. Then Rule 6 casually drops the nuclear option: uninstall Windows. Rule 7 follows up with "reinstall Linux" because obviously that's the only logical solution to literally everything. And Rule 8? Turn your egg whites into meringue. Because when your production server crashes at 3 AM and you've lost everything because you ignored Rules 1-5, at least you can stress-bake some pavlova while contemplating your life choices. Honestly, the progression from "make backups" to "become a pastry chef" is the most relatable career trajectory in tech.