Live data from Hacker News

After two years of vibecoding, I'm back to writing by hand

atmoio.substack.com

241–250 of 652 posts

Re: After two years of vibecoding, I'm back to writing by hand

#241
post #207
post #16

Earlier quoted context omitted.

> That's your job. Exactly. AI assisted development isn't all or nothing. We as a group and as individuals need to figure out the right blend of AI and human.

I'm only writing 5-10% of my own code at this point. The AI tools are good, it just seems like people that don't like them expect them to be 100% automatic with no hand holding. Like people in here complaining about how poor the tests are... but did they start another agent to review the tests? Did they take that and iterate on the tests with multiple agents? I can attest that the first pass of testing can often be s…

> I can attest that the first pass of testing can often be shit. That's why you iterate.

So far, by the time I’m done iterating, I could have just written it myself. Typing takes like no time at all in aggregate. Especially with AI assisted autocomplete. I spend far more time reading and thinking (which I have to do to write a good spec for the AI anyways).

Re: After two years of vibecoding, I'm back to writing by hand

#242
I don't know whether I would go that extreme, but I also often find myself faster writing code manually; for some tasks though and contextually, AI-assisted coding is pretty useful, but you still must be in the driving seat, at all times.

Good take though.

Re: After two years of vibecoding, I'm back to writing by hand

#243

AI is incredibly dangerous because it can do the simple things very well, which prevents new programmers from learning the simple things ("Oh, I'll just have AI generate it") which then prevents them from learning the middlin' and harder and meta things at a visceral level. I'm a CS teacher, so this is where I see a huge danger right now and I'm explicit with my students about it: you HAVE to write the code. You CAN'…

What you as a teacher teach might have to adapt a bit. Teaching how code works is more important than teaching how to code. Most academic computer scientists aren't necessarily very skilled as programmers in any case. At least, I learned most of that after I stopped being an academic myself (Ph. D. and all). This is OK. Learning to program is more of a side effect of studying computer science than it is a core goal (…

While I may not write assembler, there is still significant value in being able to read assembler e.g. godbolt.

Re: After two years of vibecoding, I'm back to writing by hand

#244

Earlier quoted context omitted.

Just a supplementary fact: I'm in the beneficial position, against the AI, that in a case where it's hard to provide that automatic feedback loop, I can run and test the code at my discretion, whereas the AI model can't. Yet. Most of my criticism is not after running the code, but after _reading_ the code. It wrote code. I read it. And I am not happy with it. No even need to run it, it's shit at glance.

> I can run and test the code at my discretion, whereas the AI model can't. It sounds like you know what the problem with your AI workflow is? Have you tried using an agent? (sorry somewhat snarky but… come on)

Yeah, you're right, and the snark might be warranted. I should consider it the same as my stupid (but cute) robot vacuum cleaner that goes at random directions but gets the job done.

The thing that differentiates LLM's from my stupid but cute vacuum cleaner, is that the (at least OpenAI's) AI model is cocksure and wrong, which is infinitely more infuriating than being a bit clueless and wrong.

Re: After two years of vibecoding, I'm back to writing by hand

#246

Earlier quoted context omitted.

Vibe coding was coined less than a year ago: https://x.com/karpathy/status/1886192184808149383

To a describe a thing people had been doing since LLMs became available.

When LLMs first came out, they weren't very good at it, which makes all the difference. Sometimes the thing that's really good at something gets a different name. Chef vs cook, driver vs chauffeur, painter vs artist, programmer vs software developer, etc.

Re: After two years of vibecoding, I'm back to writing by hand

#247

I feel like I'm taking crazy pills. The article starts with: > you give it a simple task. You’re impressed. So you give it a large task. You’re even more impressed. That has _never_ been the story for me. I've tried, and I've got some good pointers and hints where to go and what to try, a result of LLM's extensive if shallow reading, but in the sense of concrete problem solving or code/script writing, I'm _always_ di…

Well one way of solving this is to keep giving it simple tasks.

Exactly 100%

I read these comments and articles and feel like I am completely disconnected from most people here. Why not use GenAI the way it actually works best: like autocomplete on steroids. You stay the architect, and you have it write code function by function. Don't show up in Claude Code or Codex asking it to "please write me GTA 6 with no mistakes or you go to jail, please."

It feels like a lot of people are using GenAI wrong.

Re: After two years of vibecoding, I'm back to writing by hand

#248
post #21
post #14

Earlier quoted context omitted.

At the earliest, "vibecoding" was only possible with Claude 3.5, released July 2024 ... maaaybe Claude 3, released in March of that year... It's worth mentioning that even today, Copilot is an underwhelming-to-the-point-obstructing kind of product. Microsoft sent salespeople and instructors to my job, all for naught. Copilot is a great example of how product > everything, and if you don't have a good product... well.…

Is Claude through Github Copilot THAT much worse? I know there are differences, but I don't find it to be obstructing my vibe coding.

Yes. Copilot sucks. Copilot is like a barely better intellisense/auto-complete, especially when it came out. It was novel and cool back then but it has been vastly surpassed by other tools.

Re: After two years of vibecoding, I'm back to writing by hand

#249

I feel like I'm taking crazy pills. The article starts with: > you give it a simple task. You’re impressed. So you give it a large task. You’re even more impressed. That has _never_ been the story for me. I've tried, and I've got some good pointers and hints where to go and what to try, a result of LLM's extensive if shallow reading, but in the sense of concrete problem solving or code/script writing, I'm _always_ di…

Just a supplementary fact: I'm in the beneficial position, against the AI, that in a case where it's hard to provide that automatic feedback loop, I can run and test the code at my discretion, whereas the AI model can't. Yet. Most of my criticism is not after running the code, but after _reading_ the code. It wrote code. I read it. And I am not happy with it. No even need to run it, it's shit at glance.

You might get better code out of it if you give the AI some more restrictive handcuffs. Spin up a tester instance and have it tell the developer instance to try again until it's happy with the quality.

Re: After two years of vibecoding, I'm back to writing by hand

#250
post #27

Earlier quoted context omitted.

It’s like weightlifting: sure you can use a forklift to do it, but if the goal is to build up your own strength, using the forklift isn’t going to get you there. This is the ultimate problem with AI in academia. We all inherently know that “no pain no gain” is true for physical tasks, but the same is true for learning. Struggling through the new concepts is essentially the point of it, not just the end result. Of cou…

I do appreciate the visual of driving a forklift into the gym. The activity would train something , but it sure wouldn't be your ability to lift.

A version of this does happen with regard to fitness.

There are enthusiasts who will spend an absolute fortune to get a bike that is few grams lighter and then use it to ride up hills for the exercise.

Presumably a much cheaper bike would mean you could use a smaller hill for the same effect.

Post reply on HN