Infra As React

Content WRITES UNMAINTAINABLE CODE LEAVES COMPANY

Content uSe tHe clOUd, YOu dOn't nEed to upDaTe aNytHing Action Required AWS Lambda end of support for Python 3.8 AWS Account: US-EAST-11 ProdrammerHumor.io

When your muscle memory betrays you during an outage... First you panic at Cloudflare being down, then you instinctively switch to AWS us-east-1, forgetting it's the region that crashes more often than my development server after a Friday deploy. It's like running from one burning building straight into another one that's somehow always on fire. The cloud giveth, and the cloud taketh away your weekend plans.

The internet is basically a Jenga tower of questionable engineering decisions. At the very bottom, we've got C developers manually allocating memory for dynamic arrays—because who needs garbage collection when you can have segmentation faults? Above that foundation of tears sits DNS (the system that translates human-readable website names into IP addresses) and the Linux Foundation (keeping the lights on while everyone else has fun). Then we've got the unpaid open-source developers—those magnificent souls whose thankless work powers 90% of the internet while they survive on ramen and GitHub stars. AWS and Cloudflare are the duct tape holding everything together, while AI dangles precariously off the side like an afterthought. Microsoft is apparently doing... something... with Angry Birds energy? Meanwhile, Rust developers are zooming around in their little rocket ship, telling everyone their code is "memory safe" for the 47th time today. And at the tippy-top of this architectural abomination? That's you, my friend, just trying to watch cat videos while the entire digital infrastructure—built on WASM, V8, and whatever "LEFT-PAD" is referring to—teeters beneath you. The miracle isn't that the internet works—it's that it hasn't collapsed under the weight of its own absurdity.

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 aws T'VE GOT COOL NAMES FOR MY SERVICES, LIKE GREENGRASS AND BEANStALK Azure I NAMED MY SERVICES AFTER WHAT THEY ASTUALLY ARE SO PEOPLE CAN UNDERSTAND WHAT THEY DO