The engineering questions you get asked, and the bugs you actually hit. Drawn, one mechanism at a time, in the order the videos ship.
You asked for a name and a price and thirty-eight fields came back. Every difference between the two is one trade seen from a different side — and the caching bill is where it comes due.
Every request came back 200 and nobody could buy anything. The last two digits have no categorisation role at all — and an error inside a success is a lie three separate systems believe.
REST is six constraints in one chapter of one dissertation, not a synonym for JSON over HTTP — and the spec's own example of getting it wrong is a link a crawler follows to delete your rows.
Not the definition. The four things you actually send, what each one is for, and how to find the one that's wrong.
