4 ms·
I don't know why that's funny. This is not a post about a vibe coding session. It's Kenton Varda['s coding session]. later updated to clarify kentonv didn't
by tptacek 1y ago
I don't know why that's funny. This is not a post about a vibe coding session. It's Kenton Varda['s coding session].
later
updated to clarify kentonv didn't write this article
- kevingadd 1y agoI think it makes sense that GP is skeptical of this article considering it contains things like: > this tool is improving itself, learning from every interaction which seem to indicate a fundamental misunderstanding of how modern LLMs work: the 'improving' happens by humans training/refining existing models offline to create new models, and the 'learning' is just filling the context window with more stuff, not enhancement of the actual model or the model 'learning' - it will forget everything if you drop the context and as the context grows it can 'forget' things it previously 'learned'.
- BurritoKing 1y agoWhen you consider the "tool" as more than just the LLM model, but the stuff wrapped around calling that model then I feel like you can make a good argument it's improving when it keeps context in a file on disk and constantly updates and edits that file as you work throguh the project. I do this routinely for large initiatives I'm kicking off through Claude Code - it writes a long detailed plan into a file and as we work through the project I have it constantly updating and rewriting that document to add information we have jointly discovered from each bit of the work. That means every time I come back and fire it back up, it's got more information than when it started, which looks a lot more improvement from my perspective.
- tptacek 1y agoI would love to hear more about this workflow.
- kiitos 1y agoThe sequence of commits talked about by the OP -- i.e. kenton's coding session's commits -- are like one degree removed from 100% pure vibe coding.
- tptacek 1y agoYour claim here being that Kenton Varda isn't reading the code he's generating. Got it. Good note.
- kiitos 1y agoNo, that's not at all my claim, as it's obvious from the commit history that Kenton is reading the code he's generating before committing it.
- kentonv 1y agoWhat do you mean by "one degree removed from 100% pure vibe coding", then? The definition of vibe coding is letting the AI code without review...
- kiitos 1y ago> one degree removed You're letting Claude do your programming for you, and then sweeping up whatever it does afterwards. Bluntly, you're off-loading your cognition to the machine. If that's fine by you then that's fine enough, it just means that the quality of your work becomes a function of your tooling rather than your capabilities.