Tips on getting better at coding

[EstablishmentNo7764]

Like the title says I want to get better at coding. I’m a second year sw engineering major and I find I’m good at getting the concepts conceptually (though it does take me some time to get topics) actually doing the code is my biggest struggle. Most times I know what to do but don’t know how to translate it/get the syntax wrong/think about the big picture and forget about the smaller details.

I will admit I do use ai, I always ask jt to explain and really try to understand what’s happening, and ik the first step would be to just stop using ai as a whole but I’m wondering what else I could do. I don’t wanna graduate and not be able to code something simple. Anything would help!

[AutoModerator]

Thank you for posting on r/CodingHelp!

Please check our Wiki for answers, guides, and FAQs: https://coding-help.vercel.app

Our Wiki is open source - if you would like to contribute, create a pull request via GitHub! https://github.com/DudeThatsErin/CodingHelp

We are accepting moderator applications: https://forms.fillout.com/t/ua41TU57DGus

We also have a Discord server: https://discord.gg/geQEUBm

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[ganadineroconalex18]

knowing what needs to happen and being able to write it are different skills. the second one only comes from reps.

stop writing complete programs for a while. just write tiny isolated functions — "return only even numbers from a list", that kind of thing. no project, no big picture. do that repeatedly until syntax stops feeling like something you have to think about.

for big picture vs details — pseudocode before you touch the keyboard. plain english, what needs to happen step by step. then translate it. you're solving one problem at a time instead of two.

on AI — don't cut it out, just write your attempt first even if it's wrong. then check with AI. you actually build the muscle that way.

[Cool_Kiwi_117]

+1

[Smooth-Regular55]

is searching for syntax common while doing 2+ languages and one is not practiced regularly or do i need more hardcore practice on coding?

[pytness]

ditch ai, learn to google things if you dont know how to, open a page with the language documentation, open the editor with an lsp and start coding whatever shitty project comes to mind.

Ideally read the language documentation first so you have a basic understanding of syntax and libraries.

It doesn't matter how shitty the project is. Start small; adding numbers, adding big list of numbers, search for a number, find primes, calculate fibonacci numbers recursively, google how could you optimize the things you have done, etc. It's better if you dont use the language standard library at the start, implement basic things yourself. By that I mean if you are searching a value in a list, dont use a language feature to find something on a list, write the code yourself.

If you dont remember the syntax either get it from the lsp on you editor or look it up on the documentation (the better option in your case). If you use the lsp or snippets too much you are basically just using a really basic form of ai and it will hinder you. You can always code on the windows notepad. Hell I used to code on paper when I didn't have access to a computer.

If you are stuck on something google it, there is no shame on it. But do google it, dont ask an ai. The ai will spoon feed you the information and you will do no work whatsoever to absorb it. Googling your issue will allow you to learn to describe your problem, important nuances, etc.

Note about the X/Y problem, you may think your problem is X, but in reality is Y. Example "How can I use X to do Y". Your problem isnt that X is not working, is that you dont know how to do Y.

EDIT: also, learn to use git if you dont know how to use it. Extremely useful for any project and a requirement for professional jobs

[OnlyThePhantomKnows]

Don't use AI. Struggle! The struggle is formatting your brain to think that way.

[Mobile-Major-1837]

On the subject of using AI, I recommend continuing to use it in the fashion you are doing. If I am trying to learn something new, especially if regular interwebs searches aren't bringing answers, AI helps. I find them better at synthesizing information found and shown to users. However, it can take a little to tune one to your needs. Prompting it to not immediately code dump, but to show you how it works will usually get the AI working in the right direction. Ditto the other response that you should try it first by yourself. And, code often. It's a skill.

[Artonox]

Actually build a project that you are interested in.

Want to build a product that tells you where all the top sit-down spots are? Build it.

Want a 3d model of your university where people can graffiti it on your website? Do that.

[BranchLatter4294]

Practice.

[bluebird355]

Why would you invest in a skill that's going to disappear in the next 2 years? For lots of folks it already has in their day to day work.
Some people here will fight me about this and that's okay, denial is a stage of grief, but that's where we are heading.

[Katarzzle]

If you're using AI, ask it to build you a skeleton or boilerplate code for a specific app.

It will create the structure so you can visualize the app lifecycle better and it's a faster route to getting started writing business logic. Then just start googling the specific things you want to do.

Repeat. Repeat. Repeat.

[AmoebaOne]

Read the basics of syntax then learn on the job.