Click Ops Engineering

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 we consume the most ram nave you seen me with 100 tabs PC WHAT WAS THAT, PUNK? OWLTURD.COM G ProarammerHumor.io AMATEURS. PC 'AMATEURS. docker made with mematic

Content Am Devloper iamdevloper Every now and then, ping one of your competitor's websites using an IE6 VM. Keep them on their toes. 72418, 4:57 AM 760 Retweets 2,536 Likes

BREAKING NEWS: Trillion-dollar tech giant taken down by... *checks notes*... a blank field! 🤦‍♂️ Google engineers deployed code with ZERO error handling, no feature flags, and then pushed a policy with blank fields that created a null pointer that spiraled into a crash loop ACROSS THE ENTIRE PLANET in SECONDS! The internet's backbone CRUMBLED because someone couldn't be bothered to write an if-statement! And the best part? This disaster is from THE FUTURE! 2025! Time-traveling bugs are apparently Google's new specialty! 💀

Content No text found in image

Content Before Deep Learning THE 1 PROGRAMMER EXCUSE FOR LEGITIMATELY SLACKING OFF: "MY CODE'S COMPILING." HEY! GET BACK TO WORK! COMPILING! OH. CARRY ON With Deep Learning THE 7 DATA SCIENTIST EXCUSE FOR LEGITIMATELY SLACKING OFF: "MY MODEL'S TRAINING" HEY! GET BACK TO WORK! cere TRAINING OH. CARRY ON With Cloud Computing THE 2 DATA SCIENTIST EXCUSE FOR LEGITIMATELY SLACKING OFF: "My compute cluster is starting" HEY! GET BACK TO WORK! Starting compute session OH. CARRY ON