A senior developer's well-informed take on vibe coding, explaining many weaknesses and problems that come with AI coding assistants.

https://youtu.be/1A6uPztchXk

nostr:npub1p2ehwtdsz3axv7sppsg0zl02zawwfp9pvpgvk8psldrzcx8fkk7s5uwwhy

Reply to this note

Please Login to reply.

Discussion

Hahaha great rage bait - he’s absolutely correct too though on many points. However, I think there’s a real difference between vibe-coding done as a developer vs our expectation of what can be done with it by someone new. Just as they teach design recipes in school for object-oriented, events-oriented, synchronous and asynchronous approaches, vibe-coding is a skill that requires systems thinking along with instructions, pipelines, cross-references, and testing. Still believe it’s the fastest way to learn while building AND definitely worth having an expert around!

I don't know how complex the projects are that you build. But if I don't start modularizing soon, then debugging sessions will keep getting longer or new features will affect old ones. Maintainability goes downhill even for the AI agent.

Definitely something to keep track of! I expect to actually break it up into different git repos, I think you hinted at this before

Heard of this method before. So you can build dependencies with npm, right?

that’s the idea and I’ve never built an npm package before

Your AI know how to 😄