Ask HN: How do you give estimates on work?

1 point·reactordev··5 comments

In this era of agentic coding, how do you give business stakeholders estimates on the units of work that you do?

Are you still cataloging man hours?

Are you doing everything in story points?

How do you account for the time it takes the agent(s) to do the work?

This is a dilemma I have at work currently. I can estimate how long it would take me to do something but Claude?

> I can estimate how long it would take me to do something but Claude?

If I were in this situation, what I'd do is to continue to give estimates as I always have before, ignoring the use of genAI, and keep track of how much the accuracy of those predictions have changed. That would give me some real data on which I can begin to adjust my time predictions.

To do it any other way is to just be guessing blindly.

That’s just it. It’s dramatically changed.

By using my mind to reason about how long the task(s) will take, based on past experience of using the tools, processes and mental frameworks to achieve similar task(s) in the past? Has Claude really totally preempted even such critical thinking abilities?

Very cynical approach to the fact that for my teams, complex tasks that took a sprint are now being finished in hours.

Depends, do you want to give an honest answer? Do you have a stake in your employer succeeding?

Reply on news.ycombinator.com