| HN Mirror

> Mostly it's because I'm facing a problem I don't know how to solve. And I'm expected to somehow predict when it'll be done.

Does your team allow for knowledge buying tasks? For example, if our team needs to implement a continuous integration solution I might suggest to first create a research task to evaluate the tools available. Once we have that knowledge we can choose the best option for us and create the task to implement it. The way you can sell this is by saying, "I can give you an estimate now but I'll know a lot more after a few hours researching the problem. If you give me that time then I can give you an estimate with a higher level of confidence."

> Another scenario is when I'm asked for updates but in reality the status hasn't changed

I've struggled with this as well. Especially when the person asking for the update is not technical and therefore has a hard time relating to the complexity of the problem. In this situation your instinct may be to tell the person what you think they want to hear. Something like, "I'm figuring out the solution and should be done soon." I know it's uncomfortable but you are better off being honest about your progress. Tell them that the problem is more complex than you initially thought and you are having to do more research to find the right solution. Don't forget that research is part of the job so looking for solutions is doing work. Don't feel bad about that.

With that being said, there is nothing wrong with asking for help from other developers when you are stuck. Asking for help is a sign of strength. It is good to try solve problems on your own before asking for help but do not drive yourself crazy. I have spent far too long banging my head against the wall looking for solutions. These days I am much more comfortable asking for help.