![]() Since I’ve completed the certifications, I’ve built, rebuilt, and re-rebuilt many different projects using whatever technologies were relevant and interested me - hitting constant issues, working through, digging through documentation, looking at examples, reading Stack Overflow, etc… On this portion of my learning I’ve spent probably the better part of 8-10 hours each day on average 6-7 days per week. FCC gives you a framework at the end of which - in my opinion - you will have a decent foundational knowledge to understand what it is you need to go after independently and learn on your own or dig into further. Once I completed my certifications, I asked myself if I could build from scratch, in my own environment locally, and deploy it. I started FCC in June and got my certifications completed around October - putting in probably 6-8 hours a day usually 6 days a week. I’ve decided I wanted to divert my career path more towards development, so I jumped in head-first this past summer to iron out my old skills and learn new skills that are relevant. I had a bit of formal education (MIS degree which incorporated CS curriculum at University of MN) and professional experience with coding (I’ve worked in Global IT organizations and as a Solutions Architect for a custom software dev company throughout the past 10 years). Whenever I had a job interview, the first thing they wanted to see was what I’d built. Just learn, learn, learn and build, build, build. You’ll always have some mistakes, but as you get better you’ll have fewer and be better at spotting them. But the more advanced the concept, the harder it is going to be to absorb. ![]() The first lessons are easy enough to absorb right away. You would learn less if FCC spoon fed you everything.īut I guess making a mistake is a process that should be. As a professional programmer, on a good day, I only have to google things or consult the docs 20 times a day. ![]() You are expected to do side research about things that confuse you. …but my javascript learning process doesn’t move as fast as html / css, which makes me think there’s something missing. Not a lot of people can do what we do because it is hard to learn and takes a long time. I call it “job security” - if this were easy it would pay minimum wage. If you can’t do it, go back and do it again. Keep reading books and doing tutorials, but do it in parallel with actually building things.Īctually, being unable to complete the JavaScript directives, which are explained simply, makes me pessimistic. But once you have a basic knowledge, I think this is important. ![]() You will make mistakes and learn from them. Just start building things and you’ll run into problems and have to research things. They help you get ready but the real learning is when you jump in the pool and struggle. Books and tutorials aren’t the same as coding. My point is that you could read all the books you want and all the youtube videos but the real learning is when you get in the pool and struggle. I always say, “you can’t learn to swim without swallowing a little pool water”. But they can be good practice and interviews often use these types of problems for interview, sometimes even using sites like these.Īnother thing I would suggest is to start building crap. Keep in mind that some of these have poorly written challenges and people with attitudes there. There are also plenty of web sites with algorithm challenges, like Code Wars, etc. I believe the solutions are in Java, but you can probably tell what’s going on and there are people that have published JS solutions online if you look. It deals with a lot of ideas about interviewing, but the meat of it is algorithm challenges. I would also throw in Cracking the Coding Interview. I agree with a lot of the suggestions here. I’m not saying learning Java is a bad idea, just that if you are still learning JavaScript, it may not be the best idea. So first of all, Java and JavaScript are different languages, right? They have some similarities because they both descend from C, but they are very different languages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |