Dev Team Productivity - Technical Practices
Busyness and productivity are not the same thing in software teams. A twelve-point rundown of the technical practices — version control hygiene through observability — that actually move the needle.
devops
8 posts
-
-
Site Reliability Engineering Book Trio
What works for Google probably doesn't apply to the rest of us. Three SRE books — the SRE Book, the Workbook, and Seeking SRE — worth reading with that caveat firmly in mind.
-
Book thoughts and notes: Accelerate
Accelerate is the rare software book that brings data instead of opinions. It ties deployment frequency, lead time, MTTR, and change failure rate to real business outcomes — and has the receipts.
-
Shift Left on Documentation
Documentation is most accurate the day it's written and wrong when needed. Shift left by making docs executable, generated, or version-controlled — leave hand-crafted prose as the last resort, not the default.
-
Make Alerts Worthy
An alert nobody acts on is just noise with a timestamp. Five properties of a worthy alert — actionable, owned, contextualized, tunable, state-change aware — and why each one matters.
-
DevOps Book Trio
Most DevOps books are one person's opinion. This trio earns more trust. The Phoenix Project, The DevOps Handbook, and Accelerate in sequence: story first, then implementation, then data.
-
Continual Transformation
Renaming things Agile isn't transformation. What separates useful change from ceremony: eliminating waste and making small, steady investments in delivery capability that compound.
-
PromCon 2018 highlights
The most interesting Prometheus work in 2018 wasn't inside Prometheus. PromCon highlights: Grafana's query explorer, Thanos, OpenMetrics, model builder, and automated benchmarking from the ecosystem around it.