It has been measured that changing more than 25% of software incurs more than 100% of the cost. So your mileage may vary.
have fun.
It was a reply I made to another friend and previous co-worker on twitter a while back that was talking about software estimation. It wasn't a comment on any other blog post or hackernews story.
I was thinking I should edit and elaborate on it into a full blog post at some point, but that would also require setting up a blog ;P I didn't take the time to write this up to the standards of an adversarial blog aggregation audience. And I don't care to defend it as such or in detail. It's meant to outline a broad point I think is true, but not to be ironclad in it's argument.
Anyhow, no cherry picking or anything unethical going on here.
Not that it's necessarily bad, but it is formulaic.
I dislike accurate estimates.
I'll do them, but I'm happy when I do it in 3x the time, not sad. And I certainly don't feel like I wwasted my time.
I just can't seem to find any employers or customers who feel the same way.
"You mean you didn't have a complete design for that bridge before you started building it??"
"You mean you waterfall designed and implemented your YC app project??"