testplzignore

Police approving AI PRs without reading them: This is the way the world works now. Get with the times.

"You choose the AWS Region(s) in which your content is stored. You can replicate and back up your content in more than one AWS Region. We will not move or replicate your content outside of your chosen AWS Region(s) without your agreement."

> till the AI is happy

My god this is dystopian.

Joe Burrow weighs 215 lbs and makes $55 million per year. That makes him worth his weight in gold x4.

I'm still researching the average weight of a football field. Depends if it has rained recently.

LOL. I had to check if this was published on April 1st.

From a taxpayer perspective, it's such a waste to have multiple agencies doing their own unconstitutional surveillance. Why have two Ministries of Love when one would do? :)

The same demographics that are the most likely to have gone from working in the office to working from home...

I'm guessing the alternate billing flow will contractually require the app to "phone home" to Google with how much the user spent. Presumably will be part of the app review process.

Similar improvements have been made to improve colorfastness. Mixing new reds and whites used to consistently produce pink. Not anymore.

Most unrealistic prediction :)

Interesting how controversial Zig will be in the future :)

This is what jumped out at me as the biggest problem. A wild west deployment process is a valid (but questionable) business decision, but if you do that then you need smart people in place to troubleshoot and make quick rollback decisions.

Their timeline:

> 08:47: Configuration change deployed and propagated to the network

> 08:48: Change fully propagated

> 08:50: Automated alerts

> 09:11: Configuration change reverted and propagation start

> 09:12: Revert fully propagated, all traffic restored

2 minutes for their automated alerts to fire is terrible. For a system that is expected to have no downtime, they should have been alerted to the spike in 500 errors within seconds before the changes even fully propagated. Ideally the rollback would have been automated, but even if it is manual, the dude pressing the deploy button should have had realtime metrics on a second display with his finger hovering over the rollback button.

Ok, so they want to take the approach of roll forward instead of immediate rollback. Again, that's a valid approach, but you need to be prepared. At 08:48, they would have had tens of millions of "init.lua:314: attempt to index field 'execute'" messages being logged per second. Exact line of code. Not a complex issue. They should have had engineers reading that code and piecing this together by 08:49. The change you just deployed was to disable an "execute" rule. Put two and two together. Initiate rollback by 08:50.

How disconnected are the teams that do deployments vs the teams that understand the code? How many minutes were they scratching their butts wondering "what is init.lua"? Are they deploying while their best engineers are sleeping?

Imagine a world where every software update has hundreds of signoffs from companies across the industry. That is achievable if we work together. For only a few minutes a day, you too can save a CVSS 10.0 vulnerability from going unpatched :)