It’s go time!! The @Flightcontrolhq mini-documentary is LIVE! Watch and drop your thoughts in the comments 😃

👀

TanStack AI is now in Beta! TanStack AI is no longer just a text-generation library with extras bolted on. TanStack AI has first-class dev experience for: ✅ Text and Streaming Structured Data ✅ Tool Calls ✅ Summarization ✅ Image Generation ✅ Video Generation ✅ Audio Generation ✅ Realtime voice chat ✅ Middleware ✅ Lazy tool discovery ✅ Code Mode ✅ Host-side MCP ✅ Orchestration (still experimental) ✅ Pluggable debug logging ✅ Isomorphic devtools All with per-model type-safety that actually matters!

Executor v1.5 is live! Highlights: - Sources -> Integrations - Full GSuite support - Run tools from the web - Integrations now support multiple accounts - Revamped product UI - WIP Docker and Cloudflare deployable versions Lot of love went into this one, hope you like it!

Pulled the plug on coderabbit. @greptile is just so much better these days.

Excellently written insight to what startups are actually like inside: zchmael.substack.com/p/start…

What conferences do you recommend for quality and deep technical talks?

So is workos.com/auth-md ID-JAG sign up flow already dead? Cloudflare removed it. And seems workOS is not even using it 🤔

Ready for display at @DaytonAirShow next weekend!!! Cleaned and glistening after an afternoon of rides.

I used the new AWS MCP server this week, and it’s MUCH better than earlier iterations. Mostly because it has code mode! I used it to find and nuke unused resources in our dev account. And to find cost optimizations in prod account. aws.amazon.com/products/deve…

It’s true

Man, AI is truly a product person's dream because it's so easy to implement heavy weight things that greatly enhance UX but would be super hard to prioritize the effort in the past.

Ok PR review in Linear is 🤯 So FAST. And the AI walkthrough is really good.

Don’t do a deck, do a memo. Eliminates all the visual cruft so you focus on the content.

Your cloud infrastructure feels complicated because the 3 core components live in different systems: 1. Infrastructure-as-Code. Your Terraform state and history is in something like Terraform Cloud or, God forbid, your local machine 2. Code deployments. Your ECS/k8s deployments are in CI or some other deploy controller. 3. Metrics, logs, cost tracking. Maybe you’re suffering with AWS Cloudwatch or Datadog. Now how can you expect developers to make and monitor changes effectively with this fragmentation? Soon we’re shipping something groundbreaking that solves this in a way every platform engineer will love 👀

We're finally shedding the .so (thank you Somalia!), and using the .com for @NotionHQ. And for this beautiful moment, I want to share a fun story: Back in 2018, I had just joined Notion, and one of the first things @ivan asked me to do was figure out how we could own notion.com. I had never done a big domain purchase before, so I reached out to a few domain brokers to understand the landscape. We tried different brokers, kept things anonymous, and attempted to surface a price the seller might consider. A year went by… nothing. Meanwhile, it was pretty clear this was only going to get more expensive as we grew. We needed a different approach. A fellow founder connected me to a broker who took a very different tack. Less transactional, more long-term relationship builder. He spent months getting to know the domain owner. Turns out owner was a fellow entrepreneur in the west coast… and a huge Grateful Dead fan. So we figured, why not get creative? Something beyond just price. So I called up our investor Ronny Conway and asked if there was any way he could help set up a private meeting between the domain owner and the Grateful Dead. Ronny is one of those people who somehow makes impossible things possible. A week later he calls me back: “New York City. Halloween. 15 minutes after the concert. Done.” The broker went back to the owner with an offer: some cash, some equity, and a private meeting with the Grateful Dead. That got his attention. He didn’t take the band meeting in the end, but he did lean into the equity (great call, in hindsight). We shook hands, and a few weeks later, the deal was done. I’ve been waiting years for the day we move our product to notion.com. Looks like 2026 is finally the year. Safe to say I’m unreasonably excited about this update!

Our AWS Fundamentals Newsletter just crossed 12,500 subscribers! 🎉 We started sending out deep dives on AWS back in 2022! What we ship here regularly:

I've got an agent in a loop optimizing a renderer with the goal to minimize frame times (and tests to measure). It got times down from 88ms to 2ms and allocations down from ~150K to 500. Sounds good, right? Wrong. This is exactly why agent psychosis is a big fucking problem. As an experiment, I rewrote the Ghostty core render state in Go, with access to identically laid out data structures as Ghostty and the exact same validation tests. I made a purposely naive renderer (simple, correct, but slow). 88ms per frame with 150,000 allocations (horrendous, lol)! I then kickstarted a Ralph loop to bring the frame times down. I told it it can't modify input data structures or the public API or tests (they're correct), but it can do anything else it wants. It got to work. It has worked for about 4 hours. I've spent around $350 on this experiment so far. The results? 88ms => 1.5ms 150K allocs => ~500 allocs Incredible right? Nope. My hand-written renderer I ported has frame times (same benchmark) of ~20us (0.020ms) and 0 allocations in the update path. This is the problem with psychosis and lacking systems understanding. If you don't understand the system, you're going to accept that this is an incredible result. If you understand the system, you'll see better solutions immediately and can do roughly 75x better on throughput. The people who blindly trust agent output are in the former camp. They're sheeple, overdrinking from a fountain of mediocrity. Standard disclaimer: I use AI all the time. I like AI. The point I'm making is to not blindly accept results. Think. Analyze. Learn.

We just finished migrating from Lambda to ECS at @sazabi. At first, everyone on the team was super excited about Lambda. We loved the idea that endpoints would scale “infinitely” and that we didn't have to manage any stateful hosts. But in practice there were too many gotchas. For example, Lambda has a maximum size on the env variables you can include in the Lambda environment. This seemed very weird and dumb. We would occasionally add a large environment variable and it would cause the function to no longer work 🤦🏼‍♂️ There is also a max size on the bundle itself. Meanwhile, the local development story for Lambda was really weak. We tried using SST to provision Lambdas that relayed local traffic back to our machines, but it didn’t work well and left us a bunch of orphaned Lambda functions in our dev account that needed cleaning up. We replaced this approach with something much simpler: a dev.ts script that wrapped Lambda functions in an @honojs server to make them callable over localhost as if they are normal servers. This was okay but still felt a bit hacky. Of course, I am obliged to mention Lambda's Achilles' heel: cold starts. That was also a pain point. In the end, the cost associated with Lambda outweighed the benefits we originally thought we'd receive. We gave up on them. Now we're back on containers. Everything is fast. Local development is ergonomic - no hacks required. Deployments and rollbacks are straightforward. It's a shame that serverless development on Lambda still doesn't quite live up to its promise. Companies like @vercel make the serverless experience way better but AWS hasn't caught up. We may introduce Lambda again in the future for burst capacity but for now we’re completely off. Doing things the old fashioned way 👍🏼

Everyone saying this, you want Slack to start charging for each message instead of per user?

AI agents can now hit any of 15,000 AWS API operations through one managed endpoint! AWS MCP Server is GA! 💪 My "AI AWS" setup so far was super duct taped Now there's one official, simple solution! Three tools you get out of the box.