here's where I'm at with vibe coding -
when I'm going from 0 to 1 on a new idea, 100% of the code is generated. I don't eve bother looking at it.
I spend most of that time up front writing a spec with ai. half of that is defining the MVP scope, the other half is carefully specify the layers and interfaces of how I want the program structured. I provide specific idioms and coding standards.
the result is generally a working advanced prototype, but the code is actually maintainable.
the focus on interfaces and components up front is the same approach I've used building production software in the industry. if the interfaces are correct it doesn't matter as much if the implementation is subpar - we can refactor it later.
@note1x8g80...
when I'm going from 0 to 1 on a new idea, 100% of the code is generated. I don't eve bother looking at it.
I spend most of that time up front writing a spec with ai. half of that is defining the MVP scope, the other half is carefully specify the layers and interfaces of how I want the program structured. I provide specific idioms and coding standards.
the result is generally a working advanced prototype, but the code is actually maintainable.
the focus on interfaces and components up front is the same approach I've used building production software in the industry. if the interfaces are correct it doesn't matter as much if the implementation is subpar - we can refactor it later.
@note1x8g80...