I’m zoomed in to read what they’re saying on the bottom right and was disappointed.

It make sense for a wrapper layer to do this and I had to fight against APIs that didn’t. If I make a single HTTP call that wraps multiple independent API calls into one, then the overall HTTP code should reflect status of the wrapper service, and the individual responses should each have their own code as returned by the underlying services.

For example on one app we needed to get user names by user id for a bunch of users. To optimize this, we batched calls into groups. The API would fail with an error code if one of the user ids in the batch was bad or couldn’t be found. That meant we wouldn’t be getting data for any of the users in the batch and we didn’t know which userId was bad either. Such a call should return 200 for the overall call and individual result for each id, some of which could be errors.

First I saw jelly beans, then I noticed the arrangement and saw touching tips, then I looked for what else could be taken in that direction and noticed the clearly intentional double penetration.

Sawyer started writing games in Z80 assembly. Assembly language was definitely something you would use to program games back in those days.