Not impossible, its akin to having a P vs NP problem. Properly estimating a software project takes just as long as developing the software itself. When people

Not impossible, its akin to having a P vs NP problem. Properly estimating a software project takes just as long as developing the software itself. When people want estimates they somehow assume they can be given on the spot, or at most with a few hours of work. Nothing further from the truth. A good software estimate is a project in its own right. It takes time, a deadline and a budget to break apart a software project, design a solution, identify its subtasks, identify its critical path, research alternatives, evaluate frameworks, tentatively assign tasks to teammates, write down an estimation report, discuss it with the customer, etc. And then you end billing the customer for 120 hours of work to conclude the project can be done in five days, give or take a week.