The Fourth Rule: No AWS

Content Gedda gedda AWS terms of service. (42.10) " will not apply in the event of the occurrence of a widespread viral infection transmitted via bites or contact with bodily fluids that causes human corpses to reanimate and seek to consume living human flesh, blood, brain or nerve tissue...

Content grey jena tweetsbyweber Dear recruiters, if you are looking for: - Java, Python, PHP - React, Angular - PostgreSQL, Redis, MongoDB - AWS, S3, EC2, ECS, EKS - nix system administration - Git and Cl with TDD - Docker, Kubernetes That's not a Full Stack Developer That's an entire IT department

Content sophie netcapgirl Follow guys be like " know a spot" and it's aws-us-east-1 2:08 AM 27 Oct 23 270K Views

Marketing vs. Reality: The eternal tech industry cycle. "Serverless" still runs on servers. "No code" still requires coding. It's like ordering a "meatless" burger and finding out it's just meat hidden in a different bun. After 15 years in the industry, I've learned that new buzzwords are just old problems wearing trendy hats. The facepalm is the universal gesture of a developer who just deployed their first "serverless" function and discovered they're debugging server configurations at 2 AM.

The joke here is multi-layered, like an onion made of pure irony. Internet Explorer, famously the slowest browser known to mankind, has a Twitter handle "@TheFastest" while reporting on an AWS outage. But the real punchline? The tweet is dated April 1st, 2019, has supposedly 94.8M retweets (more than any tweet in history), and Internet Explorer wouldn't even know about an outage until three years after it was fixed. It's like watching a tortoise report breaking news.

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