Post

I refuse to call it vibe coding, but I prompted my way to a command line tool, written in C, that converts millimeters to inches and vice versa. A few prompts later, I got something that works, and a man page with usage examples. 🤯 I usually can't find the time to create man pages or remember how.

The ability to generate code like this is impressive, but the ability to interact with the tool to explain things I don't understand is the game changing part to me. Even when using this tool, I'm still learning. I also noticed that I'm not reaching for my web browser to look things up.

A big part of my experience feels like it's based on my existing ability to write and debug code. I know what I'm looking at, and find myself studying the code for style, high level logic, and not fussing around with the syntax. While it works, I'm still finding the urge to make it look good too.

It's almost like I'm writing the application twice. A good first draft, a detailed review, and lots of refactoring until it's just right. But isn't that how I've always done it? Is this a better workflow than the one I had before? Can this do things I can't? Those are the open questions for me.