3 ms·
Why not? For nearly any user-facing program, merging the design and requirement gathering¹ with programming brings only good things. 1 - Including user testin
by marcosdumay 6y ago
Why not?
For nearly any user-facing program, merging the design and requirement gathering¹ with programming brings only good things.
1 - Including user testing. It's worth putting a lot of time into the process design just to have user testing concomitant with programming.
- geophile 6y agoMy experience is mostly server-side, and there, I have found that smushing these things together leads to sadness.
- marcosdumay 6y agoOh, non-user facing programs is the land of well written specs, tests before implementation, design before implementation, and all the old school academic markers of good software engineering. Yeah, you really do not want to program those before deciding their architecture. But the experience is far from universal.