> I worked on something similar[1] and was totally hamstrung by front-end engineering. Well, frontend is my thing, so... The estimation is a total hack, though

> I worked on something similar[1] and was totally hamstrung by front-end engineering. Well, frontend is my thing, so... The estimation is a total hack, though. But it can easily be ripped out. > I can't tell if this a straight up adaptation of PERT 3-point estimates or not. It's probably not. I skimmed through some papers I found, but only to confirm the basic Idea I had to begin with. There is lots of room for improvement. > I'm wary of projecting from a few tasks to all tasks. Yes. This is intentionally just bullshitting. You are often very unsure of how big a task is going to get, and this bullshat number is sometimes as good as any number I can think of. And, sometimes the best way of getting the right answer is to give a wrong one. > My suspicion though is that it actually works (...) more because of what psychologists called "the unpacking effect". This is what I have noticed at work, and what I have (tried to) optimize the UI for.