The Most Fundamental Secret to API Success

I’ll be celebrating my fifth year as a Masherite in early July. It’s been a wild ride. In my very second week of work, I was asked to speak at a local meetup on behalf of the company on any topic I wanted relating to APIs. I could have chosen to speak on good RESTful design or how to design the underlying architecture to best support a truly scalable system, but those paled in importance compared to the topic I chose: Developer Documentation.

Five years later, I maintain that poor documentation is still the greatest hindrance to developer success — more so than monolithic legacy architectures, un-typed scripting languages, or byzantine release processes. Poor documentation can’t be fixed with something like microservices, or adopting the Go language, or integrating your code repositories with continuous testing and deployment tools. Documentation is a human problem that can only be solved by human intervention. https://goo.gl/1auHeX #DataIntegration #ML

It’s No Myth: A Guide to Taming the Hydra of Enterprise Integration

#ICYMI: As an experienced enterprise IT professional, you have undoubtedly faced a few Herculean challenges. Probably more than a dozen, even. But application integration is truly hydra-like: each enterprise integration project creates two interfaces that must be maintained to keep data flowing smoothly. Right now, your IT organization is fighting a losing battle, trying to maintain dozens or possibly hundreds of application and data integrations.

It’s clear that the current technology and tools your company uses for enterprise integration projects are inadequate; exploring the reasons why can help to define the requirements for the new application and data integration solution you’ll choose. You can think about those requirements in the context of five important questions you’re undoubtedly asking yourself right now: https://goo.gl/wAucnL #DataIntegration #ML