Related reading
Quoting voxium
A new engineer observes that a big company's reliance on AI for all artifacts (code, specs, tickets) leads to human bottlenecks. Despite AI generating everything, engineers work long hours because nobody understands the output, making the team slow.
Simon Willisonsimonwillison.net1 minFrom Individual Experiments to a Shared AI Practice: How Avant Scaled AI-Assisted Engineering
Avant replaced many personal AI‑assistant setups with a single, organization‑wide Claude Code configuration that embeds the company’s coding standards, project‑tracking links, and documentation. Treated as an internal product, the setup is versioned, owned by delivery engineers, and iteratively improved. The shared tool speeds routine tasks (scaffolding, tests, migrations, docs) and enforces cons…
Moove-itqubika.com2 minThe Shadow Factory: Why Your CI/CD Sprawl is About to Move Faster Than You Can Think
The article warns that unchecked CI/CD sprawl— orphaned pipelines, hard‑coded secrets, and permissive runners— creates a hidden attack surface, and that AI‑driven agents will amplify the problem. It recommends a governance layer with real‑time inventory, policy‑as‑code, and AI guardrails to bring the software factory under the same security rigor as production.
Codeshipcloudbees.com3 minBuilding Multi-Tier CI/CD Verification Gates for AI Pull Requests
AI-generated code often passes basic CI but contains subtle bugs like vacuous tests or off-by-one errors. This article details a multi-tier CI/CD pipeline using AST analysis, property-based testing, and mutation testing to catch these issues and annotate GitHub PRs with actionable SARIF reports.
SitePointsitepoint.com17 minAI Changed How Spotify Builds. What We Learned (and Fixed) About Quality at Higher Velocity
Spotify’s AI‑assisted development doubled change volume, exposing gaps in alerting, capacity planning, fleet‑update safety, and mobile quality signals. The team added end‑to‑end monitoring, priority‑based tiering, stronger rollback/observability, and expanded edge capacity. Data shows AI‑generated code isn’t a direct incident cause, but verification pipelines must scale with velocity.
