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

In addition to what brianmcc said: Given that the requirements are going to change, what are you going to do about it? The ability to change rapidly gives you a chance (not certainty) to respond successfully to a requirements change.


What certainly helps:

* Having small, self-contained, loosely-coupled modules.

* Having an extensive test suite for each module.

* Having small (or zero) amount of technical debt.

* Talking to your customers constantly, preferably before you commit a lot of resources into a new development.

Easier said than done, but definitely not impossible.


I'd add obviousness here. Make the design and code as obvious as possible. Simple and easy to understand.


Correct. I guess I was thinking more agile rather than rapid prototyping.




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

Search: