I feel so vindicated when the AI struggles just as much as I did. Just got DeepSeek to think for almost 5 minutes and then spit out a totally incorrect solution that I had also tried

Jevon's paradox modified: As the price of a good goes down, people will start using it for stupider and stupider stuff

If the rate of Grok expansion keeps up it's current rate, every button on X will be replaced with Grok by this time next year

I have an irrational hatred of this API This reads like "next_interval, with a maximum of 1", but it's actually "next_interval, with a minimum of 1" It breaks my brain still after years of full-time Rust

I lost my 50-day Chessbook streak :/ But is anything truly lost when you have production database access

React vs SolidJS, in a nutshell

You know what else makes a nice timeline of the work you did? And lets you easily revert stuff if shit hits the fan? Git. Plain old git. Nothing here is specific to PRs, commits share all these properties

Props to the App Store reviewer grinding straight through the Super Bowl halftime show 👏🏻

Couldn't get stockfish w/ neural net to work well on Chessbook web. Turns out, I was fetching HTML instead of the neural net weights. Unsurprisingly, Stockfish does not perform well with neural network weights converted from HTML 🤦‍♂️

Anthropic really cooked with the Claude Code thing, really impressive performance and a great TUI. Have been refactoring code all day with it

Claude Code woke up and chose violence

Love getting feedback like this!

Chessbook outranks Chessable on the App Store for "Chess openings" 🎉

It drives me nuts to see the "devs should unionize/devs should have a formal accreditation process" conversation spring up like clockwork on Hacker News You want the tech industry, with its famously high salaries, cushy jobs, generous severance, and job mobility – where you can

So cool to see stuff like this. We’ve finally reached the point where when people ask “how do I learn openings?”, the most popular answer I see is Chessbook

I’m convinced the gap in experience between a native mobile app and a mobile web app boils down primarily to user input at this point. The performance gap is illusory for most use-cases & devices. Safari iOS handling of how a keyboard displays, the havoc it wreaks on the page,

Bro, your site isn't slow, you just forgot to properly implement streaming RSC with PPR and ISR for dynamic segments, falling back to SSR only when necessary, obviously using SSG for the static shell with proper caching and prefetching on visible elements. Also don’t forget to

The dream of React Native for iOS devs: never touch Xcode again, no need to clean the build artifacts and restart your computer every time the day of the month is a prime number The reality: same mysterious errors, but JavaScript

Expedition 33 is a masterpiece and anyone that enjoys games should play it. I can’t believe what this small studio has pulled off. Actually may be the best game I’ve ever played, and I’ve played a lot of games.