AI generates more code than devs can track in 2026, so will the code review process have to adapt – or is it doomed? A look into this decades-old practice and the approaches that could replace it
These days, my preference is React and TypeScript for frontend development, and Go, TypeScript, then Rust for everything else.
I really like Rust, and I have used it a lot. But when I think about whic
Today, a single prompt turned 46 SWC issues into 45 pull requests.
I do not know exactly how long it took. While the work was running, I was looking at my phone and playing games. By the time I checke
Jq is a great tool. I use it frequently, but this recent article from Sequoia McDowell still has some great tips in it. Well worth a read. One thing that stood out to me from this post was the snippet
Copilot code review can now approve pull requests - GitHub Changelog
Copilot now tells you when a pull request is ready to approve, and admins can authorize it to sign off on approval. The ability for Copilot to approve is off…
Still way beyond cool: resurrecting the Doomguy TDD loop
It was my first few months with Ruby. I was running through everything I could find, still figuring out what made this language different. One day I landed on an old blog post titled “Way beyond cool: autotest + growl + Doomguy”. The date read 2007. The screenshots showed a Doom Marine face — smiling when the tests passed, bleeding more with every failure.
Storybook Workbench: audit vibe-coded UIs and find hidden bugs in hours—Martian Chronicles, Evil Martians’ team blog
Storybook Workbench is a bundle of Agent Skills that turn Storybook into an audit layer for AI-generated UIs: find dead components, design-system drift, and hidden accessibility bugs.