2) The code written using your API by people with 1-2 weeks of experience with it (not you, not experts) looks pretty and idiomatic
Show this thread
Tests of whether a developer-facing library API is any good: 1) You can follow a step-by-step tutorial one day, then the next day go through the same workflow from memory, without looking up any docs
-
-
-
3) You frequently come across implementations for use cases *you never anticipated*, that you didn't even know your API could do
Show this thread -
4) Complex (>10 files) projects written with your API by average developers remain as readable as single-file scripts
Show this thread
End of conversation
New conversation -
-
-
This is the exact blueprint that everyone should follow
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Good stuff. I wish tests like this could be automated, especially as the library grows. We're releasing a client-library very soon. Would love to get some initial feedback.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.