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

I agree when he says that trying to model your problem in a specification then write the software is doomed for failure.

I disagree when he seems to imply that you don't need to document what you're building.

Being iterative with software and specifications/documentations can lead to both good software and specifications.

Write a small amount of software, formalize, write some more, etc.



"I agree when he says that trying to model your problem in a specification then write the software is doomed for failure."

Is that a reasonable generalization?

Here is a case where divergence between the model and "reality" would be catastrophic: http://www.fastcompany.com/node/28121/print

I'm also interested in exactly how one would apply an iterative cycle of implement->test->formalize to this category of software? (Ooops. There goes the rocket! Back to the keyboard!)




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

Search: