dora-metrics
7 posts
Rushing feels fast but creates rework, bugs, and firefighting. Why pausing for refactoring, tests, and CI upkeep is an investment in speed, not lost speed.
technical-debt · testing · ci-cd +2
Each git event deserves a different GitHub Actions job: what to run on push, pull_request, the merge queue, and tag/release, and why routing protects lead time.
ci-cd · github-actions · devops +1
How high-performing teams shrink the lead time from code-complete to live in production, without trading away security or code quality. A guide for tech leads.
ci-cd · devops · dora-metrics +2
How high-performing teams keep security review from becoming a lead-time bottleneck: shift-left automation, risk-based gates, a paved road, dependency cadence.
ci-cd · devops · security +3
AI absorbs more of the implementation, so the framework name matters less than four feedback loops. A decision lens for tuning flow, cadence, WIP, and review.
leadership · agile · team-management +3
Where AI coding assistants actually help, why individual speed gains stall at the team level, and what to put in place before widening adoption.
ai-tools · productivity · github-copilot +3
Practical structures and guardrails that raise team autonomy without chaos, drawing on Holacracy, the Spotify model, and Team Topologies.
organizational-design · leadership · dora-metrics