offering an API early in the life of a service is almost alway a good decision, even though it feels scary

Jul 23, 2014 · 9:10 PM UTC

11
70
1
109
Replying to @sama
@sama If you suggest that in office hours, send people my way :) readme.io
1
2
Replying to @sama
@sama even better if you build your product off it: then you make sure that it actually becomes a good api. worked well for us with close.io
3
Replying to @sama
@sama It is a very smarter way of scaling from the first day. cc:@irhythmgupta
Replying to @sama
All day long RT @sama: offering an API early in the life of a service is almost alway a good decision, even though it feels scary
3
Replying to @sama
@sama the hard part is justifying the burn to build and maintain as a startup - but it was a great decision for us
1
Replying to @sama
@sama is on the Twitter during meetings.
Replying to @sama
. @sama denouncing @paulg and his pseudo-humanitarian political agenda is an even better idea
1
Replying to @sama
API first! “@sama: offering an API early in the life of a service is almost alway a good decision, even though it feels scary”
1
Replying to @sama
@sama @a16z ... but only offering an API early in the life of a service is almost always a bad decision.
1
1
Replying to @sama
@sama: offering an API early in the life of a service is almost alway a good decision, even though it feels scary” #apifirst
1