{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Good Tech Companies ","title":"A Hitchhiker's Guide to the Slopocalypse","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/3c4bfd93\"></iframe>","width":"100%","height":180,"duration":343,"description":"\n        This story was originally published on HackerNoon at: https://hackernoon.com/a-hitchhikers-guide-to-the-slopocalypse.\nHow to survive the AI coding “slopocalypse” with automated PR tripwires, daily reviews, and two key engineering metrics that keep AI-generated code under contr\nCheck more stories related to undefined at: https://hackernoon.com/c/undefined.\n            You can also check exclusive content about #ai-and-machine-learning, #software-engineering, #developer-tools, #devops, #code-quality, #engineering-productivity, #cybersecurity, #good-company,  and more.\nThis story was written by: @deployfriday. Learn more about this writer by checking @deployfriday's about page,\n            and for more stories, please visit hackernoon.com.\nDon’t panic about the “slopocalypse.” Instead of relying on careful reviews alone, set up automated tripwires for oversized PRs, zero-review merges, critical-file changes, and stale PRs. Use a daily digest and track just two key metrics: time to merge and change failure rate.","thumbnail_url":"https://img.transistorcdn.com/HZ9CRzf5js9DK86xzUVMWBRbXYwg4dA8xVXJGVzpL6Y/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8xMTNl/MjgwMmI0ZmEzNThj/YmJiOWNiN2UyZmRm/MzY3My5qcGVn.webp","thumbnail_width":300,"thumbnail_height":300}