Have you been attending Stackery’s Serverless Summer School? As a non-engineer, I’ll admit, I was a little nervous. Was it going to be over my head? Would I spend the entire Twitch stream furiously writing down all the terms I didn’t know so that I could ask about them later? Would my brain need some debugging after trying to download a bunch of information that I didn’t really get?

I’ve heard many conversations about the limitations of “serverless technology” ever since the concept was widely known. They often focus on how specific implementations of serverless are limited by certain aspects that the user doesn’t have control of. This seems odd to me because serverless isn’t a technology.

Now that you’re invited, here’s the lowdown: Starting this Wednesday, you get the unique chance to attend four weeks of live working sessions with some of the top minds in serverless. They’ll prepare you to build production-ready serverless applications with the best practices of AWS top-of-mind. Along the way, you’ll get the chance to earn awesome prizes as you unlock milestones like deploying a stack and finishing your app.

Starting today, any developer can locally debug and develop any Lambda function, in any language or framework, against live cloud resources with any IDE, for free. You don’t even need a Stackery account. This capability can be obtained by installing the Stackery CLI either automatically via the Stackery VS Code Serverless Tools Plug-In or manually alongside any IDE.

Every day that I commute home, I check Google Maps for the next Trimet bus arrival at the usual stop. There’s nothing wrong with this ritual but it always distracts or leaves me stalled for a few empty minutes. Ever the proponent of laziness automation, I decided to build a stack that will do this for me by texting incoming arrival times for my bus home.

Ben Kehoe wrote a post about AWS API Gateway to Lambda integration: How you should — and should not — use API Gateway proxy integration with Lambda. In his post, Ben gave a few reasons why he believes using API Gateway Proxy Integration is an anti-pattern. Ben does a great job summarizing how the integration works. He writes: The pattern that I am recommending against is the “API Gateway proxy integration” as shown in the API Gateway documentation here.