Not-really Vibe-Coding

This weekend, I spent some more time on the swim scheduler using Claude. This wasn’t really vibe-coding as much as working with Claude to fix issues I identified and minimize the changes so that the patches weren’t replacing entire chunks of code–is this how working with AI is eventually supposed to be? It’s more like being a busy senior engineer providing the overall design and Claude is doing the work of the junior engineer and bringing it to me. Together, we got a version that meets the initial requirements, runs on Windows, Linux, and Mac, and is built through github.

It was a handy experience, because I got a little more hands-on with Rust, used ChatGPT and Claude to help me understand some of the complexities of Rust, and built what I think is the first actual GUI application I’ve built since I was in middle school (if I mentioned the language I will show my age). There are a lot of things I need to improve on this little project. For one, I’m not sure main.rs should be where everything is, but I’ll get there. I think this is the first thing I’ve worked with using AI that actually turned out. It may be that this is a highly specific use case with easy to test components that I can easily break down into pieces and also had an initial prototype…

Also, there are no real repercussions if it turns out the implication has significant algorithmic bugs…

Tags:

Comments are closed