A few thoughts about “Vibe coding”
- maxwellapex
- Aug 18
- 1 min read

Yes, I am pretty sure that every one has heard about this term. Vibe coding means coding with the vibe, and it describes a style of working. While it is a great tool especially for tiny tasks, often 100 times faster than human, sometimes we need to be careful of its backfire.
Personally, I use Kiro, Cursor and Claude Code, but all of them have their limit. For example, it is hard to describe details of the coding block, and usually you received the worse coding quality after excessively running debugging codes. My advice is to simply “delete” what it made and ask it to do again, rather than creating debugging loop. You don’t want to make a malfunction debugging code, before you generate another debugger-debugger. Well, I even met some people disable their vibe coding function and use Tab buttons.
There are still a lot to discuss. I believe these can be a series and let’s see if I have another chance to write more. Please leave a comment if you also have thoughts of this.



Comments