Old Man Yells At Cloud (Services)

Content I think I forgot something. If you forgot, then it wasn't imprtant. aws Amazon Won Services Inc Invoice TOTAL This invoice is for the billing penod December - December 31 2018 Yeah, you're right.

Content aws Internet www.aws-shg.de abraws-shg.de 080097 05 222 Fr heute. Fr morgen. Fr Sie Share

Content Others: why do you always use i,j variabes in loops? Programmers: IT'S THE LAW

Content rAskReddit Posted by uworldtraveler100 10h What technology are you shocked has not advanced yet? 26.8k J 14.6k Share Award BEST COMMENTS RegulatoryCapture 4h A 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 4 928 J imtn 1h Who the heck wrote this ridiculous bill? git blame Ah. I did. 217

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

Content Or Medium 50 Coding Laws That Would Make You A Decent Programmer. Follow these laws or get fired. LAW 1: Avoid Comments At All Cost Comments have a way of being falsely true. They deviate the mind of the reader from what the code is actually doing to what someone else says it's doing.