This tag archive currently includes 1 article. It is designed as a practical map of how this theme shows up across writing on software architecture, delivery quality, and engineering execution. Instead of treating SDLC as an isolated keyword, these entries trace how the idea appears in real system constraints, team decisions, and implementation tradeoffs.

Recent entries in this archive include The Pull Request is Dead: Surviving the AI Code Avalanche. Reading these together gives a clearer view of recurring patterns: where tooling helps, where process matters more than syntax, and where verification or coordination becomes the limiting factor.

A representative thread from this set: Code production is no longer our bottleneck. The newfound velocity of AI coding agents hasn't solved our problems; it has simply moved the bottleneck further down the pipeline, creating massive SDLC backpressure. The human "Looks Good To Me" on a PR is now the … Use this as a starting point, then follow the rest of the archive to see how the same problem evolves across different contexts and constraints.

Related tag themes that frequently appear alongside SDLC include AI coding, code review, verification debt, architecture. Those cross-links are useful when you want broader context instead of a single-topic view, especially for platform-level decisions and multi-team delivery work.

  1. The Pull Request is Dead: Surviving the AI Code Avalanche

    Code production is no longer our bottleneck. The newfound velocity of AI coding agents hasn't solved our problems; it has simply moved the bottleneck further down the pipeline, creating massive SDLC backpressure. The human "Looks Good To Me" on a PR is now the single biggest liability in deployment. It’s time to stop acting like typists and start acting like architects.