Live data from Hacker News

The cult of vibe coding is dogfooding run amok

bramcohen.com

271–280 of 555 posts

Re: The cult of vibe coding is dogfooding run amok

#271

Earlier quoted context omitted.

TBH Claude Code is surprisingly shit to use given the technical resources and the amount of money behind it. Looking past the bugs and missing features, it's so obvious it's not built by people who care about the product from a developer/craftsman perspective. It's missing all the signs of polish/care, it feels like someone shipped an internal PoC to prod and kept hacking on it. And now they are just tacking on featu…

The most obvious sign to me from the start that somebody wasn't really paying attention to how the Claude app(s) work is that on iOS, you have to leave the app active the entire time a response is streaming or it will error out.

Don't worry, the Gemini website does the same, at least on Firefox mobile. You switch apps and you lose the response AND the prompt.

Normally some software devs should be fired for that.

Re: The cult of vibe coding is dogfooding run amok

#272
post #244

Earlier quoted context omitted.

> it doesn't really matter in the end if you have one of the top models in a disruptive new product category where everyone else is sprinting also, sure..

Code quality never really mattered to users of the software. You can have the most code and still have zero users or have high user frustration from users that you do have. Code quality only matters in maintainability to developers. IMO it's a very subjective metric

It's not subjective at all. It's not art.

Code quality = less bugs long term.

Code quality = faster iteration and easier maintenance.

If things are bad enough it becomes borderline impossible to add features.

Users absolutely care about these things.

Re: The cult of vibe coding is dogfooding run amok

#273
post #49
post #17

Earlier quoted context omitted.

AI is non-deterministic. Can it still be considered an abstraction over a deterministic layer?

The argument against this is that human coders are also non-deterministic, so does it really matter if it's a human or an AI agent producing the code – assuming the AI agent is capable of producing human-quality code or better? I agree it's not a layer of abstraction in the traditional sense though. AI isn't an abstraction of existing code, it's a new way to produce code. It's an "abstraction layer" in the same way a…

Human coders and IDEs are not purported to be abstraction layers.

Re: The cult of vibe coding is dogfooding run amok

#274

It’s so strange. I think there’s a few different groups: - Shills or people with a financial incentive - Software devs that either never really liked the craft to begin with or who have become jaded over time and are kind of sick of it. - New people that are actually experiencing real, maybe over-excitement about being able to build stuff for the first time. Forgetting the first group as that one is obvious. I’ve enc…

Personally I'm getting sick of the slop. If anything that is whats making me care less.

Re: The cult of vibe coding is dogfooding run amok

#275

It’s truly strange that people keep citing the quality of Claude code’s leaked source as if it’s proof vibe coding doesn’t work. If anything, it’s the exact opposite. It shows that you can build a crazy popular & successful product while violating all the traditional rules about “good” code.

Bad code works fine until it doesn't. In my experience, with humans, doing the right thing is worth it over doing the bad thing if your time horizon is a few months. Once you're in years, absolutely do the right thing, you're actually throwing time away if you don't. And I don't mean "big refactor", I mean at-change-time, when you think "this change feels like an icky hack." For LLMs, I don't really know. I only have…

> Bad code works fine until it doesn't.

Who is to judge the "good" or "bad" anyway?

Re: The cult of vibe coding is dogfooding run amok

#276
post #168

Earlier quoted context omitted.

Those high end restaurants are more like art and exploration of food then something practical like code. The only similarity is maybe research in academia. There's not real industry uses of code that's like art.

I used the extreme of the spectrum, I can’t imagine you’re arguing that food is binary good / bad? There’s a litany of food options and quality, matching different business models of convenience and experience. Research in academia seems less appropriate because that’s famously not really a business model, except maybe in the extractive sense

There's no equivalent of experience and art in code. Writing code is not expressing your self, and you don't pay for pushing the limits and experimenting with it. That's what high end restaurants are along with service they provide.

As far as good or bad, how food is made is irreverent to the outcome if it's enjoyable.

Re: The cult of vibe coding is dogfooding run amok

#277

Earlier quoted context omitted.

This is actually a pretty good callout. Observability into how a foundation model generated product arrived to that state is significantly more important than the underlying codebase, as it's the prompt context that is the architecture.

Yeah, I'm just a little tired of seeing these pull requests of multi-thousand-line pull requests where no one has actually looked at the code. The solution people are coming up with now is using AI for code reviews and I have to ask "why involve Git at all then?". If AI is writing the code, testing the code, reviewing the code, and merging the code, then it seems to me that we can just remove these steps and simply P…

> why involve Git at all then?

I made a similar point 3 weeks ago. It wasn't very well received.

https://news.ycombinator.com/item?id=47411693

You don't actually need source control to be able to roll back to any particular version that was in use. A series of tarballs will let you do that.

The entire purpose of source control is to let you reason about change sets to help you make decisions about the direction that development (including bug fixes) will take.

If people are still using git but not really using it, are they doing so simply to take advantage of free resources such as github and test runners, or are they still using it because they don't want to admit to themselves that they've completely lost control?

Re: The cult of vibe coding is dogfooding run amok

#278

Earlier quoted context omitted.

TBH Claude Code is surprisingly shit to use given the technical resources and the amount of money behind it. Looking past the bugs and missing features, it's so obvious it's not built by people who care about the product from a developer/craftsman perspective. It's missing all the signs of polish/care, it feels like someone shipped an internal PoC to prod and kept hacking on it. And now they are just tacking on featu…

The most obvious sign to me from the start that somebody wasn't really paying attention to how the Claude app(s) work is that on iOS, you have to leave the app active the entire time a response is streaming or it will error out.

That has never happened to me. Did you try that a long while ago? I only had that issue with Gemini

Re: The cult of vibe coding is dogfooding run amok

#279

It’s truly strange that people keep citing the quality of Claude code’s leaked source as if it’s proof vibe coding doesn’t work. If anything, it’s the exact opposite. It shows that you can build a crazy popular & successful product while violating all the traditional rules about “good” code.

Code quality is a tactical concern and products live or die on strategy.

I wouldn't recommend neglecting tactics if your strategy doesn't put you on the good side of a generational bubble though.

Re: The cult of vibe coding is dogfooding run amok

#280

Earlier quoted context omitted.

Bad code works fine until it doesn't. In my experience, with humans, doing the right thing is worth it over doing the bad thing if your time horizon is a few months. Once you're in years, absolutely do the right thing, you're actually throwing time away if you don't. And I don't mean "big refactor", I mean at-change-time, when you think "this change feels like an icky hack." For LLMs, I don't really know. I only have…

If you make a working and functional bad code, and put it on maintenance mode, it can keep churning for decades with no major issues. Everything depends on context. Most code written by humans is indeed, garbage.

I define maintenance mode as: given over to different team, so not my problem anymore.
Post reply on HN