Very Inefficient But Entertaining

Content Seth Rosen sethrosen Them: Can you just quickly pull this data for me? Me: Sure, let me just. SELECT FROM someidealcleanandpristine.table thatyouthinkexists 1:42 PM 20 Apr 20 Twitter Web App 3,161 Retweets 20.5K Likes

Content WHO WANTS GOOD DOCUMENTATION WHO WANTS TO WRITE GOOD DOCUMENTATION

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

Ah yes, the classic "temporary solution" that somehow survives three system migrations, two CTO changes, and the heat death of the universe. That duct-taped code snippet from 2012 labeled "TODO: fix later" is now running critical infrastructure at Fortune 500 companies. The only thing more permanent than a temporary fix is the existential dread of the developer who has to maintain it.

Content Watching a bug disappear after adding a print made with mematic ProarammerHumor.io

Content 0 null