Re:Frequently Forgotten Fundamental Facts about Software Eng...
by AnimalMuppet on Tuesday April 28, 2015 @01:09PM
(#9453784)
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.
[ Parent
| on HN ]
Re:Frequently Forgotten Fundamental Facts about Software Eng...
by nine_k on Tuesday April 28, 2015 @01:22PM
(#9453861)
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.
Re:Frequently Forgotten Fundamental Facts about Software Eng...
by penguat on Tuesday April 28, 2015 @02:52PM
(#9454412)
I'd add obviousness here. Make the design and code as obvious as possible. Simple and easy to understand.
Re:Frequently Forgotten Fundamental Facts about Software Eng...
by AnimalMuppet on Tuesday April 28, 2015 @01:27PM
(#9453896)
Correct. I guess I was thinking more agile rather than rapid prototyping.