Post

Engineering management after the cost of code collapsed: “Investing in machine-checkable correctness is now among the highest-leverage infrastructure work an org can fund” karimjedda.com/engineering-...

Aaron Kimball

@gremblor.com

This is a great essay. I really appreciate the measure/assumption framing; agree with most of what follows. Something I've struggled with in my org lately is that "effort (point) estimates are based on 'complexity' (of typing code)" but *implicitly* bake in review time commitments for teammates.

26/7/26, 7:07 pm0 reposts0 likes

Aaron Kimball

@gremblor.com

26 July

If review_time = k * coding_time , k < 1, then this shakes itself out with a team's self-correcting point capacity target at sprint planning. But k >> 1 now. The wrong person is now estimating the wrong part of the problem. This has hamstrung planning accuracy. I need to analyze this better.