My Thoughts on Vibe Coding and Gemini CLI

title: [Vibe Coding][Gemini CLI] Some Thoughts on Vibe Coding
published: false
date: 2025-07-30 00:00:00 UTC
tags: 
canonical_url: https://www.evanlin.com/til-about-vibe-coding/
---

![image-20250731145350802](https://www.evanlin.com/images/image-20250731145350802.png)

### »»» Imagination is Important «««

Just like "Übel" from *Frieren: Beyond Journey's End*, "imagination" is actually very crucial in product development. This is somewhat like "Butcher Ding's Ox," where you need to anticipate how to break down the problem and complete it efficiently. Vibe Coding is such a "completed" tool. (This analogy is a bit old-school XD)

For example (I'll probably write an article about this in the next few days), if you want to use an army of Agents to assist in product development:

- You can't just have a one-sentence requirement.
- You must describe in detail the functionality you want to achieve (similar to a PRD).
- It's best to supplement with relevant background knowledge, such as Github App or Github Webhook, which can save hundreds of dollars in discussion fees.

![image-20250731145521001](https://www.evanlin.com/images/image-20250731145521001.png)

### Personal Thoughts on Vibe Coding:

- A good development process and deployment method can allow Vibe Coding to achieve greater benefits. This is also the most obvious difference between senior engineers and those who understand system architecture.
- Don't fully trust AI; you still need to play the role of a quality gatekeeper (whether you're the boss or the client).
- Senior engineers are usually optimistic about Vibe Coding because they know how to check and even correct the AI's development methods.

My current habit is to let Vibe Coding run in YOLO mode once before a meeting, and then check what it has done. Actually, it's really enjoyable to use for developing side-projects!