Maybe read the original blog post from the gnome dev then? The post the article references… it says right there why the ai code is a problem, it has to much unnessecery code in it and reviewing that takes time. The author also says the submitted ai code doesnt adhere to good practices.

Have you read the first paragraph if the lidnked articel? It quotes the criteria right there: "Extensions must not be AI-generated

While it is not prohibited to use AI as a learning aid or a development tool (i.e. code completions), extension developers should be able to justify and explain the code they submit, within reason.

Submissions with large amounts of unnecessary code, inconsistent code style, imaginary API usage, comments serving as LLM prompts, or other indications of AI-generated output will be rejected."

Maybe instead of commenting under every comment that lines this change read the articlw first? Ai is fine if your code is fine and you uderstand it. If the reviewer has to argue with a llm because the submitter just pasts the text into his llm and then posts the output of said llm back to the reviwer it is a huge waste of time. Thiss doesnt happen if the person submitting the code understands it and made shure that the code is fine.

I mean as a electrical engineering student who likes to program, building such a system seems like fun but playing with it not so much. If there was a game that was purly made for cheaters with the goal of beating the anticheat without detection i would love to try that. I feel like this could be something like the capture the flag competitions some groups make where you have to hack a website faster than others or break some encryption.

Desstroying other players without effirt is like playing a game in easy mode and i dont get that at all, where is the fun if there is no challenge?

The last person that startet in our department and decided to go while they still can said “you can only stack shit that high…” and i think its beatifull… imagine a codebast that startet in assembly bad c code with lots of hardware specific shit and the demand to always ship features to old systems build byy electrical engineers who didnt know better.

I hope in like 10 years i will understand how all of the stacked shit works…

I use isopropanol regularly for cleaning flux off boards after soldering, it is fine and with 5v you wont fry it if it is still a little wet. Just clean it off good then let it dry and if you have concerns wait a little longer. You should be able to feel if there is stuff left in the keys.

I work in a company that has a old codebse in c with tons of realtime intime stuff that is acessed via a shared memory from the realtime to the non realtime system. Tons of strucs get copied around then typecast to other structs and global variables all over the place. You never know where a variable is written to and where it is also acessed from or if it is just a copy. No assembly but still super obscure.

With embedded stuff its still done like that. And if you go from the arduino functionss to writing the registers directly its a hell of a lot faster.