• 0 posts
  • 21 comments
Joined 1 year ago
Cake day: August 26th, 2025
  • I think people really need to understand the “it just took a bunch of public work and connected the pieces” isn’t a gotcha for LLMs: it’s one of the sales pitches. The cross-discipline general knowledge combined with the ability to churn huge datasets to find connections across already-known work, and extrapolate to or derive novel findings, is exactly one mode of superhuman success that AI companies have been trying to achieve.

    The bigger issue is that they may be camping human efforts then kill-stealing the last hit on the boss by burning millions of dollars to get a proof a few days/weeks/months earlier than when it would have happened without AI. Basically, waiting for problems to be all-but-formally solved, then beating the researchers to the punch; like the recent Millenium controversy

  • It’s hard to leave when a huge chunk of your interpersonal connections are tangled in its web. It’s the same reason Facebook and Twitter still exist.

    That’s part of the reason why these platforms have such high valuations per capita, opposed to non- or less-social apps. There’s a lot of momentum.

    I host a Matrix server myself and even I still use Discord more because that’s where people are. Matrix has its own issues and, frankly, it’s a shitshow; discord offers a lot of features with better UX and it has a lot of people.

    The only reason Skype and team speak died* was because Discord provided a better value. Now it has the momentum, and the only way it will die is if something else offers even more value. Enshitification helps shift, but the momentum fights against it; momentum is like a small multiplier on top of its feature value.

    Even if the app enshitifies, even if their base value drops; the product is still larger because of the userbase. So it becomes a chicken and egg problem. Until an inflection point is hit, their sheer mass buys them room to enshittify.

    People who can walk away early are the exception, not the rule. It’s why people still use Reddit more than Lemmy. I may get some hate for this, but I don’t think the people on Lemmy are inherently “better.” There are selection biases, and I’m sure that holds true by some metrics, but not in totality.

    “If everyone accelerated at the same time, there wouldn’t be a traffic jam” is true, but that’s not how the world or its people work; you just need to come to terms with that before you can do anything about it.

    Edit: speech to text typos. Probably missed some.

  • A meaningful distinction to me at least is that when I’m vibecoding a one-off personal project I don’t care about, I don’t even look at the code.

    When I’m using LLMs on a serious project that matters, I never blanketly give it a task to write code. Debugging and investigation work is more “go do the thing” vibecody, but when it comes to actually implementing fixes or features: I’d only ever use an LLM when I already know what the code should look like. And most of the time, when I’m writing in a language that I’m not perfectly familiar with, it’s writing as good as me if not better. Its a flat win case. In something like C++, I have a particular style and am very pedantic, and I know the standard very well, and so I tend to need to handhold and fix or rewrite a lot more. The vast majority of programmers who write C++ don’t write like I do, and I’m willing to bet that my “like me or better” statement about languages I’m only intermediate in applies to most casual or junior C++ devs.

    With that said, his diff seems to have a hell of a lot of additions. I’d be willing to bet if he’s using Frontier LLMs that the vast majority of that is testing (and comments if they use claude…)

    I think if someone has a hard no-AI stance, then it’s probably just safe to avoid the project. Whether or not it’s “vibecoding” depends a lot on their workflow and their standards.

    If I need to write 10,000 lines, and I know what it should look like, and the AI produces that: I see no reason why I should waste my time typing it all out by hand. With that said, “Bot, go implement XYZ” isn’t how I or most experienced devs work with AI, and that’s where a lot of problems come from.

    The good news is that it’s mostly a self-solving problem, because those codebases become completely impossible to work in over time.