When I write code, it achieves two goals:
The obvious goal - the code we get that run and does a thing.
The less obvious goal - my own knowledge of that code, which enables me to debug, improve, and expand it in the future.
👀 The React Compiler in Rust is being rolled out
✅ Oxlint v1.70
✅ SWC v68.1 - Rust crates
✅ Next.js v16.3.0-canary.52 - Soon in v16.4? 👀
✅ Rspack v2 canary - Soon in v2.1? 👀
Did I miss anything else?
🚀 Episode 3 of the Greenfield Games on @codetv.dev comes out tomorrow (3pm PT / 6pm ET)
So far in the series, the autonomous app builder (C.H.A.D.S.) and the human teams are tied 1:1.
Tune in to find out if C.H.A.D.S's app will win, or if one of the human team's will beat it.
Most AI-built apps don't have a test suite. The first honest test is a real user clicking around, and the first you hear about a broken flow is when they tell you. Or worse, when they don't.
Replay QA finds the bugs and hands you the recording of exactly what broke and why.
Most AI-built apps don't have a test suite. The first honest test is a real user clicking around, and the first you hear about a broken flow is when they tell you. Or worse, when they don't.
Replay QA finds the bugs and hands you the recording of exactly what broke and why.
buff.ly/NWo1JBH
Starting in a few minutes... find out of the bot beats the human dev teams (again). C.H.A.D.S. has been waiting for it and has been preparing!
www.youtube.com/watch?v=JP-N...
Live today: buff.ly/NWo1JBH
Maybe this is more obvious to me because I'm also a musician - we play music to give a performance, yes, but we also play it over and over to build our skills.
The performance is not the only goal - your own learning is the deeper goal, and possibly the most valuable outcome.
I've settled on a fairly powerful workflow while working on timber – my new framework.
At some point, I will share my lessons and write about it. But I've found that the more I try to push parallelization, the lazier I am being. One write-heavy work-stream at a time is plenty.