| ▲ | xmcp123 18 hours ago | |
I’ve reviewed and worked on a lot of vibe coded apps (I’m an engineer, 20 YOE). I can basically split it into 3 groups. 1) Pure vibe code. No software experience. 2) AI with someone who knows the software development process and some things about software, but can’t code. 3) Engineers using AI assistance, reading/reviewing code, forcing structure. If someone can pay to replace #1 with #3 it’s very worth it. The quality between each of these tiers is enormous. I actually got curious and asked AI to look at each module in a codebase, and tell me about who wrote it without looking at git. It successfully profiled all 3 of these groups and correctly attached them to the right module. | ||
| ▲ | zie1ony 7 hours ago | parent [-] | |
Thanks for writing this. In my refactoring process I also start with code profiling. Opus is good, at finding hand written code, which sometimes is a good starting point of understand the codebase in general. | ||