The problem I have with this post is that it equates vibe coding with stupidity. You don't have to be stupid to be a vibe coder, and you can actually do things smarter than a traditional coder ... if you take the time to learn how to do it. His mistake wasn't being a vibe coder. His mistake was in not learning the proper way to connect it via API and failing to use tools to check the security.
Readit Newsomgwalt commented on Vibe code is legacy code blog.val.town/vibe-code... · Posted by u/simonw
Deleted Comment
First, I get it.
Second, you can look at it differently.
AI is going to do most of the coding in a very short time. That's a fact. The opportunities are going to come to those who know how to prompt the AI and hold it accountable.
So yes, you're no longer going to be the hero for the code you type out.
But you CAN be the hero for being the Senior Developer or Project Manager who know what needs to be done and knows how to get the AI to do it right the first time.
I actually got out of coding a number of years ago because I was tired of keeping up with the latest changes in languages, standards, best practices, etc.
When AI became a thing over the past couple of years, I decided to try again ... and I'm actually enjoying it a whole lot more. I make a lot more progress a lot faster, which means I get to see faster results.
You can't control the direction that coding is going. It will go where it goes. But you can control how you think and feel about it. So what choice will you make?
omgwalt commented on I've been using Claude Code for a couple of days twitter.com/Steve_Yegge/s... · Posted by u/tosh
I've been using Claude for about 3 months now. What I've learned is that you have to learn how Claude "thinks" about your project, meaning what kinds of mistakes he makes. They're pretty consistent. As you uncover each new kind, compile a list of things to remind him of each time. For my own project, some of my reminder items to give him each chat (sometimes multiple times in the chat) include: "maintain a single source of truth", "avoid duplication", "stick to our established architecture instead of building new architecture". I always make sure he has an up-to-date file tree to look at. I remind him to ask me if there's a particular file he needs to see for reference instead of making up something new. I also say to make the changes specific to just what needs to be changed, rather than building in stuff and "anticipating" problems that aren't even here yet. Stuff like that. By the way, Project Knowledge is a very useful feature. Just don't expect Claude to ever look at it after your first statement/question. That's when he looks at what's there.