Topic
Engineering Practice
Testing, reviews, diagnostics and the habits that keep software changeable as teams and tools change.
Measure the AI Review Queue Without Inventing Reviewer Effort
Delivery times are not lead times, elapsed is not effort, and five approval notifications can be three accepted tasks. Measure the review queue honestly, then model capacity.
When an Agent Says Done: Resolve Each Claim Against What Was Delivered
A passing test run survived a filter edit and the receiving import never ran. Track claims with their subjects so the next session knows what is valid, stale, failed or missing.
AI Makes Drafting Faster. Why Is the Team Still Waiting?
Follow twelve changes through drafting and review: a fourfold drafting speed-up saves real effort, barely moves delivery and doubles the queue. What studies measure, and how to measure yours.
Your AI Chat Cannot Carry the Team's Architecture
A clean invoice rename breaks a monthly export because the reason lived in an old chat. Record the decisions agents would erase, make them executable, and put them where work starts.
Who Owns AI-Written Code When Everyone Reviewed Something Else?
A three-line cleanup patch deletes pinned files after four green checks. Follow the hand-offs, find the one test that stops it, and give ownership real information and control.
AI Can Finish the Task and Still Leave the Junior Developer Behind
Finishing a task, explaining it and adapting it are different skills. What controlled studies show about AI help and learning, and a mentoring practice that keeps the speed.
Why Publish Technical Writing When AI Can Explain the API?
An assistant answers the question you asked. An article chooses the question, gives a claim an address others can challenge and puts rare cases back into the public record.