The idea is that -someone- reviewed the lines of code they modified, leading to the sum of code being looked at by many human eyes. Using someone else's code has always been a system of trust in this way.
AI/Vibecoding breaks this social trust, hence the general aversion to using those codebases or bringing LLM code in. It's not really about the general quality of the agents. It's about the code no longer being reviewed and understood by a human. How can one place trust in that? Unit tests don't replace careful review and considerate design.
That's MIT. At a state university my friends were making in the ballpark of ~30k.
And yes, that is "next to nothing" compared to the salaries they make now after quitting and just finding work. And their outlooks are in significantly better shape, whereas one friend was highly depressed before.
People can also develop "deep expertise and specialized skills" through their work, and network via conferences, generally paid by their employer. Well, if they can find a job as a junior nowadays.
This really gets on my nerves. ishouldstayaway provided a perfectly valid resource to support the initial statement that gourmand isn't just about quantity anymore.
> Well, you had to go to #2
This is clearly a disparaging remark meant to discredit their comment. So what if it's #2? It's a definition in multiple dictionaries. This usage warranted its own definition.
> in an American English dictionary
Same thing here- italicizing American as if it means anything. Again, both Merriam Webster and the OED carry both definitions.
> It's a usage that has morphed in recent times, sure
"Recent" being 1758. 268 years. Long enough that it doesn't warrant a nit anymore.
> the first 1a primary
Again: the non-quantity usage warranted a dictionary definition.
> Following that Chesterfield example is a 1816 Coleridge extract
Ignoring the 1804 extract before that and the extracts after it.
All in all I find this type of interaction (needing to be "correct" instead of accepting that there are multiple usages) to be extremely distasteful, leaving a sour taste in my mouth.
Because the bugs were caused by programmer error, not anything inherent to rust. It was more notable due to cloudflare being a critical dependency for half the internet, but that particular issue could've happened in any language.
This kind of melodramatic reaction to rust code is fatiguing, honestly. Rust does not bill itself as some programming panacea or as a bug free language, and neither do any of the people I know using it. That's a strawman that just won't go away.
Rust applies constraints regarding memory use and that nearly eliminates a class of bugs, provided safe usage. And that's compelling to enough people that it warrants migration from other languages that don't focus on memory safety. Bugs introduced during a rewrite aren't notable. It happens, they get fixed, life moves on.
This is a bit more than overselling a proof of concept. He made claims that were not correct, and presented some LLM generated code as point of pride. And not on his blog, but a company's website.
He's emblematic of the era we now live in. Vibe coded projects that the "developer" didn't learn anything from, posted using LLMs. People have zero shame, zero curiosity, zero desire in learning and understanding what they're working on.
Also it doesn't make sense to escalate an interaction by swearing at a person and simultaneously asking them to calm down.
There has to be some consideration for cross-language discussion where english is not the native language of the poster. The usage and intent there is completely different than a native speaker lazily having gpt spit out a comment for them.
There's no better time to play fighting games than right now. Street Fighter 6 has one of the best training rooms that I've seen. I also will slow the game down to 50% speed when internalizing a new combo sequence.
There's something zen and theraputive about sitting in the training room, working on the same combo over and over. Really working it into the muscles so that it becomes fluid and effortless in a real match.
I don't think the culture is the same due to cabinets having network capabilities now, but I do think it's possible.
At the taito station in Akihabara, I've met tourists a few times when I was in town for a large tournament (EVO Japan) and made friends from it. I've also had people watching me play, but unfortunately I don't speak Japanese.
I know there's a few arcades that still have some street fighter III: third strike cabinets with regulars. I can't speak for other games but at least for street fighter, people are almost always open and friendly.
- except the cost of materials and gas to drive to the hardware store, which you'll likely do twice or thrice as you realize you bought the wrong thing or need some other specific tool, that you'll use one time a year or less
- except the cost of your own time away from personal projects and family
- except the cost of hiring a plumber afterwards to professionally fix the problem you caused by DIY'ing it without the knowledge and experience that a professional brings
> Nobody has ever walked past a photograph because they can't inspect its digital authenticity hash
That the average person hasn't thought about this doesn't mean it couldn't become a thing in the future. People do value authenticity and genuine things, though I agree the particulars aren't relevant in a lot of cases.
This is a (very expensive!) toy camera, but I could see traditional camera companies like Fujifilm, Canon, etc, incorporating this tech later down the line.
AI/Vibecoding breaks this social trust, hence the general aversion to using those codebases or bringing LLM code in. It's not really about the general quality of the agents. It's about the code no longer being reviewed and understood by a human. How can one place trust in that? Unit tests don't replace careful review and considerate design.