# Vibe coding leaves me with a very sour taste

**URL:** <https://forum.devtalk.com/t/vibe-coding-leaves-me-with-a-very-sour-taste/211157>\
**Category:** Blogs/Articles/Talks/Podcasts\
**Tags:** rust, vibecoding, blog-post\
**Created:** [16 August 2025 22:55 UTC](https://forum.devtalk.com/t/vibe-coding-leaves-me-with-a-very-sour-taste/211157 "2025-08-16T22:55:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![waseigo](https://forum.devtalk.com/user_avatar/forum.devtalk.com/waseigo/32/7258_2.png) [@waseigo](https://forum.devtalk.com/u/waseigo)\
**Post date:** [16 August 2025 22:55 UTC](https://forum.devtalk.com/t/vibe-coding-leaves-me-with-a-very-sour-taste/211157/1 "2025-08-16T22:55:35Z")

</div>

> **[Vibe coding leaves me with a very sour taste](https://overbring.com/blog/2025-08-16-vibe-coding-sour-taste/)**
>
> An engineer's adventures in business, product development, Elixir, and writing books

**Top-tier LLMs, Rust and Erlang NIFs; nifty, and night and day vs. C, but let me tell you about vibe coding…**

After I submitted my [blog post](https://overbring.com/blog/2025-08-13-writing-an-elixir-nif-with-genai) to [Hacker News](https://news.ycombinator.com/item?id=44914040) on using Grok 3 to generate C for an Erlang NIF with the help of code reviews by GPT-5 and Gemini 2.5 Flash, I received some interesting comments. Let’s review them before we dive deep into why vibe coding leaves me with a very sour taste, and why I will never engage in vibe coding again, if I can avoid it.

---

<div class="post-metadata">

**Author:** ![adamaiken89](https://forum.devtalk.com/user_avatar/forum.devtalk.com/adamaiken89/32/2661_2.png) [@adamaiken89](https://forum.devtalk.com/u/adamaiken89)\
**Post date:** [18 August 2025 12:04 UTC](https://forum.devtalk.com/t/vibe-coding-leaves-me-with-a-very-sour-taste/211157/2 "2025-08-18T12:04:28Z")

</div>

This is a nice promise. However, it is still in a very early stage to say whether it would guarantee a reliable and maintainable way for software lifecycle.  
Btw, I would say it can speed up a lot of typings and you no longer need to be a super fast typers.

---

<div class="post-metadata">

**Author:** ![waseigo](https://forum.devtalk.com/user_avatar/forum.devtalk.com/waseigo/32/7258_2.png) [@waseigo](https://forum.devtalk.com/u/waseigo)\
**Post date:** [18 August 2025 12:19 UTC](https://forum.devtalk.com/t/vibe-coding-leaves-me-with-a-very-sour-taste/211157/3 "2025-08-18T12:19:25Z")

</div>

I agree, hence the second part of the blog post. Still, the top-tier LLMs did a _far_ better job at generating Rust code compared to C code.

As for typing speed, I never found this to be the limiting factor. Thinking, reasoning, understanding, problem-solving; those are the actual bottlenecks.

---

<div class="post-metadata">

**Author:** ![ragamuf](https://forum.devtalk.com/user_avatar/forum.devtalk.com/ragamuf/32/4362_2.png) [@ragamuf](https://forum.devtalk.com/u/ragamuf)\
**Post date:** [25 August 2025 23:17 UTC](https://forum.devtalk.com/t/vibe-coding-leaves-me-with-a-very-sour-taste/211157/4 "2025-08-25T23:17:43Z")

</div>

Wow. A very nice read. Trying it all back to CFD, Fortran, and my engineering days. Much appreciated.