Here are 438 free online programming and CompSci courses you can start in May & A Special Bouns Article from FCC-Forum

Hola, All 438 of these courses into the following categories based on their difficulty level: Beginner Intermediate Advanced Courses that are being offered for the first time are marked as [NEW]. Many of these courses are completely self-paced. The rest will start at various times later this month.  

View List Here

Bonus:

Read these books, complete these two courses, this certification, and these three projects


Special note: No, you're not done until you finish every step, in order.
If you don't have access to Netflix, or just want an alternative to the Netflix Project
Clone Spotify - you can sign up for a free account.
Spotify268
You can use their API to search pretty much all of the data they have available:
Spotify Web API249
You can't actually pull full length versions of the media to play in your app, just play the demo track :wink:

Notes (keep all this in mind as you work down the list):


Development Enviroment

  • Pick your favorite editor, write all your code on your own machine in that editor
  • Save all your code to GitHub
  • Publish all your projects to the web - using surge.sh, github pages, heroku etc
  • Avoid codepen.
  • Avoid cloud 9 or any other "just code it on the web so you don't have to learn how to code on your own machine" site.
  • Whenever you are doing a "Clone this" project - use only assets you create yourself or that have copyrights which would allow you to use them.
  • Develop the habit of giving attribution for everything you use that was the product of someone else's effort.

Power up your learning - make every minute count towards making you job ready

  • When you're working through a book, type out the example code and do all the exercises.
  • When you're working through a course, do all the assignments.
  • When you're building a Project, include a built process (like gulp574), include at least 5 automated tests (Karma299, mocha152, sinon, chai, jasmine, tape, whatever works for you), include a README.md file that clearly explains the project, and practice using meaningful
    commit messages417
  • Use each project to demonstrate that you can deliver an optimized product. Implement tests (as I mentioned above), use your build process to minimize assets, use a linter (like ESLint180) on your JavaScript and have some method to your madness when it comes to your css naming conventions (like BEM343)
Every resource on this list is freely available on the net. And, it was meant, by the author, to be free. There's no "you can find a pirated copy if you look hard enough" nonsense here. No resource listed suffers for this. There are other comparable resources you could pay for, none of the paid versions would give you some awesome advantage over those listed.
This is the "direct route" to your goal. I didn't promise it would be easy though. You'll need to put your big programmer pants on and barrel through even when it gets tough. Keep the goal in mind. Don't go wandering off looking for 12 different extra resources each step of the path, suck it up and stick to the list and keep at each step until you finish it. This is not the "easy path", this is the "work your ass off, keep at it, don't go wandering off to YouTube muttering 'oooh shiny'" path.

If you get stuck and need to look something up:

  • Use the official docs.
  • Use MDN
  • Train yourself to write the code, not copy paste it.
  • Stack overflow should be a resource for ideas, not a crutch to help you avoid writing code yourself.
  • Shay Howe394 has a good overview of HTML and CSS if you need more than you got in the CS50 and MEAN stack course to feel comfortable with the projects.
  • If you're at a loss for how to figure out the design for a page you're building, reference Google's Material Design documentation627. Try to become familar with it by the time you finish the list of resources in this post. It will save you from having shoddy looking pages.

If you get lost. If this is too hard.

  • Buck up camper - no one said this was easy - it is WORTH IT though.
  • Figure it out. Ask for someone to point you in the right direction.
  • Don't Quit.
  • Don't Panic!

If you don't even know where to start with GitHub and/or Surge.sh

Using GitHub

thenewboston's Git Tutorials Playlist on YouTube384
The Git Tutorial on CodeSchool268
GitHub site119
Git Cheatsheet283 - new link, the old one changed

Using surge.sh

YouTube video by Hiếu Sensei walking through the entire process233
YouTube video by David Wells that goes into far more detail109
Very brief article and video showing how to quickly deploy to surge.sh98
surge.sh site132

if you're on fire and want more to boost your chances even higher or if you need a "productive break" from the main guide

  • sign up for https://www.codingame.com846 - finish every training challenge up through "very hard", for the hard and very hard challenges, you'll likely need to have worked down the main list in this post to the data structures book
  • learn Sass314
  • Join one of the Chingu cohorts that @tropicalchancer puts together and actively participate on one or more group projects
  • Project: Clone this1.2k landing page
  • Project: Clone this643 blog template - note that there are multiple pages
  • Project: Clone this737 online resume template
  • Project: Clone the front page of this581 website modifying it to highlight a different product or industry. Make special note of the secondary navigation bar at the top. Implementing that is the highlight of this project.
  • Project: Do one of the FCC projects not listed in this guide.
  • Goal: Contribute one pull request per month to an open source project of your choosing.

If you're thinking @P1xt, you're nuts, I just want to be a frontend developer, this is too much

  • No it's not.
  • This will actually do what the frontend cert alone wont. It will prepare you to do the job of a frontend web developer in today's market. Writing some HTML and CSS isn't all there is to the job. This will prepare you for the rest.
  • Don't quit.
  • Don't panic!
- From FCC Forum

Comments

Popular Posts