TNT Ep 08! "Nobody's Going to Write the Next React." @badlogicgames admits he's never done code review, @mitsuhiko has an 11-yr-old submitting PRs, @dillon_mulroy learns by taking down prod, @RhysSullivan says "slop harder," and @threepointone is on vacation. LGTM!
TNT Ep 07! "Code Mode Inside Code Mode." @mattzcarey joins to talk Code Mode, the dead internet of Facebook Marketplace, Claude game-modding, the AI agent moment for normies (?), and @RhysSullivan continues to make "Slop Superhighway" happen. /cc @threepointone@dillon_mulroy
TNT Ep 06! "The Senior Engineer Death Spiral." Rhys and Sunil join the Jevolution, Sunil's blog annoyed Hacker News, Rhys recaps YC, and Rhys shows his latest dual-repo workflow.
Cloudflare's AI gateway is underrated.
AI gateway is good for individuals because you get a single API interface and a single bill for *all* models. You can be promiscuous in switching from GPT to Claude to Grok to Gemini, plus all the generative multimedia models, and the open-weight models too, like Kimi and GLM. Switching is easy, so comparing model performance and capabilities is easy. You change one line of code to switch models, and you don't have to sign up for any of the providers or manage API keys.
AI gateway is good for enterprises, because you can govern which models your team has access to, set spend limits, track individual usage, etc. Give your teammates AI superpowers without letting all hell break loose. We use it internally at Cloudflare to safely manage AI access for ~5000 employees.
AI gateway is good for everyone, because you get better observability, better security, better logging, and unified billing for all your AI usage. And the product keeps improving, with more new hotness coming very soon...
To catch up on this stuff, tune into the latest episode of @NextTokenShow with special guest @michellechen, who runs Cloudflare's AI platform. 🍿
youtube.com/watch?v=gPBw5Cr9…
Bonus! 30 extra minutes we trimmed from Ep 05 about using SlopCodeBench in hiring, @michellechen shouts out @gpusteve, @dillon_mulroy reads the code/argues on the internet, etc.
This is what happens when you listen to our podcast: You write a rad article that about the loss of collaboration in software engineering. Thank you @J_Kreutzbender & keep writing!
Oops took awhile to get this finished, life has been busy lately but finally got it written. What started out as listening to a @NextTokenShow episode really got me thinking about how much time we don't spend with our coworkers anymore
jeremykreutzbender.com/blog/…