Lobsterslucascarlson.net · 27 August 2026 · 2 posts · not counted as a party

August 24, 2026 · Lucas Carlson For a few years I have kept coming back to one idea from Cloudflare's Durable Objects: an object with a name. One single-threaded object per identity, addressed by name, with durable state attached. A shopping cart, a chat room, a game table, a device, a document, an agent run: each one is an object. Calls to one identity run one at a time, so two requests can't corrupt the same cart. Calls to different identities run in parallel. Kenton Varda's team shipped that, and it removes work the rest of us usually do with a database, Redis, a queue, and a pile of locks. I have spent twenty years building that pile of locks, in Rails apps, in Node services, and once, regrettably, in a spreadsheet importer. When the Durable Objects model finally clicked for me, my main reaction was frustration that it only ran on one vendor's edge network. I'm not alone in wanting this. Ryan Dahl's celld recreates the model as a self-hosted daemon: your VMs, your object-storage bucket, the Workers API without Cloudflare. It's a good project. But celld solves it at the infrastructure level, where you run i

Figma blogfigma.com · 26 August 2026

Welcome to Workflow Lab, where we present a sample workflowWorkflow lab: Deploying designs directly with Figma MakeThe handoff from design to code doesn't have to be a one-way street. This workflow shows how a designer can connect a codebase to Figma Make, make the changes directly, and bring the whole team into review—right up to the PR. using Figma products and tools.Workflow fact sheet:Figma products: Figma Design, FigJamTools: Figma MCP server, Code Connect, use_figma, generate_diagram, search_design_system, generate_figma_design, get_variable_defsTeam: Product designer, design systems lead, software engineerQuestion to solve: What if your coding agent’s output could be production-ready sooner?The engineering team at Radicle, a fictional STEM learning app, is moving faster than ever. Work that used to take weeks now takes days, or even hours. Still, this speed isn’t getting them very far; their AI-generated code strays from design specs more often than not. The team gives their coding agent screenshots and dev tickets to work from, but it’s not enough to get the outputs right, and the team gets stuck reworking them.What i

LangChain bloglangchain.com · 26 August 2026 · 6 posts

Today, we’re excited to release a redesigned LangSmith product homepage as well as improved support for resource organization within your workspaces. These updates reflect our ongoing insights into how engineering teams build, optimize, and iterate on their LLM applications. In this post, we will walk through our updated beliefs and how they guided our design.Our approach to redesigning the LangSmith homepageThrough collaborating with thousands of developers and companies, we’ve observed that they work across three main areas when building LLM applications: observability, evaluation, and prompt engineering. To reflect the critical role each plays in an effective developer workflow, we’ve split our LangSmith product homepage into these three areas.ObservabilityThis section in LangSmith includes Tracing Projects and Dashboards.One of the biggest recommendations for AI engineers is to “look at your own data” — and LangSmith enables this by helping users identify issues and understand their LLM application’s performance over time.Tracing Projects are collections of traces emitted from your AI application.

Vercel changelogvercel.com · 26 August 2026 · 60 posts

Python projects can now use routing rules to set response headers or rewrite requests to internal paths, including apps built with FastAPI, Django, and Flask.The Vercel CDN evaluates rules before requests reach your application, so changes apply without a new deployment.For example, this FastAPI app serves a /new route:main.pyfrom fastapi import FastAPIapp = FastAPI()@app.get("/new")def new_route() -> dict[str, str]: return {"message": "New route!"}Defines the /new route the rewrite below targetsTo send requests for /old to that route, create a rewrite from the CDN tab in your project dashboard or with the Vercel CLI:# Add a rewrite (staged automatically)vercel routes add --ai "Rewrite /old to /new" --yes# Review staged changesvercel routes list --diff# Publish to productionvercel routes publishCreating and publishing a rewrite with the Vercel CLIPublished rules take effect immediately across all regions, and you can roll back to a previous version from the History tab.You can also manage rules from Python with the vercel SDK, which wraps the Vercel REST API. add_route stages the rule, and update_route_version publishes it:add_route.pyfrom

Cloudflare blogblog.cloudflare.com · 24 August 2026 · 8 posts

You likely noticed the recent redesign of the Cloudflare Blog. We added dark mode, modernized the look and feel, and made a lot of other small improvements along the way.What you might not have noticed – well, except for those who are more terminally online – is that the redesign was part of a much bigger migration project. On Wednesday, August 12, we moved the blog to EmDash, a content management system (CMS) built especially to work on Astro and with Cloudflare.We’ll take you into the migration story – what we learned and how EmDash got better – as well as into the benefits we’re already seeing from a new platform.We are Customer ZeroAt Cloudflare, Cloudflare itself is Customer Zero. This means that we use our products. And – in use – we make them better for ourselves and our customers.This is a very real cultural value at Cloudflare. The burden of proof is on you if you want to use an external vendor. Why can’t that team support you, what gaps are there, why can’t those gaps be filled, and are those “gaps” true requirements?This preference is even enshrined in our internal engineering standards, known as our Codex.We don’t just buil