"We built it, it worked sometimes, so we threw it all out" is either the most honest engineering blog post I've read in a while or the plot summary of every project I've ever worked on.
It feels like the teams getting AI workflows right are the ones willing to iterate toward simplicity, figuring out what they're uniquely good at and letting the rest of the ecosystem handle the rest.
That loop of build, learn, simplify is quietly producing better products than "build the whole thing" ever did.
Just wanted to flag the use of the little "jump back to where I was reading" links on the footnotes is a feature I'll be implementing and using on every footnote I ever write for the rest of my life now. Thank you!
"English spelling has a reputation. And it’s not a good one." - never have i ever agreed with anything more
different hill, but one I would die on is: as the letter "c" should make the "ch" sound, the letter "c" serves no purpose not already handled by "s" or "k" otherwise
I totally get this side of things. I see the benefits of Agentic coding for small tasks, minor fixes, or first drafts. That said, I don't understand the pseudo-tribalism around specific interfaces to what amounts to only a few models under the hood and worry about what its doing for (or not doing for) junior devs.
Also, if we could get AI tooling to do the reviews for us reliably, I'd be a much happier developer.