by Ronnie Mitra
the sum of interactions between
the developer and an API owner
the emotive impact of API usage on the developer
You can't design for usability if you don't know who is using your API
effective API design is difficult
effective == meeting our design and business goals
Everyone tries to avoid
Less consistency between APIs
Focused teams = knowledge silos?
Fewer code dependencies, but implicit dependencies between APIs, datastores
Smaller APIs are easier to understand
Continous delivery and single-click deployment
Measure things (statsd, newrelic, logstash)
Dogfood things (build your own apps on your API)
Cross team pairing and collaboration
People can move between teams
Knowledge sharing sessions
slides from conf is comming soon
@kisPocok