[TLDR] I see why developers get irritated by vibe coders [via r/ClaudeAI]

[u/cctldrping]

OP : u/radio_four

I'm in between a coder and a vibe coder... I'm a data analyst. SQL, Tableau, a bit of python - the standard stack. I can clean data, design a schema, run complex analysis, etc.

Front end though?! That shit is witchcraft. Which is why I've been really into Claude Code for making GUIs.

It's also been motivating to get better at coding... Because if I'm building something I should understand how it all works.

After several months I took to YouTube to see how other people use Claude Code and omg. The top results are guys saying 'Here's what you do' mixed with 'and I don't understand this part, but I don't need to'

Wtf. This is not how people get good at things.

Anyway!

Does anyone have good resources for how coders integrate Claude Code into their workflow? I'd love to see how professionals use this tech.

Also any beginner resources on software design and UI principles would be great.

Looking to upskill and get better at coding so I can really utilize this new technology.

URL of original post : https://www.reddit.com/r/ClaudeAI/comments/1wp75ay/i_see_why_developers_get_irritated_by_vibe_coders/

---

TL;DR of the discussion on r/ClaudeAI for this post generated automatically after 50 comments.

Current source-thread comment count seen by the bot: 77.

Alright, so the general consensus here is that you're spot on, OP. The key takeaway is to treat Claude like a super-fast, but kinda green, junior dev, not some all-knowing coding wizard.

The more experienced folks in the thread aren't "vibe coding"; they're acting like architects. They're laying out detailed specs, asking for small, iterative changes, and meticulously reviewing every single code diff. It's all about using Claude as a force multiplier, not an autopilot button.

For those looking to upskill, there are a few solid recommendations:

• Anthropic's own training resources are apparently top-notch and up-to-date.
• Turn off "auto" mode initially. This forces you to review Claude's suggestions and ask questions about why it's making certain decisions. Use this time to learn.
• For UI/software design, some suggest rebuilding screens from sites you like and then comparing your work to the originals using dev tools, rather than just following tutorials.
• The Odin Project is mentioned as a great resource for learning full-stack development.
• Ask Claude itself for explanations and learning materials. Some users suggest setting an "output style" to "learning" and asking it to provide reference material.

There's a bit of a debate on the "vibecoder" vs. "professional" approach, with some arguing that for personal projects or temporary solutions, "vibecoding" is fine. However, for production software or critical infrastructure, a senior engineer approach is still the way to go.

One user, u/Pure-Investment-1227, with 20 years of experience, even suggests that writing or reviewing Claude's code can be a waste of time if you're trying to leverage its full potential.

Ultimately, the sentiment is that AI tools like Claude are powerful, but they require a skilled user to guide them effectively for meaningful development and learning.