Re:How to Version an API
by nradov on Thursday June 08, 2017 @04:29PM
(#14516956)
Never say never. It's generally impossible to predict how an API will have to evolve over time in response to changing requirements.
[ Parent
| on HN ]
That's true. However, I think this falls under YAGNI [0]. If you happen to get to a point where you have to change your an entire API rather than evolve what you have, you should consider it a new, separate API rather than instruct all client developers to plan for it up front. Plan for evolvability and handling changing requirements up front.
And how would you name this new API? Bob? Or version 2?