{"version":"1.0","type":"rich","provider_name":"Acast","provider_url":"https://acast.com","height":250,"width":700,"html":"<iframe src=\"https://embed.acast.com/$/69ab3b7c7036d739021982df/69dd4bca2cfb2f5bcbaa90bf?\" frameBorder=\"0\" width=\"700\" height=\"250\"></iframe>","title":"I Looked At Amazon After They Fired 16,000 Engineers. Their AI Broke Everything.","description":"<p>What's really happening inside your codebase when AI writes code nobody fully understands?</p><p><br></p><p>The common story is that dark code is a security or engineering quality problem. But the reality is more complicated: it's an organizational capability crisis that is only going to get worse.</p><p><br></p><p>In this video, I share the inside scoop on dark code and what actually fixes it:</p><p><br></p><p>• Why observability and agent pipelines don't solve the core problem</p><p>• How spec-driven development forces comprehension before code exists</p><p>• What self-describing systems look like and why they matter at AI speed</p><p>• Where a comprehension gate catches what the first two layers miss</p><p><br></p><p>Every builder, founder, and engineering leader shipping AI-generated code right now faces a choice: treat dark code as an organizational discipline problem, or keep driving with the headlights off.</p><p><br></p><p>Subscribe for daily AI strategy and news. For playbooks and analysis: https://natesnewsletter.substack.com/p/your-codebase-is-full-of-code-nobody?r=1z4sm5&amp;utm_campaign=post&amp;utm_medium=web&amp;showWelcomeOnShare=true</p>","author_name":"Nate B. Jones"}