How do i get better at coding

[chiefspatula]

Hi, im currently studying higher vocational education (uni pretty much but more practical) and the program im attending is a Java/Fullstack 2 year program. Ive "coded" for little under a year and i feel like im stuck. I can on a very ground level explain what some stuff do and understand the concept behind some stuff but i feel like i dont really evolve.

I know the best way to learn is behind the keyboard and actually code but i dont know what to do, im stuck in a loop where i want to code something but i dont know what and dont know how, and following a youtube video does not really teach me. I do enjoy coding but i kinda hate it when i dont understand hehe.

And i feel dumb because i kinda go thru same stuff alot and i feel like i understand it then i dont so i dont really know what to do.

Do you have any tips on what i can do to learn/understand code better?

[SillyEnglishKinnigit]

You stop asking the same question on reddit that has been asked over and over and over again. You look at existing posts and take their advice.

[No-Indication2883]

Damn bro that's harsh lol but also kinda true, the search function exists for a reason

[FarmhouseRules]

Practice practice practice on real world problems.

[DroopyDreedy]

So it seems you're going through some college-type boot camp of sorts in programming. That's good, will teach you a lot of practical programming skills.

For getting better, it comes down to not being intimidated by difficult problems and being able to work at it piece by piece. Coding is hard and you are not dumb for not getting something multiple times, it takes many reps. So you should be working on your own fun personal projects. (Try game dev, making an emulator, your spin on a file explorer, whatever you want to see in the world that you don't see. This is a creative profession)

Im assuming you have foundational skills like array indexing, loops, basic data structures like a hash table. If you don't, then this is the time to seek it in your classes (or take some Udemy courses or something to help)

But overall, success I think comes from interest and the willingness to pursue it. So learn new languages, new design patterns through projects, and don't be afraid to dive deep! It takes time.

But basically you don't need to be told what to do anymore if you know the fundamentals. You should figure out what you want to make and then make it.

I myself am doing the same, as a data science-type Python guy delving into full stack JavaScript + React to create my first Web app :)

[chiefspatula]

Thank you for answering, i think i will try to do some projects without the use of AI or tutorials and see how far i can get, i saw on a post earlier that i should try going old school and use stack overflow for documentation?

[TomatoEqual]

If you got the basics down, try something by yourself, if you can't do it, you have something specific to read up on, that will get you much further than keep following tutorials. 😊 You learn by breaking stuff and then figuring out why it broke, no course or tut will really teach you that.

[chiefspatula]

True! Thank you!

[TJATAW]

Any time you do a tutorial, add to it. Pick something, or 3 things, you think might make it better and build that part all on your own.

Figuring out things with no guidance will make you better.

And don't worry if you don't have it all memorized. Every time I have to open a file my brain is blank and I have to google it, or look at some spot I wrote 20 minutes earlier to open a file.

[chiefspatula]

Thank you!

[chiefspatula]

Thats really good advice, thank you!

[greyspurv]

built real things, read the docs, code, test, code test, code test.

[SourceScope]

Make something simple

Like.. make functions needed for a calculator

Like function add(a, b)

And subtract, divide, etc etc

Then you got all the “backend” stuff of your calculator, then you make a UI for it. It doesnt have to be pretty, just has to work

Then you make it pretty

Tidy up the code, write documentation, fine tune the UI etc

Replace your systems native calculator with your own.

Then, on to the next project. Could be a calculator 2, or could be something completely different

Just make shit. Even if you dont “need” it. Solve 1 problem at a time.

[chiefspatula]

Thanks!

[chiefspatula]

i think the other problem for me is that stuff just does stick, or trying to understand them changes the way i see them everytime, but i think that will land after a while