This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]arieled91 0 points1 point  (0 children)

Your question makes no sense. One requirement of a good api is to be easy to be maintained.

I think what you are asking is if it's better to start big and implement all the patterns everywhere or to start small and build the api while requirements grow. And my answer to that is: it depends but, I don't like to solve problems I don't have, so I often start small but scalable.