Blog

hero-book-blogAPI Developer Weekly – January 19, 2017 – Issue #145
A hand-curated weekly newsletter for API developers, published with permission from LaunchAny and CaseySoftware.

Subscribe to their newsletter to stay updated on the latest API trends and industry news.

 

Hot Topics

If your product isn’t documented it doesn’t exist
Along with the onboarding process and customer support, documentation is the “transfer layer” of knowledge for your customers. Documentation is an essential component in how a user transforms their intent into an outcome. So maybe not a small thing to ignore. [medium.com]

How much code do you need to know to create developer documentation?
Wood says tech writers who are learning to code often underestimate the degree of difficulty in learning code. To reach developer proficiency with production-ready code, tech writers will need to sink much more time than they feasibly can. As such, tech writers shouldn’t aspire to the same level as a developer. [idratherbewriting.com]

8 Great Examples of Developer Documentation
You just received an email from an angry developer. Something is wrong in your documentation, and the developer just spent hours figuring it out. Now it’s your turn to update the documentation and figure out how to avoid those issues in the future. But how? It’s hard to… by Zapier [zapier.com]

What Are The Goals Behind Launching An API Portal?
I was getting ready to do some work on a developer portal for a project I’m working on and I wanted to stop, step back and try to define what the goals in launching this portal are. [apievangelist.com]

[Video] User Delight Driven Design of APIs
Michael Hyatt discusses the main complains users have with APIs and ways to address them using early user acceptance testing, RAML, JSON schemas, traits and mocks.

IFTTT vs Zapier vs DataFire
DataFire is the iPaaS solution I’ve been waiting to see emerge and will be investing time into learning more about how it works, developing integrations and flows, and telling stories about what others are doing with it. [apievangelist.com]

The State of Mobile SDKs in 2016
Currently, there are thousands of SDKs available, so developers often ask us which ones they should choose. Here at MightySignal, our job is to shed light on this by providing marketing and sales intelligence on what SDKs are embedded across millions of mobile apps. [blog.mightysignal.com]

We reverse engineered 16k apps, here’s what we found
Out of 16,000 apps, most of the apps didn’t have any sort of key or secret in it. Roughly 2500 apps were found to have either a key or a secret of a third party service hardcoded in the app. Some keys are harmless and are required to be there in the app for example Google’s API key but there were lots of api secrets as well which definitely shouldn’t have been in the apps. There were 304 such apps… [hackernoon.com]

How One Developer Hardened His App Against API Failures
APIs are often prone to failure. That’s no surprise. But if your app is dependent on an API that goes down like there’s no tomorrow, what do you do? Thomas Roca, a stats researcher at the French Development Agency explains how he overcame the API developer’s dilemma. [highcharts.com]

Using An OpenAPI Spec As Central Truth In Stakeholder Discussions
This approach to defining a common data schema and API definition requires that all stakeholders involved become fluent in OpenAPI Spec, and JSON Schema, but is something that I’ve done successfully with other technical, as well as non-technical teams. This process allows us all to all be on the same page with all discussion around the Open Referral API definition and schema, with the ability to invite and include new participants in the conversation at any time using Github’s existing services. [apievangelist.com]

Let developers try your APIs without registration!
Developer: “It feels like the API provider is getting in the way! He wants: a full registration, with a username, password, my name, my address, security questions, maybe even credit card details. And then i am forced to participate in a click-through tutorial.” This is way too much! by mattbiehl [api-university.com]

Why I Still Believe In APIs–The 2017 Edition
As I approach my seventh year as the API Evangelist and find myself squarely in 2017, I wanted to take a moment to better understand, and articulate why I still believe in APIs. To be the API Evangelist I have to believe in this, or I just can’t do it. [apievangelist.com]

REST API Notes for 2017/01/17
In Northern Virginia, we’ve started that weird part of the year where winter and spring begin their tug of war. That usually means gray, overcast days that occasionally belch out a traffic-crippling blizzard. Thankfully, there’s plenty of great reading to be done inside. [tinyletter.com]

Upcoming Web API Events
A list of upcoming Web API Events, maintained by Matthew Reinbold

 

The Business of APIs

Why APIs are Important for Business
3 Ways APIs are Important for Business: 1. APIs are huge time-savers, 2. Businesses are creating apps that rely on APIs, 3. APIs help businesses focus [medium.com]

Businesses @ Work – IT will never be the same
An in-depth look into how organizations and people work today—exploring employees, partners, contractors and customers, and the apps and services they use to be productive. As we dug into the data, one thing became clear: IT will never be the same. The traditional role of IT is expanding beyond simply managing employees. The clear distinction between corporate apps and personal apps is fading away. And, we’re seeing early signs of a potential shift away from Microsoft Active Directory. [okta.com]

API adoption: Traditional industries lag
At the close of 2016, Gartner Research Director Mark O’Neill presented at both API Strategy and Practice (in Boston) and APIdays Global (in Paris) to share his insights into this year’s API trends. Top on his list was a discussion about how, while everyone talks about building APIs, the much larger impact of APIs is with their consumption. by Mark Boyd [networkworld.com]

7 Lessons Learned Building an API Startup
The word startup is one of those trendy silicon valley terms that’s been thrown around the last few years. With it come images of warehouses lit by Apple computer screens, being grinded down by young hipster like adults as they try to sell, sell, sell. by Ben Virdee-Chapman, Gabriella Leone [nordicapis.com]

What Organizations Need to Know When Deprecating APIs
One topic that comes up a lot in the API space is the decision of companies to deprecate an API’s version, or fully shutdown support for a popular API. Take the most recent example of Google, which silently announced that it’s shutting down support for its Hangouts API in January, 2017. by keshav vasudevan [swaggerhub.com]
Extracting Value from Data: The Rise of the API Economy
Increasingly, people are choosing to interact digitally with businesses, each other, and even objects. As companies search out ways to make use of the oceans of data being generated from all these interactions, many are opting to explore a business strategy that would have been almost unimaginable just a few short years ago – openly sharing proprietary information with other enterprises. by Leon Stigter [data-informed.com]

 

(Un)Related Topics

Technical Writer Ranks Among Best Jobs of 2017
Find out more about the average technical writer salary and learn where the best-paying metropolitan areas are for a technical writer across the country. [money.usnews.com]

Why Plain Text Will Boost Your Productivity as a Writer
Plain text writing may sound like a complicated concept to someone who grew up with text processors. But it is actually what writers did before text processors even existed: sit down in front of a typewriter and type words. When preparing for print, the text of a manuscript was then marked up by hand to indicate what typeface, style, size etc. [ulyssesapp.com]

Developing Microservices with Aggregates
Chris Richardson describes how to use aggregates to design modular business logic that can be partitioned into microservices. He also discussed his ideas on how to use DDD and CQRS concepts as a guide for implementing a robust microservices architecture. [infoq.com]

Google reveals its servers all contain custom security silicon
Google has published a Infrastructure Security Design Overview that explains how it secures the cloud it uses for its own operations and for public cloud services. Revealed last Friday, the document outlines six layers of security and reveals some interesting factoids about the Alphabet subsidiary’s operations, none more so than the revelation that “we also design custom chips, including a hardware security chip that is currently being deployed on both servers and peripherals. [theregister.co.uk]

 

Want to share something?
As always, if you want to chat, share a link, or make a suggestion, feel free to drop us a quick note using Twitter (@launchany and @caseysoftware) or by emailing us at: james@launchany.com.
Categories: Ecosystem, News

Leave a Reply

Your email address will not be published. Required fields are marked *