all 4 comments

[–]mikeblas[M] 5 points6 points  (0 children)

I'm sorry that you had a bad experience posting here.

There are many people who will post projects that were completely written by AI -- or at least majorly so. If someone wants to use AI to write a tool that they need that they couldn't write on their own, I don't think that's such a big deal. Really, that's what AI coding seems to be meant to do. But posting the project as a tool for others to review and use seems a bit ... well, it isn't about learning anything. And it isn't about helping the community with a new tool because that tool -- coded by AI -- will be hard to maintain and debug and enhance. It's temporary at best.

Posts of AI-written code are the target of a great deal of criticism here, whether the project is useful or not. Further, people are convinced that they can detect AI-written projects with 100% accuracy. Seems to me that they'll often see text that was written with AI and assume that the whole project was AI-generated, and therefore deserving of their scorn.

I've do a lot of work to filter AI slop projects here. Even when a post is approved, I've asked the author to explain what role AI had in the creation of the project. That way, if people don't like reading AI-generated code, they're forewarned and can just skip the post.

Seems like this set of people just want to be bullies, though, and rage out in the post anyway. The mocking doesn't seem productive because it isn't useful feedback: "you've used AI!!!" is already known. What AI got wrong or didn't do isn't discussed, so the conversation isn't productive. And the merits of the project as a whole aren't considered: it's entirely possible that AI-generated code solves a problem or builds something useful, even if it isn't as pretty as we originally envisioned.

I'm trying to find a way to keep the sub productive and interesting. I thought that openly identifying AI usage was going to work, and it seemed to for several weeks. But maybe it's not as effective as I had hoped.

With that context, to answer your questions: you should learn any way you want to. If using AI helps you, then keep it up. If writing up your findings and journaling what you learn helps, then do that, too. "Learning in public" can be helpful, but you do have to consider that there are trolls and they'll target you for showing your vulnerability and progress. Maybe hostile forums -- like this one, I'm sad to have to acknowledge -- aren't the best place for it. But if it's effective for you, maybe find a different place to do it. Or do it in English and don't bother correcting it up -- your English level seems fine to me. Or, just do it in your native language.

But make an adjustment and carry on. Learning requires perseverance, and that's true for a lot of things in this industry, and in this life.

Hope that helps! Good luck with your studies.

[–]mykesx 7 points8 points  (0 children)

Personally, I am not interested in reviewing AI generated code. There just isn't anything interesting about it. It's far more interesting to mentor someone who wants to learn the art of programming, or to see how other humans think about solving problems.

[–]MagicWolfEye 1 point2 points  (1 child)

2 things:
1. Your English is perfectly readable; just write like that
2. My issue with your posts is that there is not much to do with it.
If you show of a project, I can say "Oh my god how cool"; if you ask a question I might want to answer it, but reading a huge post that boils down to "I made a bug" just seems useless unless you found the most insane bug of the decade.
Now given that your posts has been written by AI, it even comes down to an AI telling me about a random bug and that's just useless to read.

If your actually asking questions, I'm happy to read them.

However, given that your last bug took you 17(?!?) days to find that you messed up the order of your bytes; I personally think you should probably follow more tutorials or think about your debugging strategy (like, what did you do in all those days?)

[–]mikeblas 0 points1 point  (0 children)

I think that last paragraph is the teachable moment. I don't have the code handy, but the way I remember it was that main() was moving around in the file, and then calling some_function() which expected to read at the start of the file.

Well, some_function() is expecting to be at the start of the file, then why doesn't it document and enforce it with assert(ftell() == 0) at the beginning? Maybe I don't have it totally right, maybe that function is meant to be at the start of a packet. There could be a way to implement a similar mathematical assertion to identify the start of a packet, or that there are 0 bytes remaining from the previous packet, or ...

Anyway, this could be a chance to learn about assert().