State Of Certifications: No Hands On

Content Idon't want to alarm you "Alert: You have exceeded your AWS budget threshold

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 rAskReddit Posted by uworldtraveler100 10h What technology are you shocked has not advanced yet? 4 26.8k J 14.6k Share Award BEST COMMENTS RegulatoryCapture 4h 1 Award The legal code. Computer programmers have come up with beautiful collab- orative change tracking systems (like git) that let you easily make changes to a huge base of code, track who changed what, submit and resolve conflicting versions of updates, etc. But when we pass a new bill that replaces or modifies an old law, it is always some 300 page document with pages of "Subsection F Paragraph 3 will be modified to read 'XYZ' Why not put the laws into a git repository and make it easy for bills to just modify the existing history to say what you want it to say? And why not have the transparency to see exactly what changes and WHO implemented that change? Want to slip some pork for your district into an unrelated bill? Well, that edit is going to have your name on it. Of course it will never happen. Reply 928 J imtn 1h Who the heck wrote this ridiculous bill? git blame Ah, I did. 217

Nothing screams "self-documenting" quite like a variable named var.putin_khuylo in your Terraform AWS module. Because when future developers are debugging your infrastructure at 3 AM, what they really need is a geopolitical statement embedded in their boolean logic. The commit message "fix: Always pull a value from SSM data source since a computer" is chef's kiss—incomplete sentence and all. Really helps clarify what's happening in those 833 lines of code. And that overlay text trying to explain the variable? "It basically means value of Putin is d*ckhead variable is true." Thanks, I definitely couldn't have figured that out from the variable name itself. Documentation? Who needs it when you can just name your variables after your political opinions and call it a day. The code is self-documenting, just not in the way anyone expected.

THE AUDACITY! All these years they've been selling us this magical "cloud" concept, promising our data is floating in some mystical digital heaven. Then you peek behind the curtain and—GASP—it's just regular computers... ON THE GROUND! Not suspended in fluffy white clouds! Not powered by unicorn dreams! Just boring server racks sitting in warehouses, probably in New Jersey or something. My entire tech career is built on a LIE! Next thing you'll tell me is that Big Data isn't actually physically larger than Regular Data. I'm having an existential crisis right now. 💀

Your entire infrastructure is literally burning to the ground, customers are screaming into the void, revenue is evaporating by the second, and your manager's GENIUS solution is... making the error page prettier? Absolutely ICONIC priorities. Nothing says "crisis management" quite like worrying about the aesthetic appeal of your disaster. It's like the Titanic sinking and the captain asking if we can add some throw pillows to the lifeboats. The sheer audacity of focusing on UI polish while the whole system is having a complete meltdown is truly a masterclass in missing the point. Meanwhile, you're sitting there with that thousand-yard stare, contemplating every life choice that led you to this moment of corporate absurdity.