I've seen tighter formations of Canada geese eh.

My doorbell camera kept saying screaming was heard every time I came home, so I oiled the door hinge. 😅

How I block unwanted traffic from reaching my serverless API with CloudFront. speedrun.nobackspacecrew.com/blog/2026/07...

Blocking Requests with Lambda Function URLs - Speedrun

Blocking unwanted Lambda traffic

speedrun.nobackspacecrew.com

At @cascadiajs.com 2026, I overheard some people talking about Iowa. Turns out they also went to Iowa State University. Although they graduated 15+ years after me, they asked if I'd had Gadia, the database structures professor who wrote his own book. Yes, and here's the doodles I drew on his book.

Anyone else notice improvements to log ingestion speed with lambda and CloudWatch dashboards? It used to be up to a minute before my logs were visible in a dashboard, but now it seems almost real-time.

This swag cup may be the worst I've ever used. Holding the rolled handle is awkward enough, but the mouth feel of the rolled lip on the rim is even more immediately no. It will be used to hold my jankiest pens.

Longform YouTube videos should be called YouTube pants.

The serving size is 3/4 of a pickle. A wholly unreasonable unit. Presumably to have the calories round down to 0.

I'm a fan of this surrounding logs feature in the new CloudWatch Logs Analytics console.

If you've ever lost progress in Gmail for Android because you've opened a link then needed some info from the email and had to back out of the form you were filling, change it to always open links in browser: support.google.com/mail/thread/...

Submitted a PR to the lambda-perf repository to enable visualization of performance trends over time. For example, coldstarts for llrt on arm/.zip/512MB have gotten slower. See more here: github.com/maxday/lambd...

Way back I wrote an Alexa skill to tell me if it was recycling week. It effectively did a n%2===0 on the week of the year. After 8 years of node updates I can confirm it's faster and easier to just look out the window and see if my neighbors' bins are out.

They've surrounded our transfer station with roses. It's surprisingly effective at limiting the stank.

The woodcock with artistic liberties and the shrew. Doodle circa 2011.

The baby Steller's Jay is out barnstorming.

Since everyone forgot how to write json by hand after the AI meteor strike of 2021 caused permanent darkmode, Speedrun 1.55 can now generate the necessary json config to wire your GitHub markdown to your AWS accounts with just your Identity Center start url. github.com/No-Backspace...

Journeyed to Wisconsin for some cheese therapy. Shullsburg Creamery's muenster melts different and cures ails.

Finally maxed my ESM score.

Good news! That 50ms coldstart latency regression that appeared when using the AWS Javascript V3 SDK on Lambda with Node >= 22 is now fixed. github.com/aws/aws-sdk-... Update your dependency to v3.1011 to get back in the fast lane. Comparing my patched v3.1006 to v3.1011 shows no delta.

I ran my benchmark overnight to confirm there wasn't much improvement when turning on NODE_COMPILE_CACHE with Lambda Coldstarts. It's less than a 10ms improvement. There may be benefits with larger packages but for my setup (200K zip file) it isn't worth the trouble.

I experimented today with enabling NODE_COMPILE_CACHE to see if it would make Lambda coldstarts faster. I was able to create a .zip file with the cache from a previous run. I verified node used the cache successfully with NODE_DEBUG_NATIVE="COMPILE_CACHE". It didn't reduce the coldstart time 🫠.

LLRT v.8.1-beta has the fastest p50 InitDuration by 130ms. But if you measure E2E time from the client (what you should measure), it narrows to 79ms over AwsLite and 118ms over a modified AWS v3 JavaScript client on Node 24. This is likely due to the size of the LLRT binary being ~5MB.

Anecdotally I've noticed Lambda nodejs coldstart latencies trending down but visualizing the improvement using the daily maxday numbers is hard: maxday.github.io/lambda-perf/ I pulled the data and graphed it. Indeed, it's showing a 20-30ms improvement since November last year. Here's nodejs on arm.

Getting the client ip address when using a Lambda Function Url generally works, but sometimes you get a spoofed one. In this article I cover how to workaround the undocumented mangling Lambda does to the `x-forwarded-for` header. speedrun.nobackspacecrew.com/blog/2026/03...

Obtaining caller ip address with Lambda FURLs - Speedrun

When x-forwarded-for lies

speedrun.nobackspacecrew.com

I discovered that if you use Lambda furls, the x-forwarded-for header is truncated to the leftmost value. If you front your furl with CloudFront, the ip in that header is spoofable. CloudFront appends the viewer ip to the value of x-forwarded-for. Workaround is: github.com/aws-samples/...

TIL I was still using http 1.1 to connect to my api which supported http3. Because http3 is still kind of broken in Firefox: bugzilla.mozilla.org/show_bug.cgi... and when you enable http3 in CloudFront using the CDK, it disables http2. github.com/aws/aws-cdk/...

TIL you can get edge location in your CloudFront Functions. docs.aws.amazon.com/AmazonCloudF...

Hello darkness my old friend. I just updated to JQuery 4.0.0. Ready for 10 more years of $.

PSA: There is a performance penalty when using named exports with ESM import vs. require on built-in node modules. This is why the AWS JavaScript V3 SDK has 50 ms slower Lambda coldstarts on Node 22+. Some notes here: github.com/aws/aws-sdk-...

Look, the plating and bread choice leaves room for improvement. But the flavor of my latest Persian-American cuisine; the sumac avocado toast slaps.