4 ms·
Great list, but I don't think you need the detailed spec. Same problem as usual in developoment: the spec will be outdated by the time you're even half done, wh
by Swizec 16y ago
Great list, but I don't think you need the detailed spec. Same problem as usual in developoment: the spec will be outdated by the time you're even half done, when you're finished with the first version of the product your detailed spec will be so woefully out of date (or a huge time sink to keep updated) that you'll end up rewriting it.
What you do need is a defined documentation of your internal/public API's. If the developers don't know how modules talk to one another that's a recipe for fail. Then just to keep everything coherent, a rough skeleton to keep everyone on track. Basically a mix between your step 2 and step 5.
- jasonlbaptiste 16y agoIf you're doing a developer heavy app that requires an API, the API documentation is insanely critical. I don't think I emphasized this enough. I've been a complete lunatic (in a good way) about the API docs, response calls, etc. You can have things ghetto at first I guess, but having detailed responses is very important.
- Swizec 16y agoYes, being pedantic about responses and stuff that's flying around is vital. We can agree on that. But keeping an insanely good db documentation and a bunch of other stuff feels like overkill.
- F_J_H 16y agoSpecs are almost useless, but the process of writing a spec is invaluable. Disclaimer - Ripped off from my favorite Douglas MacArthur Qoute: "I have always found that plans are useless, but planning is indispensable."
- zb 16y agoIt was Eisenhower.