Live data from Hacker News

If you're going to vibe code, why not do it in C?

stephenramsay.net

431–440 of 626 posts

Re: If you're going to vibe code, why not do it in C?

#431
post #317

Earlier quoted context omitted.

You wish, that gray beard sometimes appears in your late thirties.

Maybe. But also what I though was a gray beard in my early 20's is very different from what I think a gray beard is now. The number of those I've considered wizards decreased, and I think this should be true for most people. It's harder to differentiate experts as a novice, but as you get closer the resolution increases.

The more I know, the more I know I don’t know.

Re: If you're going to vibe code, why not do it in C?

#432
>Vibe coding makes me feel dirty in ways that I struggle to articulate precisely. It’s not just that it feels like 'cheating'(though it does). I also think it takes a lot of the fun out of the whole thing.

This exactly. Programming is art, because it comes from the soul. You can tackle a problem a million ways, but there's only one way that YOU would solve it.

Vibe coding feels like people who aren't creative, stealing everyone's creativity, and then morphing it into something they find appealing.

There is no skill.

There is no talent.

You are asking the machine to do ALL THE THINKING. All the little decisions, the quirks, the bugs, the comments to yourself. All the things that make a piece of code unique.

Re: If you're going to vibe code, why not do it in C?

#433

Earlier quoted context omitted.

Maybe. But also what I though was a gray beard in my early 20's is very different from what I think a gray beard is now. The number of those I've considered wizards decreased, and I think this should be true for most people. It's harder to differentiate experts as a novice, but as you get closer the resolution increases.

The more I know, the more I know I don’t know.

...and the more I know you don't know. [On the disappearance of wizards as you age]

Re: If you're going to vibe code, why not do it in C?

#434
If you're going to vibe code, with an intent to review the output so that the ultimate product is actually useful and does what was intended, you should do it in whatever language(s) you're knowledgeable in so you can actually competently review that output.

If you don't give a damn about integrity though, then may as well get funky with it. Hell, go hard: Do it in brainfuck and just let it rip.

Re: If you're going to vibe code, why not do it in C?

#435
post #208

Earlier quoted context omitted.

It's really funny how much better the AI is at writing python and javascript than it is C/C++. For one thing it proves the point that those languages really are just way harder to write. And another thing, it's funny that the AI makes the exact same mistakes a human would in C++. I don't know if it's that the AI was trained on human mistakes, or just that these languages have such strong wells of footguns that even a…

I don't think it has much to do with the languages being harder .. the training sets for JS and Python are probably an order of magnitude larger.

The amount of freely available C code must be very large. Good C code, significantly smaller :-\

Re: If you're going to vibe code, why not do it in C?

#436
> I also think it takes a lot of the fun out of the whole thing.

I used to say that implementation does not matter, tests should be your main focus. Now I treat every bit of code I wrote with my bare hands like a candy, agents have sucked the joy out of building things

Re: If you're going to vibe code, why not do it in C?

#438
> Vibe coding actually works. It creates robust, complex systems that work. You can tell yourself (as I did) that it can’t possibly do that, but you are wrong.

I spend all day in Claude Code, and use Codex as a second-line code reviewer.

They do not create robust systems. They’ve been a huge productivity boost for me in certain areas, but as soon as you stop making sure you understand every line it’s writing, or give it a free reign where you’re not auto-approving everything, the absolute madness sets in.

And then you have to unpick it when it’s trying to read the source of npm because it’s decided that’s where the error in your TypeScript project must lie, and if you weren’t on top of the whole thing from the start, this will be very difficult.

Don’t vibe-code in C unless you are a very strong C developer who can reliably catch subtle bugs in other people’s code. These things have no common sense.

Re: If you're going to vibe code, why not do it in C?

#440

Software development jobs must be very diverse if even this anti-vibe-coding guy thinks AI coding definitely makes developers more productive. In my work, the bigger bottleneck to productivity is that very few people can correctly articulate requirements. I work in backend, API development, which is completely different from fullstack development with backend development. If you ask PMs about backend requirements, th…

This means your difficulty is not programming per se, but that you are working on a very suboptimal industry / company / system. With all due respect, you use programming at work, but true programming is the act of creating a system that you or your team designed and want to make alive. Confusing the reality of writing code for a living in some company with what Programming with capitalized P is, produces a lot of misunderstanding.
Post reply on HN