KothuRoti
I'm Not Reading Your AI-Generated Design Doc
OpenAI model proposes and proves Physics result
The $14 Burrito: Why San Francisco Inflation Feels Higher Than 2.5%
The creator of Claude Code's Claude setup
Sara Paine – Why Russia Lost the Cold War
DuckDB DuckLake Extension
How to Get More Headcount
Modeling Impact of LLMs on Developer Experience
49ers receiver Ricky Pearsall shot during robbery attempt in San Francisco
Google gives up trying to elimintate cookies
Re:Story Points Are Pointless, Measure Queues
on Tuesday July 16, 2024 @05:02PM (#40980299)
My personal experience with story points is that the number never really mattered, but the process of the team discussing how to rate the complexity of a task was very useful. In terms of having utility of estimating how long something will take, I personally have never been able to translate story points into a reliable indicator for that for many reasons (e.g team changing, domain changing, variability in operational load outside of development work).
Overall I tend to avoid using story points, but on the few teams I worked on who really wanted to use it, I always framed it around building shared understanding rather than a metric that is actually useful for estimating work.