Jev week is HERE - kicking off with a 30m intro to @typesafeai Jev with yours truly. In this ep I cover: - what is Jev and what makes it different - the 3 types Jev can return - the $100k use case that cost me $0.09 - some fun product ideas to inspire you Consider this your starter Jev ep - with a follow up on Weds with the one, the only @johnlindquist on his 28 (!!!) fun Jev use cases. 👉 Full ep on YT: piped.video/watch?v=-KIBgpGA…

Exactly, it’s never been about the code, it’s about solving problems and having to write the code was the way to achieve the goal of solving the problem. Now you can focus more on the solution and how to frame it, worrying less about the code.

100% this. Performance hits were worth it to improve human productivity, "time-to-solve" for real customer problems, and confidence when shipping (this is why I am still a big TS defender) Most of these issues are solved now. Time to rethink everything.

Two things I'm sensing I need to prepare my team for in the coming months: (a) Headless software (b) Deterministic vs. Probabilistic UI What does the role of Designer look like when (a) users are interacting with your product via agents only, (b) UI is generated on the fly?

Claude can now help you build evaluations and hillclimb on them. In this article, we share guidance on eval design & skills that Claude Code can use to improve your applications. claude.dev/blog/automating-e…

open source is core to so much cloudflare does today is the first day of @cloudflare birthday week, so here are a bunch of big updates to open source projects we maintain + some new ones: 1. we introduced forge — a new, free, OSS pipeline for auto generating SDKs, CLIs, docs, and libraries 2. cf cli — forge is in production and cloudflare is the first customer! our CLI now supports so much more than just workers 3. vinext 1.0 — what started out as a slopfork is now powering many organizations' production next.js apps 4. emdash 1.0 — the open source CMS that runs our blog (that we operate our network for) 5. 4 months of voidzero, speeding up the dev (and agent) toolchain — oxc compiles react.js 10x faster, vitest 5 is up to 50% faster, tsgolint is now stable (and up to 18x faster than eslint) and more!! 6. experimental preview of native rust in cloudflare workers! 7. big update to kitesurf — our open source agentic browser that runs on workers. webmcp and all 8. BEACON — open dataset of web performance data for you and your agents to go play with and explore forever blown away for how much cloudflare can ship in one day? as if we didn't ship a bunch of major announcements last week and have a whole week ahead still...

this has become one of my most used prompts recently: > restate in your own words what you think my goals are and what the problem i'm trying to solve is

Hi, Tomorrow we are re-opening the Pro $200 subscriptions to new subscribers, but together with it we are also changing how we calculate the usage for it. In effect, if you do the math, it will net out at half the dollar in API spend compared to the old Pro $200 plan. Now that it's said, let me explain why this is happening and why you will still get more work done than if you were on the Pro $200 subscription one month ago. (a) We didn't want to compromise in other ways and are committing to not reintroducing the 5h limit, so that you can fully use the weekly usage when you want. (b) On the subscription, we guarantee that over time you always get more work done and with an increasing level of quality. This means that you will continue to get more value per dollar spent as a result of models getting more efficient and us passing down the improvements in the form of API price reductions. (c) We don't want to put an incentive on ourselves to artificially inflate the API list prices to make it look like you are getting a lot (and workaround it through discounts, etc). Instead we want to continue to both rapidly reduce prices and increase capabilities of models on the API. This week we introduced GPT-6 Sol and GPT-6 Luna at 50% of their previous price. Over time, we see prices go low enough that it makes sense for most to buy usage as needed without there being a significant gap between what you get in a subscription and what you get in the API for a dollar spent. (d) Tomorrow, we are adding more things to the subscription that won't draw on the usage, I won't reveal what that is yet. I wanted to be transparent before all the big announcements tomorrow. Lots of new exciting things are coming to the subscriptions that will make it super compelling, but I wanted to make sure to share this change ahead of time so you can all understand it before we shower you with good news. Codexingly, Tibo

personal update! i joined @OpenAI a year ago to rethink how we work in a world full of agents. tomorrow, we get to show you what we’ve been cooking 🍿 future is bright. dm if you have ideas or thoughts on making chat or codex better, ill build it

We are releasing cf, our new command-line tool that mirrors the entire Cloudflare API and supports programmatic TypeScript configuration. We are also open-sourcing Forge, our internal SDK generator. cfl.re/3VECjml #BirthdayWeek

Wow, things are getting really rad now.

Pretty excited for DevDay tomorrow. We have found a new thing.

Peter Steinberger, the creator of OpenClaw, open-sourced his entire agent setup The core idea is one folder that every agent on his machines reads from. A single AGENTS.MD holds his rules, and a script symlinks it into ~/.claude/CLAUDE.md and ~/.codex/AGENTS.md This way Claude Code and Codex always follow the same instructions. Every other repo gets one line at the top: READ ~/Projects/agent-scripts/AGENTS.MD BEFORE ANYTHING. Change a rule once and every project picks it up. Skills work the same way. 69 of them live in one place, each with a short description the agent reads to decide what to load, and scripts/sync-skills links them into both agents. Fork it, replace his rules with yours, and delete the skills you do not need. His AGENTS.MD is full of his own hosts and accounts. 6.6k stars, MIT - github.com/steipete/agent-sc…

We saved you a seat. See you tomorrow for the OpenAI DevDay keynote: openai.com/live/

Introducing Claude Sonnet 5.5, the second model in the Claude 5.5 family. It’s a clear upgrade over Sonnet 5, runs more than 30% faster, and costs up to 30% less for most work.

EmDash 1.0 is a stable, open source CMS built for Astro, with agent-friendly workflows, secure sandboxed plugins, and a decentralized registry that keeps publishers in control. cfl.re/4iXWjKx #BirthdayWeek

There is no silver bullet or perfect prompt but if you do hard core engineering (not related to LLMs themselves but instead how you apply them) the craft gets recursive very very fast. People keep asking me about what skills I use and how I prompt LLMs and the answer shocks folks. I don’t pre-install any skills or rely on attempting to eval max markdown into a context window. There’s no magic trick except application of the craft of software engineering itself! Stop chasing LLM prompt fairies and instead focus on the craft.

*deep breath* people think I'm joking when I tell them that to develop taste for software they need to have brunch with their friends, watch old movies and find old records, walk around metropolitan cities and observe how the building styles lend to the personality of the people around them, but I'm so fkin dead serious. where else is this mythical "taste" going to come from? what are you doing to parse the human condition? mf you can barely decide what discomfort you're subjecting yourself to in finding out what you like/dislike, and I'm supposed to trust you to make decisions for millions of people? go do some pottery and come back to me and describe the joy you felt without faffing about curves or whatever, I need you to feel the clay under your fingernails and fall in love with mud. even steve had the decency to drop acid on a sweaty beach in goa to find himself, the least you can do is listen to your friends talk about their lives over a meal without getting distracted by your phone. *exhale*

Code freeze isn’t really a thing anymore before releases and in the future the code might even be generated online per request according to some constraints.

This is the missing piece that engineers need to develop skills in. For the past few years I have been encouraging engineers to become more “product engineers” or approach work from a founder perspective. This is such a huge unlock for working agent-led.