Basic Algorithm Scripting

JavaScript
1

Is it normal to get stuck a lot on the Basic Algorithm Scripting, I’ve personally got through the JS course pretty easily till I’ve reached this point I’ve only managed to achieve one challenge on the Basic Algorithm Scripting, I’m not too certain what I can do to assist myself apart from going back through previous challenges, Is it normal to get stuck at this stage and how can I help myself solve these better?

2

It is perfectly normal to get stuck. For any problem where you get stuck, I’d open up a thread with your code, thoughts, and questions so far. That’s what we are here for!

1 Like
3

I am also stuck at this section. I am only 3 weeks into learning all the necessary things to become a front end web developer. My checklist in order includes:

(8 month plan)
FreeCodeCamp:

  1. Responsive Web Design Cert.
  2. JavaScript Algorithms & Data Structures Cert.
  3. Front End Development Libraries Cert. (Skip JQuery)
  4. Data Visualization Cert.
  5. Back End Development & APIs Cert.

The Odin Project (Skip NODEJS)

  1. Foundations
  2. Full Stack Javascript

UDEMY

  1. React JS Frontend Web Development For Beginners Course by Ryan Dhungel

Harvard

  1. CS50: Intro to Computer Science

Last Steps:

  1. Create Portfolio on GitHub
  2. Network and Find a Job

The first section “Responsive Web Design” was really fun and honestly fairly simple. HTML and CSS was very straightforward.

I have been able to do probably 90% of the Javascript section on my own…10% of the time I may get stuck and look at a hint or look up a video. For the most part there has been long instructions that most people can probably follow. But once I got to the Basic Algorithms section the instructions went from long and detailed to about two sentences. Now I feel like I am not doing a good job at retaining the information from previous sections because I see a problem and draw a complete blank. I feel so guilty looking at solutions or videos because I want to be able to get to these solutions myself. Last thing I want to become is that self taught developer that needs their hand held during the job. Anyone have any advice? I am noticing a lot of people getting stuck at the Basic Algorithms section so I don’t feel too bad.

Also, what do y’all think of my 8 month plan?

4

8 months is a really fast timeline. Other junior devs spend 4 years in college.

JavaScript is harder because you need to 1) understand the problem, 2) develop a plan to solve the problem, and 3) then start writing code that matches the plan. This is hard and takes a lot of practice to learn. I would start asking questions when you get stuck.

5

Thanks for the advice! Next time I get stuck I will come back here to ask questions.

I could be wrong but I think that is enough time given my circumstances. I live with my parents and this is the only thing I do. I don’t have any other responsibilities like school, kids, or a job. I wake up and spend my entire day doing problems on freecodecamp. But I am in no rush, understanding the material is more important than rushing through to me. My goal is to have a job by the end of this year, but if it takes 12 months instead of 8 then I wouldn’t be upset.

It takes 4 years for people that go the school route because of several other required general education courses. Plus they have about 3 months of breaks every year (summer, winter, spring). If they didn’t take breaks or have to take a bunch of general education courses, and worked 7 days a week with no other distractions, I’m sure they could’ve been ready for a junior dev position in an 8-month timeline. Everyone’s pace is different though.

6

8 months is fast. During the summer, students often have internships or coursework. Also, the general coursework isn’t always immediately related to programming but helps the student offer a well developed range of skills that are attractive to employers. You have to compete with what those students can offer an employer.

It’s not uncommon for the job search alone to take 3-6 months.

You can aim for a fast timeline, but plan on it possibly taking longer than expected.

7

Definitely! You’re completely right. I’ve seen people do it in 8 months, others may take 12 months, 18 months, or 4 years in a college system. I’m not denying that 8 months is fast, but it is just a goal I set for myself. The timeline isn’t important to me. I will become a front end web developer regardless of how long it takes.

8

Cool, so long as you know that learning everything in 8 is much faster than most self taught devs do and have a plan if it takes closer to 1-2 years.

Have a goal and a backup plan.

1 Like
9

Thanks for the amazing feedback and keeping it real with me! I really appreciate the honesty. 1-2 years is more realistic, and I don’t want to put unnecessary pressure on myself to get it done in 8 months. An 8 month goal reminds me to stay consistent and discipline, but it most likely will take me 12 months or more. Other than the timeline, do you have any other feedback on the checklist I have made for myself?

10

I’d move up CS50. It’s closer to the stuff in the first JS cert here on fCC

1 Like
11

Ahhh thanks! I will do CS50 right after fCC

12

Id put it in the middle of fCC, before Front End Development Libraries Cert. (Skip JQuery)

1 Like
13

Thanks for being so helpful! I will do that for sure.

1 Like
14

Idk if I should ask this question in a different thread but I am having trouble with:

" Repeat a String Repeat a String

Repeat a given string str (first argument) for num times (second argument). Return an empty string if num is not a positive number. For the purpose of this challenge, do not use the built-in .repeat() method. "

So far I have:

function repeatStringNumTimes(str, num) {
let repeatedString = “”;

for (let i = 0; i < 0; i += 1) {
let (repeatedString === repeatedString*(num));
}
return repeatedString;
}

I figured I would set the repeatedString equal to itself times whatever num…then the repeated string would repeat as many times as the num’s value. But I know my logic is off.

15

Getting stuck is inevitable but getting stuck all the time means you should find a different approach the way you think about it. Mostly missing abstraction of the exercise.

However, I run debug my code it helps a lot to see step by step in real time what is happening. I use this but there are way many others:

Click on javascript and console buttons in the middle. Copy and paste your exercise and run what happens with any value. Remember to use console.log(); then, try another value and notice if it gives you the expected result. If not, go one step at a time.

I haven’t got stuck anymore it only takes more time reading and understanding the problem.