Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I see this mistake in project planning as well: I'm asked to scope how long it will take to complete module #1, then how long it will take to complete module #2, then module #3, etc. but in reality they all end up going hand-in-hand but depend on some common work that's "invisible" to the planners.


You sort of have to go along with it if you want to estimate. The perfect plan and estimate only happens after the completion date.

There are so many unknown deps and unknown opportunities to optimise at the start of a project.

You find those out as you get in the weeds and as the ICs dream a 1am about their code and bring that idea in the next day.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: