Number 1 tip for new API developers: split your public and private routes up. You'll be tempted to "build the API" for your client (esp. if you're full-stack and in control of the client!), but I guarantee you're wrong about what "building the API for the client" means. #webdev
This API I'm working on is a year-and-a-half old (as is my experience with it), and I'm finally at the point where the growing pains are being felt.
The main thing wrong with it is we crammed in all kinds of personal information into routes that should be isomorphic. We thought that would be convenient.
It is not convenient. #programming #webdev #fullstack-suffering
Here's a question you should ask: what if we go international? What if we want to use a CDN to cache this bulky route? If you don't make certain highly-trafficked, bulky routes isomorphic, you literally have cut your legs out wrt CDN's: YOU STRAIGHT UP LOSE OUT ON THEIR USEFULNESS. #webdev
