Irakli Nadareishvili CA Technologies
For decades now, we, computer programmers, have borrowed, copied and imitated the terminology and mannerisms of civil engineers. But truth be told, “software engineering” was never really like the architecture of buildings or bridges. In the “real” architecture the cost of a mistake is sky-high: if you make a mistake — a buildings will collapse, bridges will sink. In software engineering the cost of a “mistake” was always significantly lower: the predominant philosophy taught us to “just ship it” — we can fix mistakes, later, relatively cheaply.
With the rise of the Internet of Things, potentially millions of apps and devices will use APIs that we build. Any breaking change in our API can have severe effects on millions of consumers. The cost of making an early design mistake, the cost of a sloppy architecture is rising rapidly.
Let’s talk about how to build long-lasting APIs
This post is older than 4 years. External links has been removed
October 21, 2014 09:30
High impact blog posts and eBooks on API business models, and tech advice
Connect with market leading platform creators at our events
Join a helpful community of API practitioners
Can't make it to the event? Signup to the Nordic APIs newsletter for quality content. High
impact blog posts on API business models and tech advice.
Become a part of the world’s largest community of API practitioners and enthusiasts. Share your insights on the blog, speak at an event or exhibit at our conferences and create new business relationships with decision makers and top influencers responsible for API solutions.