> use of AI has indeed lowered the story point cost
It should not have. At least not significantly. Points should represent complexity, risk and overall effort (review burden, testing burden, dependencies, etc.), and so AI should increase velocity before it decreases story point estimates.
Over time, if a team's baseline delivery model genuinely changes, then reference stories can be recalibrated, but casually saying "AI lowered the point cost" is usually a smell that points are being treated as time estimates.
This is the same reason points should not = days even without AI. Velocity is what tells you if a team is getting better through training, tooling, hiring/firing, or process improvements. Re-pointing the same class of work downward hides the gain.
> I don’t want APIs, I want agents to use the same CLI tooling I already use that is locally available.
I do not want agents using the same elevated auth I have via my CLI tooling. One hallucination with your gh cli and the blast radius is every repo you have write (or worse, admin) access to.
MCP lets you scope tokens down (on supported platforms), or at minimum gives you something you can revoke independently.
The real cult is the engineers who refuse to shift their perception of what "good" or "quality" means in a world where humans, for the most part, won't be reading or writing code anymore.
I get it, existential threats are scary, but you can't just shit talk them and hope they go away.
Welfare should rightly fund "survival" and "levelling the playing field" resources, but charity can offer more than that - it can offer quality of life and a sense of community/belonging. It's nice to be around other people who are going through the same things, and people who support you.
So I think charity will always have a role, both financially and socially.
It should not have. At least not significantly. Points should represent complexity, risk and overall effort (review burden, testing burden, dependencies, etc.), and so AI should increase velocity before it decreases story point estimates.
Over time, if a team's baseline delivery model genuinely changes, then reference stories can be recalibrated, but casually saying "AI lowered the point cost" is usually a smell that points are being treated as time estimates.
This is the same reason points should not = days even without AI. Velocity is what tells you if a team is getting better through training, tooling, hiring/firing, or process improvements. Re-pointing the same class of work downward hides the gain.