No. He used to be good with ideas. Now he's drinking too much of his own poison. His blog posts are bloviated monstrosities incapable of coherently describing the very trivial ideas contained in them.
> His blog posts are bloviated monstrosities incapable of coherently describing the very trivial ideas contained in them. That's not true. He coherently and clearly described this crypto pump and dump nonsense he was pushing for a while https://steve-yegge.medium.com/bags-and-the-creator-economy-...
There are some good ideas in the tools. I hope our culture has room left for curiosity and exploration in that way. I also highly doubt these will catch on over one-shotting and Jira though. Here’s one quick thought from each: Beads keeps the issue tracker state in git. This can only work if you don’t have a PR/Review-Gate to submitting patches (to file bugs/issues/etc) but I’ve found it unexpectedly helpful for pers…
> Beads keeps the issue tracker state in git. Wow that's so innovative. I'm amazed Linus didn't think of that twenty years ago when he invented git. Oh wait... It's been tried and discarded half a dozen times since then. Git is literally just a bunch of text files with a tree pointer. You can fit any data into it you want, but as it turns out, most people who report bugs don't want to use git to do so. > Gastown uses…
We’re all at different points along this path. Today, I was one of the lucky 10000. I hope you get to be in that group again in the future too.
You can't trust it 100%. Sometimes it will just refuse to fix a compiler or lint warning (often saying "This was a pre-existing issue...") or write a trivial test that does nothing and always passes.
> writes code with a lot of warnings > compacts > "This was a pre-existing issue..." I still take this over writing code myself though.
I'm not saying you shouldn't. I'd say 70% of my work code is written by Claude Code or Codex. But this is something you should be aware of when interacting with agents.