Seven new models launching at Build: let’s go!
Reasoning. Code. Image. Transcribe. Voice.
Built from scratch on a clean data lineage, designed for efficiency, working seamlessly as a family of models
Thread 🧵
#MSBuild
Pressure to have faster output by burning tokens but not allowed to burn infinite tokens and then looking at the output and hating it and realizing you could have done a better job with zero tokens but now the tokens are spent and time has passed is kinda killing me rn
To simplify our Codex compute fleet management, we will be sunsetting GPT-5.2 and GPT-5.3-Codex in Codex on June 2nd when logged in with your ChatGPT account.
For free plans, GPT-5.5 will be the default frontier model to build and work with going forward.
These models will remain available on our API.
We've modernized #nock! 🎉 Nock 15 (beta) is now written in TypeScript with auto-generated type declarations and ships as a pure ES module. Cleaner APIs, better DX, and first-class type safety out of the box. Test it if you can! pnpm i nock@beta
"Hard truths about AI-assisted coding"
While AI-Assisted coding can get you 70% of the way there (great for prototypes or MVPs), the final 30% requires significant human intervention for quality and maintainability.
No law says that a team must immediately start on the next story after finishing the previous one. In fact, it's essential to have planned slack time in your schedule to get a smooth product-development flow. Depending on variability (e.g., how many emergencies pop up or surprises you find as you make changes), you'll need between 30% and 50% slack. The more variability, the more slack you need. Fill that time with things like learning and personal projects. Break out of the badly-done-Sprint death march.
@RyanCarniato I tend to optimize for humans first, then for performance, if necessary. I value readability very highly. If you can’t understand your code, then it’s difficult to refactor or introduce new changes and easier to introduce bugs. Only optimize when necessary.
Tanner may be the most cracked/underrated frontend engineer alive. The most refreshing React talk I’ve seen all year*. Tanstack Start is a funny name though I guess I take a bit of the blame, but hits 99% of what I feel has been missing from the React metaframework landscape for YEARS.
*though nextjs conf is next week
@jarredsumner any new thoughts about this issue https://t.co/2Ob1OMkfDw ? Yes, works as designed, but def holding people back from adopting. Can’t even use bun test because of this, where ts-jest or @swc/jest just work…