> I've not known a dev who made accurate enough estimations to avoid a crunch. And yet after three years at my first job, I could easily do a quick breakdown o

> I've not known a dev who made accurate enough estimations to avoid a crunch. And yet after three years at my first job, I could easily do a quick breakdown on a project, assign a three level complexity to each step (easy, medium, hard), put an amount of days corresponding to the selected complexity (to be reviewed after each project), add 25% for unforeseen events and contingency and my estimates were accurate enough most of the time. It is not difficult to properly do rough estimates. Most developers just refuse to invest the time necessary to do it properly and sadly for some as the answers here already illustrate I do believe it’s because they think of themselves as special snowflake rather than team player.