|
You are here |
programminghistorian.org | ||
| | | | |
williamdurand.fr
|
|
| | | | | Designing a REST API is not easy. No, really! If you want to design an API the right way, you have to think a lot about everything, and either to be pragmatic or to be an API terrorist. It's not just about GET, POST, PUT, and DELETE. In real life, you have relations between resources, the need to move a resource somewhere else (think about a tree), or you may want to set a specific value to a resource. | |
| | | | |
mherman.org
|
|
| | | | | Let's build a RESTful API with Python and Flask. | |
| | | | |
blog.miguelgrinberg.com
|
|
| | | | | miguelgrinberg.com | |
| | | | |
www.softdevtube.com
|
|
| | | Programming history is filled with bugs that turned out to be features and limitations that pushed developers to make even more interesting products. We'll journey through code that was so 'bad' it was actually good. Along the way we'll look at the important role failure plays in learning. Then we'll tame our inner perfectionists and | ||