The ACC should be their first call to fix anything related to tiebreakers.

Not saying that it was OPI, but OPI can be called within 5 yards of the line of scrimmage if the offensive player initiates contact.

The backwards pass should have been ruled as an inadvertent whistle.

Comedy of errors.

Firing him and keeping Andrew Berry around is a travesty.

Baker off the injury report. May have healed enough.

Oh boy…

An equally scary version of this applies to operations: an engineer was using a LLM to do some tshooting, and the LLM decided to propose and run cmds to delete a prod CF stack. Permissions issues aside, this was also a failure of understanding what the LLM was trying to do and just accepting it.

Can’t wait until The Pitt is back!

An alternative approach is to think about ways that AI can accelerate the understanding of a service by engineers (and managers). This can help developers be more effective more quickly, and also help ensure that proper changes are being made and the service is being operated well.

Where I work you can’t push code to prod today without a code review, but I am concerned that there will be a level of rubber stamping happening too.
What will happen is that the no. of service issues and TTM will go up because the understanding of the service will decline.

This has been my biggest fear and why I actively discourage pure LLM coding with no review. There is so much understanding lost by using AI as an “answer machine.” And those same engineers need to operate the services that code is deployed in, which requires some level of understanding.

They needed the booming “The game is not over” over the loudspeaker.