Unfortunately, estimating effort is one of the hardest skills for developers to learn. Projects often look easy on paper, but fall apart during development. Quick fixes can turn into long nights. Countless variables such as design problems, integrating with other systems, red tape, and unexpected bugs can hinder progress.
So so so true. Good thing there's a lot of material to learn how to TRY to be better estimating and also how to prevent ourselves from giving bad estimates.
However, many of devs(including myself) only find this material after we've suffered the problem.
If this is a new project, make sure you’re familiar with the team’s coding practices and standards.
Or try to add some practices and standards. Add docs were they lack. Try to leave the project better than you found it.
Well, really nice article. The reason I always gave about "why software is so difficult" is because of lack of specifications but the reasons listed here are really valid.
Bookmarking for future reference 😁
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
So so so true. Good thing there's a lot of material to learn how to TRY to be better estimating and also how to prevent ourselves from giving bad estimates.
However, many of devs(including myself) only find this material after we've suffered the problem.
Or try to add some practices and standards. Add docs were they lack. Try to leave the project better than you found it.
Well, really nice article. The reason I always gave about "why software is so difficult" is because of lack of specifications but the reasons listed here are really valid.
Bookmarking for future reference 😁