Context is the issue. I have not seed a model that can actually handle the complexity of large code bases.

Reply to this note

Please Login to reply.

Discussion

I guess it depends on what we mean by vibe coding. Example: if you have written out an ideomatic and properly typed service and with a repository (eg. Userservice.ts, publish.user.ts, fetch.user.ts) you can almost one-shot vibe the rest horizontally.

If you have vibed this layer contextless and you can't read what's in there the ints garbage in, garbage out situation and you'll be facing pain.

Experienced vibe coders with understanding of software engineering maybe aren't really vibe coding. They supervise and are therefore doing "supervibed coding".

But in this case you are taking care of the modularisation, no?

I agree, given an interface and some information AI can write an implementation quite well.

Yes, therefore I'm not sure if this is vibe coding in the classical sense.