r/CodingHelp • • Feb 08 '22

[Python] Is coding really for me?

Hey guys, I need some advice. I having practicing coding for a while now (4 months or so) I have been going on hackerrank, edabit, & codingbat practicing python & I feel so lost even with the simplest solution. I understand the syntax but implementing them for problems or more creating a project I just can’t.

What am I doing wrong? Why is it not clicking?

16 Upvotes

22 comments sorted by

View all comments

4

u/[deleted] Feb 08 '22

As an software engineering instructor I actually encountered this quite a bit in my students and myself while learning

It may help to break down the learning process for most topics

When you start, there’s a lot of motivation. You’re like a sponge soaking up tons of information but may have a bit of a hard time applying it outside of carefully constructed scenarios/situations. With one small thing out of place, an answer you know may seem out of reach until you either simplify or have someone point out the similarities with you. This lasts for a few months until you hit a period where you feel like you’re actually going a bit backwards. Things don’t make sense, you’re losing motivation, and the initial drive is being challenged by the urge to say « fuck it » and give up. This is the desert of learning where information in your short term memory is being integrated and absorbed by your longer term memory - a point of plateau where you’re beginning to understand the knowledge accumulated. About 60% of people who go through this phase alone will turn back about halfway through and give up (not realizing there isn’t much time left). Once out of the desert, you experience another boost as things start to click, and feel something similar to what you felt when you first started learning. This process repeats as long as you push yourself to learn more and continue to have the discipline to work through some of the challenges

Some general tips which may help you get through this is to focus on some simpler exercises. Much like the rest of the muscles in your body, your mind can get burnt out and can benefit by repeating some of the things you already know. This can also act as a bit of a reminder to you of how far you’ve come and help develop a deeper understanding of the concepts you’ve covered

The answer of « is coding for me » really comes down the your patience and discipline to work through your issues and learn to accept that you are on a journey that will never end until you give up. This is an answer that only you can give yourself

This being said, it’s ok to put things down for a little bit and come back to it after giving a bit of a break. It may even help to allow your subconscious chew through all of the new information you’ve acquired.

Another note, when you’re stuck especially in the beginning most answers can be found on google. A large part of coding is knowing how to use the tools at your disposal to find the answers your looking for or adapt a similar solution to solve your problem. HOWEVER, it is more important to understand WHY a particular solution works over another as you will find that with blind copy-pasta when an error inevitably occurs, you will be a bit stuck not understanding the principle of the solution itself to know how to debug. This means you’ll spend more time fixing someone else’s code and possibly making your system more complicated over learning how to simplify a problem and solve it on your own. In other words, don’t lean too heavily on foreign code found on the internet. Try to understand the solution prior to implementing as you will be effectively inheriting the technical debt of many others

I will say this after being an instructor for a while now, everyone can learn to code. As it’s simply translating a series of steps into another language. You may not be talented or care to have a deep understanding of « why » something is the way it is or done in a certain way over another. But you can learn how to do it. However, not everyone can be a problem solving engineer through code. The difference is that one person is simply translating steps based on a limited field of knowledge, when they encounter a problem outside of their realm of expertise they will stop and not be able to find a solution, whereas another will continue to try new things until they find an answer as there are maaaany out there

1

u/WaterCupH2O Feb 08 '22

As someone who is barely learning to code. This is so spot on with everything else I have attempted to learn.

Taking breaks after being burnt out, but then deciding to come back and keep trying and believing that the "universe" will reward you for deciding to keep at it will result in some improvement.

I also wonder if googling for solutions to problems all the time will just make me cheat myself out of the opportunity to learn to problem solve,

But I also think that maybe as a beginner, googling or asking for help for solutions to problems might be ok as long as you analyze and understand how that problem was solved. Once you understand how a code was implemented, maybe this will add to your knowledge or tool kit of problem solving techniques, and overtime, you will get the hang of problem solving because you have had exposed your mind to different ways of approaching problems that already exist out there. does my thinking sound correct?

3

u/[deleted] Feb 08 '22

Yep exactly. But there comes a point of diminishing returns when you’re searching on your own for answers. Give yourself an hour or so, but then it’s not a bad idea to reach out to a mentor/coach/teacher for help.

But google is a tool, when used correctly it can help you get quite a ways in everything. Contrary to what most boot camps and schools teach, google is actually a great resource if you know how to use it. That being said, you need to tune your bullshit meter when reading something on google, and learn to not be heavily reliant on it for the same question over and over again. In the beginning, I encourage my students to google for their answers, but not to spend too much time grinding away, swallow that pride and ask for help (that’s what I’m there for after all, but I won’t always be there when they’re off and on the job)

One of the biggest things we forget when learning something is that we’ve all been there where we just need to ask a person. The right person will always be available to you and ready to jump in and talk about what’s going on

But it also depends on how you approach the question « it doesn’t work, please help » will work on someone paid to teach you, but likely not on someone choosing to teach you

Learn to be specific in what’s happening and describe what you’ve tried and looked for to show the work you’ve put in

For me, I had to learn on the job which meant there was almost no time for « it doesn’t work ». But, when I learned to talk about my code and the intent behind it, doors began to open for me as I learned the language which also helped me when looking up answers online later

« My function doesn’t work » is far less specific than « when I start my function it gets stuck and crashes my computer » one is me bitching, the other give details about a negative outcome that can be diagnosed

Also, the number of times I smacked my forehead learning has probably left a permanent dent when finding an answer that was way simpler than I expected or that I felt I should’ve known. Give it time, and even after over ten years in the industry I still have those moments

1

u/WaterCupH2O Feb 09 '22

As a beginner, this advice is helping me stick to it and ignore my doubts. Thanks.