What's the most difficult programming concept you can explain in a tweet?
-
-
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.
-
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.
End of conversation
New conversation -
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.
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.