85$ BILLION Developers spend approximately four hours a week on “bad code,” which equates to nearly $85 billion worldwide in opportunity cost lost annually Bad Developer eXperience is the Joker of the API Economy, burning billions of dollars while just watching the flames. @Jarkko_Moilanen
DEVELOPERS The amount of skilled developers is limiting development More easily usable tools and APIs can increase the developer base and speed in development @Jarkko_Moilanen
TO MARKET Getting product to markets fast is essential. Great Developer eXperience with tools and APIs can significantly reduce the time to market timespan. @Jarkko_Moilanen
GOAL Provide easy access to data and efficient tools to foster creation of applications. Make world more developer friendly Improve the developer experience in everything @Jarkko_Moilanen
EXPERIENCE Creates value (solves a problem) Reliable Low learning curve Self-service Up-to-date accurate documentation Support Unified and consistent @Jarkko_Moilanen
GOAL WITH LIMITATIONS Maximum positive developer experience for the platform (developer) consumers without killing the internal developer experience. @Jarkko_Moilanen
CRUCIAL ROLE @Jarkko_Moilanen The Developer Coefficient report 2018, Stripe & Harris Pol, More than 1,000 developers and more than 1,000 C-level executives
EXPOSED APIS • Microservices architecture • Lots of internal APIs • Identity API • Broker API • Product API • …. • Developer needs logical entities • Product and data from same • As few API calls as possible • No chatty APIs ”Your and my primary concern requires compromises. Let’s use HAProxy / API management to solve this”
OPEN API • Internal choice • Reuse efficiency • Fading ecosystem • Not possible to use in Slate based documentation • ”Consumer’s choice” • Default and expected • Growing ecosystem • Tooling grows • Can be used in Slate ”Use RAML, I’ll make a tool to handle gap between Slate and RAML”
Custom tool Slate Github RAML 6 Code examples 40+ Open API spec Slate formatted markdown Build static html pages Stripe style 3 column API documentation Served via Github pages under own domain Change in Github master automatically fires regeneration and deployment of API Docs ALWAYS UP-TO-DATE API DOCUMENTATION docs.oftrust.net
“They [Insomnia] tend to address the bugs and feature requests in GitHub pretty fast”. “I initially switched to it [Insomnia] simply because the `hosts` bug made Postman unusable” [Insomnia] easier for both new users and experienced users, as well as just having more useful features, and most critically - less bugs.
EFFICIENCY WINS Internal developer experience is more important in the beginning to assure development speed Find tools or build processes to satisfy 3rd party DX needs derived from internal DX.