I’m not sure how many devs out there need such a guide. The barrier to entry for serverless isn’t quite so low as too entice many developers building out their first APIs without the necessary experience to anticipate the workarounds and concessions they’d have to make before attempting it, not least due to still niche nature of serverless. But as it happens I was struggling to preserve redirect URLs and state between endpoint invocations for OAuth 2.0 Auth flow without any session storage, and I figured I couldn’t have been the first.

I built my first, end-to-end, unsupervised, wholly-owned product this year. Here are my tweet-length thoughts in between manual build-deploy cycles.

I put off homework to make this list. I recommend you try to control for the hyperbole with which I’m inevitably going to describe my favorite music.

1. Deftones - Koi No Yokan

I’ve spent the last semester frazzled and scattered. I’m doing a lot and I’m accomplishing little. What do I do?

I discussed the motivations behind PWAs earlier. They’re just awesome. I don’t think the app as of yet necessitates a data store and we can probably get away with just passing everything as props but perhaps after a discussion with our designer that may change. As I’ve taken over backend duties our frontend engineer can take care of the executive decisions here.

Buzzword!

Following the advice of a friend I realized that I could have more fun learning a completely new paradigm of backend development - serverless. More specifically, Serverless… Framework.

I promised myself I’d write about the architecture for Rooms months ago but a semester later and here I am with only 3 published posts and a handful more sitting in the repo. I figured then I’d try writing an evolving article detailing not just my architecture but the reasoning and learning behind the development of Rooms like all those cool kids working at the cool companies with their cool dev blogs.