What's the most difficult programming concept you can explain in a tweet?
-
-
Replying to @tlakomy
Never write the API first. Write the code that does the thing, then write the code that uses the thing, then get the whole system working, soup to nuts. It should then be pretty obvious where the line between them is, and thus what the API should be.
8 replies 16 retweets 116 likes -
Replying to @tom_forsyth @tlakomy
Can we get
@cmuratori here?
Not because I want a holywar on the design principles(I don't), but because you two to go deep dive on this to gain more wisdoms.
Disclaimer: I'm not sure the aforementioned advice is contrary to what I've heard from Casey long time ago.1 reply 0 retweets 0 likes -
Funny you should choose Casey, since most of my API design experience was working on Granny. Which he wrote :-)
1 reply 0 retweets 3 likes -
Haha! Not only will I get wisdom, there's bonus stories!
1 reply 0 retweets 2 likes -
I don't disagree entirely, but I do to a certain extent. I feel like you need to write both sides somewhat independently, and meet them in the middle :) If you favor one side over the other, you often end up with accidental choices propagating one way or the other.
1 reply 0 retweets 6 likes -
Replying to @cmuratori @Kknewkles and
So, I tend to prefer writing the usage code first _if I know how I want to use the thing_. That way I can see what the easiest thing would be for the user. Then I write the implementation without thinking about the API at all. Then I try to converge the two.
1 reply 1 retweet 4 likes
If I _don't_ know how I might want to use this thing, then I start by writing the implementation and work backwards until it becomes more clear.
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.