vibe-coding, your thoughts?

Now you're talking. I have created 27 games for myself, and I'm currently discussing another game called Documenting The Odyssey. Some of my previous games are Prehistoric Park, Shaftfall and Sonar Invaders. I'm even making them so that they support my PS4 controller for more functions.

Hi Choom,

You wrote:

They made a generalization, and I decided to demonstrate, in practice, why generalizing is a bad idea.

This is precisely the problem. Based on your statement above, it appears that you knew the context of Maldalain's comment, and you deliberately chose to construct an extreme interpretation of his words to make a point. In doing so, you associated another member of our community with acceptance of child exploitation, a serious and potentially damaging insinuation for which there was no reasonable basis whatsoever. That is unacceptable.

You further wrote:

If they wanted to stay within this context they would have been explicit about that.

A reasonable person, giving Maldalain's statement its plain and ordinary meaning in the context of this discussion, would never interpret it as suggesting acceptance of child exploitation. The context was clear. It is not other members' responsibility to anticipate every extreme interpretation you might choose to construct using their words. You are responsible for what you post.

Finally, you wrote:

Since AI is not a person, the correct word when referring to AI is what, not who, so at least in my interpretation they weren't even referring to AI.

The distinction between "who" and "what" does not change the obvious context or meaning of Maldalain's statement, and it does not justify the insinuation you made.

I expect you to take personal responsibility for your contributions to AppleVis and to engage with other members in good faith. Deliberately distorting another person's position to make a point is not acceptable conduct on AppleVis.

Imagine compairing using AI to child laber, god some of you anti AI people are really something.

I don't cair if somethig was made using AI as long as it works.

There's a problem with your analogy though. The manual juicer and the electric juicer are doing the same thing. It's just that the power source is different.

Now let's assume I tell AI, "draw me a picture of an owl plow, a framework full of birds, heads and feet downward, beaks and claws ready to dig up the soil". It does. Did I learn anything about drawing?

If I drew that, it would be a *very* different process. I'm not saying this means if you use AI to make that drawing your lazy, or you shouldn't do it, or you really don't want to learn, or whatever. I'm just saying, yes in either case I get a drawing in the end, but unlike a manual vs. an electric juicer, we're talking very very different ways of getting there.

Now, it's probably pretty unlikely that I'd be able to draw such a thing. In fact I kind of want to make AI draw it, just to see what happens. But that's because I can't see, so the more complicated the drawing is, the less likely I am to be able to manage it. So this might be a great use of AI for me.

But replace drawing with something you could manage, pottery, making jewelry, programming, sewing, and so on. In all of those cases yes you get a thing at the end, but if you feed measurements and give fabric to a machine that sews clothing, then you don't know how to sew, do you?

Again, maybe you don't care, you just want the end product. That's great. But the difference between any of these and your juicer example is that using a manual vs. electrical machine doesn't do much different, in the case of the juicers. In all of the other cases, you learn a set of skills in one case, and a completely different set of skills, prompting an AI or setting up a machine or whatever, in the other. But if you do the second, you don't learn pottery or drawing or programming or sewing or whatever.

Again, that's fine. Maybe you go, I don't want to make my own clay pots, if I want a pot, I'll go buy one! But learning something like drawing or pottery isn't necessarily about raw utility, it's about learning an art, which is very different from, machine, make me this thing. Please note, I'm not saying it's better, just entirely different things.

If something gets abandoned, it gets abandoned. It won't be the first, nor will it be the last. It has already happened to countless human projects before. Some people who are beta testing also doesn't always understand code, but they can recognize a labeled button from an unlabeled one, and they can certainly report it. They can also recognize links and buttons that doesn't work, and report it to the developer. In the case of vibe coding, the coder is the AI, and it is your job to test, report and suggest until you're either blue in the face, or something comes of it.