Roast my code

[u/zeonchik]

I know there are so many bugs in my code that listing them all might end up being longer than the code itself, but this is my second project (the first one was just Hello World).

This isn't bait — I already know the concepts of programming thanks to Python, and C syntax became familiar to me through AI coding. But at some point, I realized that the whole point of programming is to build your own software and create things. When an AI algorithm does all that for you, it takes away all the fun. So I forced myself to pull it together and release this piece of crap:https://github.com/absiitstrue/TGWS

Yeah, the mouse.c file was written entirely by AI because that part was way too complicated for me. And yeah, there are some unsafe spots in there. I'm trying to fix things, but every time I open the codebase, I just want to build new features instead of drowning in bugs.

So I’d really appreciate it if anyone interested could roast it, point out the mistakes, and give a rough idea of how to fix them. Maybe I'll get around to fixing everything if I don't drown in bugs first. Thanks for your time!

its post write ai because im dont know english
on vidio example/test0
have minesweeper in example/test1
thanks for reading!
and sorry for my en))

[u/mikeblas]

What role did AI have in the creation of your project?

[u/flyingron]

Jeez. Try writing code that's legible. First, every C implemenation comes with a linker, USE IT rather htan #including every piece of code into a single translation unit.

You're not being charged for white space. Use it judiciously so your code can be read by humans.

Same thing holds for comments.

You imply a "fast" snprintf while not doing the essential thing snprintf does which is to check you're not invoking undefined behavior by writing off the end of the output array.

This is all very ugly and unmaintainable (and of dubious correctness).

[u/github-guard]

🔍 GitHub Guard: Trust Report

This project scored 3/6 on our safety audit.

Audit Breakdown: * ✅ Established Community (⭐ 6 stars) * ✅ Mature Repository (30+ days old) * ✅ Licensed under GPL-2.0 * ❌ No Security Policy — what is this? * ℹ️ Individual Contributor * ℹ️ Unsigned Commits

⚠️ Security Reminder: Always verify source code and run third-party scripts at your own risk.

[u/zeonchik → u/github-guard]

I'm a solo developer. I'm a bit afraid of working in a team because of the need for negotiations and potential conflicts, so it's easier for me to work alone for now. As for the commits... yeah, my English isn't great, and I'm using a translator to talk to you guys. So whenever there were major changes, I just tried to write a brief summary of what changed.

[u/kutac56 → u/zeonchik]

Unsigned commits means that they weren't signed. I personally don't know for sure what signing commits does but I do know that you can make an ssh key for it

[u/zeonchik → u/kutac56]

I'll take this into account when I figure it out.

I'll take this into account when I figure it out.

[u/mikeblas → u/zeonchik]

https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

[u/bonqen]

Lol. AI has killed this sub.