News for hackers. Stuff that matters.
Re:APIs that developers should know about by toumhi on Monday December 13, 2010 @08:07AM (#2000323)
Why would you duplicate what other people have built before you? Everything that has been done correctly by others, you should use. Learning how to configure Asterisk and how to use Twilio doesn't nearly require the same amount of time.

I agree to some extent that you should not rely on other services without having any kind of replacement, but to say that you have to build everything yourself seems rather ill-informed advice...

Re:APIs that developers should know about by mike-cardwell on Monday December 13, 2010 @08:11AM (#2000334)
Given the choice between spending a day or a weekend building something in house, or using a remote web service, I will always bring it in house. Because it's ridiculous to rely on some remote service if you don't have to.

If it will take me a couple of months to replicate something which already exists as a web service, I will usually use the web service. If only temporarily.

None of the web services mentioned so far on this page seem significantly difficult to replace, and suggesting that people use them seems rather ill-informed advice...

Re:APIs that developers should know about by techiferous on Monday December 13, 2010 @08:24AM (#2000368)
I think it matters whether your business has found product/market fit. Before product/market fit, taking the time to build things in house increases risk--risk that you're wasting your time on a product no one wants. After product/market fit, it reduces risk--risk that your product that people are paying for will have reliability problems.
Re:APIs that developers should know about by metageek on Monday December 13, 2010 @10:27AM (#2000704)
>Given the choice between spending a day or a weekend building something in house

Remember that building it is not the only cost; you also have to consider the costs of maintaining it and keeping the servers running.