Then I got to the Golf Code. All of a sudden I had no idea where to start. Looking up online didn’t help much and everything I learned previously in FCC didn’t seem to help me either. I’m now on the switch statements part and that is also hard and confusing. I do not know where to start with the syntax at all. I don’t want help with this lesson or any other specifically.
Because this sudden difficulty jump has caught me off guard and it is demotivating me to go from finding something easy to feeling like I barely know what I’m doing.
Playing around with different tasks is definitely a great idea. A good way to do this is to add ‘extra’ requirements to a challenge. You have a passing solution? Cool, now can you do ‘task x’ backwards? What happens if you change up the order of the code? Experiment. Break stuff.
And when you get stuck, ignore the solutions… Come onto the forum and explain what you’re trying to do and where you’re stuck. Describing problems can actually help you solve them.
That is a good point. I should just go to the forums really and ask. I’ll work it out myself much better that way and learn far more.
…especially since I’ve told people to not ask for coding solutions when helping them yet I’ve been looking at them myself. (There isn’t a ‘I am a hypocrite and feel ashamed now’ emoji or I’d put it here.)
Playing with the tasks sounds great! I’ll go back and do that. Golf Code ect here I come!
The earlier lessons seemed easy because you were tasked to do one task at a time.
Some examples of this were the create a variable or create an array, etc.
But as you get deeper into the course, you will be asked to solve problems which will require recalling multiple lessons and breaking the problem down into smaller manageable pieces.
When you encounter one of the challenges, step away from the code for a second and think about how you would solve it as a human.
Write down the steps on how to solve it as a human.
That is an algorithm.
Then slowly translate that set of steps into code.
If you need help translating that into code, then post in the forum your written out algorithm of how to solve the problem as a human and we can help you translate those steps into code.
This process will come in handy for the later courses and in real life development.
There will be many times on the job where you will dive into an unknown codebase with unfamiliar technologies.
But you start by identifying what the problems are, come up with a solution, then translate that solution into code.
That is where you will look up documentation, stackoverflow, forums, etc.
Also asking questions on how to translate steps of your algorithm into code.
It is a common idea that it is bad to ask for guidance or suggestions, but this is a thought pattern that should be challenged.
But yes, building outside the lessons and playing with code is hugely helpful. I’ll often take the starting code, copy it into a https://replit.com/, and play around and break stuff.
Then come back here or join the one of freeCodeCamp’s chat options and discuss why it broke.
Discouraging yourself from asking for help… Mind if I ask why? For some it’s pride, for some it’s fear, some were just raised independent.
As for why I don’t like asking for help, I was labelled as a ‘gifted’ kid. I was a fast learner and creative. But this label meant I was under constant pressure to preform academically lest I became seen as not-gifted. Asking teachers for help resulted in me being told ‘surely you don’t need help to do that? You’re so smart!” ect.
I’m in my 20s and asking for help is still a struggle because of that sense of shame for needing it because I’m supposed to be ‘smart’. But I’m getting there with asking for help too.