Decide when rerunning a failed CI job supplies useful evidence, when it hides an unreliable test, and how to keep both outcomes visible.
A CI Retry Needs a Failure Policy
Posted on in Programming
Articles tagged with developer_productivity
-
-
A Slow Local Test Is a Product Decision, Not Just a CI Problem
Posted on in Programming
Treat slow local tests as a developer workflow investment by measuring iteration cost, choosing the right intervention, and assigning an owner to the result.
-
Platform Intake Triage Should Make the Next Decision Obvious
Posted on in Technology Management / Leadership
Give platform requests a small evidence record and a clear routing decision so support, incidents, exceptions, discovery, and funded work do not collapse into one invisible queue.
-
How To Keep Developer Platform Office Hours From Becoming Unplanned Work
Posted on in Technology Management / Leadership
Make developer platform office hours a fast path to useful guidance and clear decisions without silently converting support conversations into unplanned implementation work.
-
The Exception Backlog Is a Developer Platform Roadmap
Posted on in Technology Management / Leadership
Turn repeated developer-workflow exceptions into evidence-backed platform investments without treating every unusual request as a product requirement.
-
When Can You Finally Retire a Developer Tool?
Posted on in Technology Management / Leadership
Retire obsolete developer tooling with evidence about remaining dependencies, funded migration support, and shutdown criteria that end the dual-support burden.
-
When an AI Coding Agent Pilot Is Ready for a Team Default
Posted on in Technology Management / Leadership
Decide when to expand an AI coding agent pilot using evidence about task fit, review capacity, ownership, support costs, and reversible rollout boundaries.
-
Make the Safe Development Path the Easy One
Posted on in Technology Management / Leadership
Make reliable engineering work the convenient default by investing in fast checks, paved paths, visible evidence, and clear escalation boundaries for people and AI coding agents.
-
Developer Platform Health Signals That Lead to Action
Posted on in Technology Management / Leadership
Use a small set of platform health signals to locate costly engineering friction, choose an intervention, and verify whether the system improved.
-
What Should an AI Coding Agent Pilot Prove?
Posted on in Technology Management / Leadership
Run an AI coding agent pilot as a bounded engineering decision by defining the evidence, guardrails, and stop conditions that would justify its next level of use.
-
Give AI Coding Agents a Change Budget Before You Give Them a Repository
Posted on in Technology Management / Leadership
Give AI coding agents a bounded change budget so teams can expand useful autonomy with evidence instead of granting broad repository access on faith.
-
A Safe Developer Feedback Loop for AI Agents
Posted on in Programming
Build fast local checks, explicit CI contracts, and clear escalation paths so AI coding agents can make small changes with evidence instead of optimistic guesses.
-
How To Measure AI-Assisted Engineering Productivity Without Turning Developers Into Telemetry
Posted on in Technology Management / Leadership
Measure AI-assisted engineering through flow, quality, learning, and customer outcomes instead of surveillance metrics that encourage activity without improving delivery.
-
How To Design AI-Agent Handoffs That a Human Reviewer Can Actually Trust
Posted on in Programming
Give AI-assisted changes a compact handoff contract that preserves evidence, makes the review boundary clear, and leaves consequential decisions with an accountable human.
-
How To Turn Agent Investigation Notes Into an Engineering Plan
Posted on in Programming
Turn an AI coding agent's reconnaissance into a reviewable engineering plan by separating evidence from inference, naming decisions and risks, and defining validation before implementation begins.
