Developer Marketing and Evangelism • Developer Experience and Advocacy • Digital Platform Strategy
How do you know an API endpoint is ready to be deployed? This checklist can form the basis of your own set of requirements to assure you maintain the quality of your API program.
I am frequently asked which API is my favorite, and it stumps me every time. I finally realized why.
The rise in security issues caused by poorly secured APIs should concern you. Audit your API to identify potential security issues, improve the developer experience, and continue to drive value for your engineers and your customers.
Low code development environments have a reputation among developers - often well deserved - of being mere "toy" applications. But low code as a development approach is rapidly maturing and worth a second look, even by the techiest of tech geeks.
A digital platform is more a way of thinking about your technology than any specific product or methodology. Rob Z. walks you through the details in this briefing.
Digital Transformation is more than just adopting technology. Rob Z. explains the details of Digital Transformation - and some of the gotchas - in this briefing.
APIs make your business processes and data more flexible and powerful. Rob Z. provides a non-technical explanation of this powerful concept with an emphasis on their value to the business.
If your APIs don't align with the goals of your business, your developer program won't succeed. And what are the goals of any business? TO MAKE MONEY. In this talk from Nordic APIs, Rob Z. describes the five business models that can drive revenue through your API program with their associated metrics.
In this follow up to his Five API Monetization Models talk, Rob Z. explains the value of turning your internal-facing developer tools and services into an external-facing program that can drive additional revenue and help your business better compete in the digital landscape.
Infra nerds love talking about stacks - web application stacks, devops stacks, data stacks, on and on - to describe the technologies that drive their domains. That made sense when you were building on top of other platforms - but what happens when everyone becomes a platform?