I've gone back and forth in my usage of LLMs, from full on vibe coding, to plans and execution, to just using the autocomplete in Clion. I've basically stabilized to a few types of usage now for vibe coding, all notably for ideas or disposable code
- prototypes for games, pipe it a love2d template and let it loose. Make sure it wires in a crude imgui style gui so that I can twiddle various numbers.
- wild refactor ideas in a new branch which I never keep. Used for reference basically.
- the main one. Getting it to create disposable tooling. This has been huge for me, and a lot of nice to have tools in the past I can now get an llm to create in a few minutes.
For me vibe coding has been less about copying existing software, and more about gluing together existing tools and programs I want to use into a stack of my own, and helping me to maintain it. The real fun then comes with custom interfaces that are just what I want them to be (often talking directly to the agents is the best of them), and freeform automation of workflows.
Things still break often and require tinkering, but the process itself is fun for me, so I don't mind the blowups.
It's the same reason why people complain about AI slop. Building a software product hasn't been a big problem for a while; there's plenty of funding out there that's ready to be deployed anytime there's a whiff that something can scale.
I've gone back and forth in my usage of LLMs, from full on vibe coding, to plans and execution, to just using the autocomplete in Clion. I've basically stabilized to a few types of usage now for vibe coding, all notably for ideas or disposable code
- prototypes for games, pipe it a love2d template and let it loose. Make sure it wires in a crude imgui style gui so that I can twiddle various numbers.
- wild refactor ideas in a new branch which I never keep. Used for reference basically.
- the main one. Getting it to create disposable tooling. This has been huge for me, and a lot of nice to have tools in the past I can now get an llm to create in a few minutes.
For me vibe coding has been less about copying existing software, and more about gluing together existing tools and programs I want to use into a stack of my own, and helping me to maintain it. The real fun then comes with custom interfaces that are just what I want them to be (often talking directly to the agents is the best of them), and freeform automation of workflows. Things still break often and require tinkering, but the process itself is fun for me, so I don't mind the blowups.
It's the same reason why people complain about AI slop. Building a software product hasn't been a big problem for a while; there's plenty of funding out there that's ready to be deployed anytime there's a whiff that something can scale.