Vibe Coding vs Assisted Coding: The Comparison

Everybody knows developers are losing jobs because of the AIs made by AI developers. This is real, and the remaining developers need to change work procedure to either:

• Assisted coding -- Should be fine for now
• Or vibe coding -- Makes production fast but a bit messed, see issue below.

Here's some tested assisted coding and vibe coding tools:

• Assisted Coding: Google Code Assist (GCA)
• Agent mode: May be disaster, multiple files are changed not the way developer actually wants
• No agent: This is good, let GCA suggest, insert code, review and edit; quality is ensured!
• Vibe coding: Claude Artifacts
• Agent mode: Of course always in agent mode 'cause it's vibe coding, you chat only.
• AI creates app very quick, very fast, much much faster than a dev types
• Issue: When you tell it to change some feature, it may spoil another feature.

Vide coding issue example:

When Claude Artifacts was told to move the Equal button to corner, it spoiled the alignment of the blue buttons.

The issue above can be fixed by chatting again and again, but it takes time. However, at this speed of generating code, and the functional features, it's already quite good. I guess next year, or in next few years, vibe coding will be real in production.

Developer alert when changing to vibe coding: Need to learn to design and supervise instead of typing, of course that coding skill must be there or not possible to supervise.