№21767[Quote]
I’m stuck in tutorial hell and course hell and it’s killing me. Every time I try to learn programming, I think, “Okay, I’ll just take this one course and I’ll be a software developer by 2 months.” But that never happens. None of them actually teach you how to program. They just show examples, copy-paste exercises, and call it a project. I just sit there thinking I should already be building real shit, and all I’m doing is staring at a screen, copying code, and pretending I understand it. Then I try to read a book to get more depth, and holy fuck, I just get overwhelmed. My brain gets cognitively overloaded and suddenly I’ve done nothing all day. I try to understand everything at once, the entire syntax and all the language features, and then I just break down. Wtf is wrong with me? It's been like this for 2 years, I done zero fucking progress…
I started with C#. It seemed fine at first, but now I’m doubting everything, since the learning process is incredibly slow. Should I switch? Am I wasting my time? Should I just start with low level language like C? I just get stuck in analysis paralysis and do nothing for hours. I feel like I’m running in circles. How the fuck do I get out of this hell? How do you guys actually learn to code and build cool projects? How do I stop being an obsessed perfectionist who tries to understand everything at once and ends up doing nothing?
№21768[Quote]
>>21767 (OP)retard start with scratch or python, experiment with said code a few times then try build something yourself
№21774[Quote]
Making a project while copy and pasting and jeetcoding is how you learn doe. Just actually read the code and figure out what it does as you go. Even ask chatjeetpeetee
№21775[Quote]
This is how every retarded nigger ive ever met talks about code
№21782[Quote]
>>21767 (OP)read a book nigga
№21783[Quote]
create something actually visual, that's a pretty good way to learn
video games are basically the ultimate stress test for your programming knowledge. use raylib and try to create a simple game (like pong or pacman) without following any tutorials
№21795[Quote]
theres not much to know about the basics. After knowing about switch statements and classes and shit, then you gotta start learning implementations. This involves lots of reading documentation. For example, if you tried to become a game developer you would spend lots of time in Unity reading Unity documentation in order to figure out how to put things together. Someone trying to build a network protocol would spend a lot of time reading aboit network infrastructure and their programming language's networking library.
>should I switch languages?
Theres usually not much to an individual language not including libraries. So yes, but expect to come back to c# later. Programmers who get hired know multiple programming languages.
>I get overwhelmed going in depth
Pick one discipline such as netwroking, and try to build a project with it, using documentation as a guide and generative AI to help find possible avenues.
<
and when youre building projects, you want to complete them and keep them in a portfolio, since employers are looking for experience.
№21796[Quote]
For some reason people were very enthusiastic about teaching everyone to code not long ago. If you dont like it then yoi dont have to, the industry already peaked in 2020 and AI already took half the jobs.
№21798[Quote]
maybe figure out what the fuck you actually want to do with such a skill
№21804[Quote]
just fucking build shit, you dense cunt.
let yourself fuck up on purpose, that’s literally how you get good.
try random stuff, break everything, fix it.
pick a project that actually excites you and ship the fucking thing.
coding isn’t about memorizing every syntax and every unnecessary detail. no one on earth knows an entire language by heart.
it’s about stacking real experience until you can build whatever the fuck you want.
start with python and quit being a paralyzed, overthinking bitch
programming languages, frameworks, libraries are all just fucking tools.
you don’t sit there dissecting the molecular structure of a hammer, reading 400-page metallurgical reports on the steel alloy, memorizing the exact angle of the claw, or writing a thesis on the history of hickory handles before you’re allowed to hang a fucking picture on the wall.
you pick the hammer up, feel its weight, swing it a few times, maybe smack your thumb once or twice, and suddenly you know exactly how to use it for the rest of your life.
same with code. it's not that deep lil blud….
№21816[Quote]
>just fucking build shit, you dense cunt.
let yourself fuck up on purpose, that’s literally how you get good.
try random stuff, break everything, fix it.
pick a project that actually excites you and ship the fucking thing.
>coding isn’t about memorizing every syntax and every unnecessary detail. no one on earth knows an entire language by heart.
it’s about stacking real experience until you can build whatever the fuck you want.
>start with python and quit being a paralyzed, overthinking bitch
>
>programming languages, frameworks, libraries are all just fucking tools.
>you don’t sit there dissecting the molecular structure of a hammer, reading 400-page metallurgical reports on the steel alloy, memorizing the exact angle of the claw, or writing a thesis on the history of hickory handles before you’re allowed to hang a fucking picture on the wall.
>you pick the hammer up, feel its weight, swing it a few times, maybe smack your thumb once or twice, and suddenly you know exactly how to use it for the rest of your life.
>same with code. it's not that deep lil blud….
№21821[Quote]
>>21816>soybooru gifit's over for nusois
№21847[Quote]
maybe this guy could help you visualize it:
youtube.com/@CodeAestheticMalloc
№21849[Quote]
>>21767 (OP)try using monogame or raylib to write something in. you can make visual programs and see what's happening. you can also try arduino electronics. it's easier if you have some visual feedback of what you're doing. it'll feel more consequential.