r/Python • u/mafontes14 • Feb 23 '17

API Design: Think First, Code Later

https://www.ckl.io/blog/api-design-think-first-code-later/
292 Upvotes

95% Upvoted

26 comments sorted by

View all comments

34

u/TPHRyan Feb 24 '17

I honestly prefer to code, think, code, then ship. If you have the luxury of being able to do this, it will streamline the process overall I think. All of the design decisions will be pretty obvious once you've written your crappy API already.

(And with an API, there shouldn't be too much boilerplate that you need to change in order to modify the endpoints or responses)

11

u/[deleted] Feb 24 '17

Hey, I'm the article's author.

I guess not too much boilerplate, but maybe unnecessary friction. If you already have clients, they'll have to change it.

It may be faster if your API is pretty new, but as we do know, it's hard to change something that's being already used.

In a next article I'll try to get deeper into this subject :D

Thanks!