Relying on a Repeatable Process
If you only build one API in your life, it’s not too important just how you do it as long as you get it done. However, for those who need to build lots of APIs—those whose job it is to convert designs into functional code—it’s valuable to have a consistent, repeatable process. Just as we covered processes for modeling, designing, describing, sketching, and prototyping APIs, we need to come up with a reliable process for the act of building the actual API.
The main benefit of a repeatable process is that it’s something you can show and teach others. A good process is also easily monitored. For example, in the design process, we can easily ask teams things like, “Have you completed your model yet?” or “Can you show ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access