When it comes to APIs, most people get things backward. The best way to create an API or any other interface is to start with the code that uses the interface. Write a program that uses the interface that you wish existed—an interface that makes your life easier and lets you do

I really don't like the notion of "ownership" when it comes to the code (or the associated notion of accountability). This is all about finding a single neck to wring. It's a form of blame, bullying, and control. It's a disease. Instead of ownership, go with collaboration. It's

It's never a good idea, in my experience, to split an application horizontally—into back-end and front-end subsystems assigned to different teams, for example, or into separate application and platform teams. Typically, back-end/platform interfaces are vastly more complicated