Earlier quoted context omitted.
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.
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.
How To Go From Idea To Launching With Paying Customers In 8 Steps
41–44 of 44 posts
Re: How To Go From Idea To Launching With Paying Customers In 8 Steps
#42Great 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…
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."
Re: How To Go From Idea To Launching With Paying Customers In 8 Steps
#43I think this post is great but the period after launch is seriously underexposed in all these 'how to start-up' articles. Typically, if you're a hands-on person with the right attitude sooner or later you'll figure this part out. Posts like this can help you ease the pain a bit but then what? You've just launched, you have a few paying customers (but not enough to be profitable), your initial press powder has been sh…
Re: How To Go From Idea To Launching With Paying Customers In 8 Steps
#44Earlier quoted context omitted.
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.
Isn't it what SOAP + WSDL were supposed to solve?