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

> An example of a contract in which it is useful have wiggle room is hiring a company to build a website for you. The best process for building a website necessarily includes discovery and continuous decision-making about what to build, so a long and prescriptive contract that spells out every product feature on day one will most likely result in a crappy final product and/or a ton of change orders and amendments.

The discussion seems to be about allowing wiggle room in an otherwise 'non-wiggly' contract, which doesn't seem to be the situation you're describing. Your suggestion clearly isn't that the long and prescriptive contract should be drawn up and then repeatedly amended, but presumably is rather that the initial contract itself should provide a mechanism for easy changes; and contracts enforced by technology, like any others, can be created in this way.



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

Search: