Changing stuff and seeing what happens. Yeah, about sums up my "debugging".
Presi300
Glory to 2B's as~ I mean mankind...
What I usually do is I explain what the function does and, if not self explanatory, explain why it does such thing. Like, with the clock example, I'd explain that it tells the time and then, if not immediately obvious, explain why the time needs to be known... Smth like that.
There is no "correct" way of commenting code. I personally think the more verbose, the better, but that's an unpopular opinion afaik. As long as the code can be understood, the comment is doing it's job.
PS, I'm also kinda new to programming, mostly doing JS and React stuff
spoiler
I love putting memes in comments :P
No, I'm broke...
My advice: try them all and see what works.
I'd recommend nobara if you don't like gnome, but I am fairly biased towards it, so idk what my recommendation is worth.
Endeavor is also a decent choice, provided that you wanna deal with some arch Linux quirkiness from time to time.
But yeah, try them all and see what works best...
plan on not using Wayland
Strong disagree on that one, X11 sucks
Coffee. Scary amounts of it.
WinBTRFS is quirky at best. For the better or for worse, you're better off either setting up a network share or sticking with mounting the NTFS partition.
So you're telling me that you can use smth like a drill/angle grinder or go to a concert without ear protection and not feel pain?
Wait, you're telling me it isn't painful for everyone?
Linux mint or ZorinOS. Try both and use the one you like more...
Sums up my experience with C++. It's fun until you actually start using it and then you get hit with: Idiotic syntax, no package management, C compilers, different operating systems, compiling in general, having to code everything from scratch, memory management and a lot more...
Shit hit me so hard, I began learning web dev instead and never looked back...