281–290 of 382 posts
I vibe coded a retro emulator and assembler with tests. Prompts were minimal and I got really great results (Gemini 3). I tried vibe coding the tricky proprietary part of an app I worked on a few years ago; highly technical domain (yes vague don’t care to dox myself). Lots of prompting and didn’t get close. There are literally thousands of retro emulators on github. What I was trying to do had zero examples on GitHub…
Earlier quoted context omitted.
1. Equality under the law is important in its own right. Even if a law is wrong, it isn’t right to allow particular corporations to flaunt it in a way that individuals would go to prison for. 2. GPL does not allow you to take the code, compress it in your latent space, and then sell that to consumers without open sourcing your code.
> 2. GPL does not allow you to take the code, compress it in your latent space, and then sell that to consumers without open sourcing your code. If AI training is found to be fair use, then that fact supercedes any license language.
However if I memorise that code and write it down that's not fair use. If I copy the encyclopedia that's bad.
The problem then comes into "how trivial can a line be before it's copyrighted"
def main():
print("This is copyrighted")
main()
This article has some serious usage of either bad prompting, or terrible models, or they’re referencing the past with their stories. I have experience AI’s deleting things they shouldn’t but not since like, the gpt4 days. But that put aside, I don’t agree with the premise. It doesn’t make the hard parts harder, if you ACTUALLY spend half the time you’d have ORIGINALLY spent on the hard problem carefully building cont…
I think AI is just a massive force multiplier. If your codebase has bad foundation and going in the wrong direction with lots of hacks, it will just write code which mirrors the existing style... And you get exactly was OP is suggesting. If however, your code foundations are good and highly consistent and never allow hacks, then the AI will maintain that clean style and it becomes shockingly good; in this case, the p…
Meta-circularity is the real test.
After all, I can make new humans :)
Earlier quoted context omitted.
> Even if a law is wrong, it isn’t right to allow particular corporations to flaunt it in a way that individuals would go to prison for. No one goes to prison for this. They might get sued, but even that is doubtful.
Aaron Swartz would probably disagree. https://en.wikipedia.org/wiki/Aaron_Swartz
Earlier quoted context omitted.
I've seen many discussions stating patent hoarding has gone too far, and also that copyright for companies have gone way too far (even so much that Amazon can remove items from your purchase library if they lose their license to it). Then AI begins to offer a method around this over litigious system, and this becomes a core anti-AI argument. I do think it's silly to think public code (as in, code published to the pub…
> I've seen many discussions stating patent hoarding has gone too far... Vibe coding does not solve this problem. If anything, it makes it worse, since you no longer have any idea if an implementation might read on someone else's patent, since you did not write it. If your agent could go read all of the patents and then avoid them in its implementations and/or tell you where you might be infringing them ( without hal…
Earlier quoted context omitted.
> I view LLMs akin to a dictionary …If every time you looked at the dictionary it gave you a slightly different definition, and sometimes it gave you the wrong definition!
Go look up the same word across various dictionaries - they do not have a 1:1 copy of the descriptions of terms. Reproducibility is a separate issue.
Differences between dictionaries are decided by the authors and publishers of the dictionaries without taking individual user queries into account.
I vibe coded a retro emulator and assembler with tests. Prompts were minimal and I got really great results (Gemini 3). I tried vibe coding the tricky proprietary part of an app I worked on a few years ago; highly technical domain (yes vague don’t care to dox myself). Lots of prompting and didn’t get close. There are literally thousands of retro emulators on github. What I was trying to do had zero examples on GitHub…
I call these "embarrassingly solved problems". There are plenty of examples of emulators on GitHub, therefore emulators exist in the latent spaces of LLMs. You can have them spit one out whenever you want. It's embarrassingly solved. There are no examples of what you tried to do.
When LLMs first appeared this was what I thought they were going to be useful for. We have open source software that's given away freely with no strings attached, but actually discovering and using it is hard. LLMs can help with that and I think that's pretty great. Leftpad wouldn't exist in an LLM world. (Or at least problems more complicated than leftpad, but still simple enough that an LLM could help wouldn't.)
Earlier quoted context omitted.
> It's so intriguing, I wonder if the people who are against it haven't even used it properly. I feel like this is a common refrain that sets an impossible bar for detractors to clear. You can simply hand wave away any critique with “you’re just not using it right.” If countless people are “using it wrong” then maybe there’s something wrong with the tool.
Illogical. I had Claude read a 2k LOC module on my codebase for a bug that was annoying me for a while. It found it in seconds, a one line fix. I had forgotten to account for translation in one single line. That's objectively valuable. People who argue it has no value or that it only helps normies who can't code or that sooner or later it will backfire are burying their heads in the sand.
Dismissive. Also kind of rude.
> People who argue it has no value or that it only helps normies who can't code or that sooner or later it will backfire are burying their heads in the sand.
I don’t think this describes most people and it’s certainly not what I think.