In my career as consultant I’ve been at more than a handful of clients doing a similar job: find a solution for their problem, bringing a new architecture or improving an existing. But more importantly, I’ve trained many teams to improve the quality of their APIs with a wide range of smaller and larger tips and tricks. Spotting the same pain points or lack of certain patterns at almost every place, I decided it was time to write some things down. Glenn took it a step further and suggested to bring it as a workshop.
Over the coming weeks (after delivery of our workshop at Code PaLOUsa), I’ll write a series of posts under the ‘Enterprise API’ tag that you can find at the top of this post, describing the what and why. So stay tuned! Demo code will also be available on GitHub. Please note that while I’ll do my best to cover as many details as possible, this series contains years of experience in an ever changing technology landscape. Focus will be on concepts with example code, rather than production-ready code to bring your attention to all the aspects required.
Don’t hesitate to contact me if you’re a conference organizer and want to bring this workshop to your attendees, or you like to have a hands-on workshop at your company for a complete team instead of going through the series on your own. We’re also able to focus on specific topics or add in extra topics, not mentioned in the series, on request.