Guess I Have To Watch

Content me my friend's code my code 1. 7.71. 4 763

Content 0 vs NULL

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 LEFT EXIT 12 Read the documentation carefully Trial and error until it works Hardcore programmers

That moment of existential crisis when you realize you're either training your replacement or your future headache. Nothing like wondering if this new dev will be the one who actually reads documentation or just another copy-paste warrior who'll break production with Stack Overflow solutions. The real question isn't whether they're smart—it's whether you'll spend the next six months fixing their "creative interpretations" of your codebase.

Content FBI FBI Google How to re-attach a detached head Google Search I'm Feeting Lucky Google How to re-attach a detached head Git Google Search I'm Foeting Lucky