There's this notion surrounding AI-assisted coding that the entire process should be infinitely fast. People gnash their teeth and wring their hands because review takes longer than the generation, and testing even more so. So, as a thought experiment, imagine that all those bottlenecks go away. The process is now frictionless, and you can spit out eight months' work every eight hours, all day, every day. Eight months' work involves many UI changes, feature modifications and additions, etc. Let's say that 10% of the program changes during those eight months. As a user, do you really want to sit down every day, only to discover that 10% of the things that worked yesterday don't work anymore, that you'll need to learn 10% of the program all over again from scratch? A program like that is literally unusable. You spend 100% of your time dealing with the changes and 0% getting work done. The fact that software is released gradually over time makes changes palatable. The speed of change has to be within our capacity to deal with the change. A firehose of AI output is simply impossible to deal with.

If a story is bigger than 1 point, instead of trying to guess how big it is, just keep decomposing it until you have a set of 1-point stories. All stories, when sufficiently narrowed, are 1-pointers. There. That's easy. I like the lunar logic estimation cards. A story is either 1, TFB (too f'ing big), or NFC (no f'ing clue) [estimation.lunarlogic.io/]. "This is the way."