Re:How To Go From Idea To Launching With Paying Customers In...
by jasonlbaptiste on Friday September 17, 2010 @11:38AM
(#1701504)
If 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.
Re:How To Go From Idea To Launching With Paying Customers In...
by Swizec on Friday September 17, 2010 @11:46AM
(#1701531)
Yes, 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.
Re:How To Go From Idea To Launching With Paying Customers In...
by iampims on Friday September 17, 2010 @06:22PM
(#1703039)
Isn't it what SOAP + WSDL were supposed to solve?
Re:How To Go From Idea To Launching With Paying Customers In...
by mkramlich on Saturday September 18, 2010 @02:38AM
(#1703811)
no that's the next buzzword silver bullet. stay tuned next week for that one. ;)
Re:How To Go From Idea To Launching With Paying Customers In...
by F_J_H on Friday September 17, 2010 @12:19PM
(#1701654)
Specs 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."
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.