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

Exactly!

It has nothing to do with the programmer. It has everything to do with what projects really are today.

1. Undefined in scope even when defined 2. Problems to be solved (innovation) not solutions to be produced (production) 3. Filled with hidden complexities of potential infinite character.

Copied from another post of mine:

Time estimations is an industrial way of thinking applied to a post-industrial (and post-capitalist) world.

In the post industrial world time isn't the problem but rather project definition and scoping. In the industrial world the problem was already solved (machine was built, market often established and output depended on a few factors that could be adjusted. Need more output add more of X)

In the post industrial world every project is about problem solving and scoping. To put it into comparison.

If we apply post-industrial reality to an industrial world.

It means that each time a product needed to be done if not the factory, then the machines would have to be developed.

It will take many many years before time estimation will die, but it will happen.



Do you have a link to that post? I really like your summary here and would like to link to it directly, outside of linking to this comment.




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

Search: