In our previous post, we covered the basics of designing a REST API: defining endpoints, using HTTP verbs and performing common read-write operations on data. In this chapter, we’re going to introduce some advanced use and edge cases you may want to consider in order to give your REST API a sound and long-lasting design.
Learn More Through My Stories
What you need to know about REST.
If you are a developer and you’ve worked in any modern web application, I’m sure this term rings a bell for you. REST stands for Representational State Transfer. If you’re already familiar with the basics, hop over to our look at Advanced REST API design. If you’re in need of an intro, lets dive in and you’ll see why this architectural style has become a de-facto industry standard for back-end APIs.
Analogous Learning and the Path to Staying Curious
When I was 6 years old, I started taking swim lessons. It was at the swimming complex at the University of Tennessee, where I remember watching the diving team practice from the 10 meter platform in complete, terrified awe. Lucky for me, I started with blowing bubbles in the shallow end. Slowly, we progressed to a swimming stroke: the doggy paddle. Did you hear that right? The doggy paddle. The instructor was teaching us how to swim like a dog.
Wrap Up + Getting to Pilot
When we first started, we were refining a problem, onboarding your team, and setting up tools. Now, we’ll do the reverse.
How a simple list of emergent themes can save you time and money in digital innovation work
Emergent Themes tries to draw signal from all the beautiful innovation noise, that flurry of empathetic activity that characterizes innovation. Most importantly, these plain-language terms help us have a conversation to answer a key question: “What piece of this problem should we focus on first as we start prototyping?