You know how Node.js seems great until you have to write an asynchronous call. Dabbling through Stack Overflow posts doesn't give you much insight. Callbacks look counterintuitive and messy.
Reading the official docs makes you no wiser.
You're starting to have a hunch that there's something happening outside of your code. What is it? Programming something you can't see is as easy as solving Rubik's cube blindfolded.
It's easier to give up on Node.js and go back to good old PHP and shell scripts, maybe even Java.
How come there's no single good resource on the operating principles? There are bits and pieces scattered across #node.js, Slack and discussion forums.
It looks like it takes five months and reading through half of Github to "get" callbacks, asynchronicity and worker threads.
Imagine orchestrating your next Node app so it calls three web APIs, posts to Twitter and scrapes two other pages all at the same time using asynchronous calls.
Imagine having the surgical moves to modify existing asynchronous code base. You could make calls fly after each other instead of at the same time. You could bend Node to your will.
You'd be using technology stack that's from this decade. And you'd be hot stuff on the job market, too.
It's true, asynchronicity can scare off people from learning Node, but it doesn't have to.
The operating principles of Node are simple and straightforward when you zoom out from the level of individual statements and for-loops. When you focus on the system that operates outside user code, you'll grasp the right mental model for writing Node programs.
A clear mental model allows you to approach Node programs the right way. The course shows you a glimpse of the engine room while still keeping Kernighan & Ritchie on the bookshelf.
Theory-only courses are long gone, and in this course, you'll get to practice your new skills early on. In fact, you’ll be writing your first app in 30 minutes. Home assignments include meaningful programs such as a stress relief exercise, an MD5 file hasher, a Twitter bot, and a news aggregator.
3 Week Course
5 Home Assignments
“Coming from traditional programming background, I always thought callbacks are a little counterintuitive. “
“One thing that always surprised me was there was no single good resource on the operating principles.“
- Developer for 8 years, new to Node.js -
Yes. If you're not happy with the course, hit us an email within 30 days and you'll get a full refund.
No. This course is for learning the operating principles behind Node.js. We'll use callbacks and plain Node. Learning async-library, Promises, generators and async/await is much easier after you've learned the basics, though.
You should allocate 30-60 minutes a day for the course. Each lesson is bite-sized in length and is digestible in one session.
If you submit each homework assignments within a few days, you'll finish the course in three weeks.
The course pauses on homework assignments, and you can take as long as you need. The course continues when you submit your answer.
The course is delivered through email. You'll receive one email a day. And at the end, you'll have access to all-in-one PDF with all the lessons and a ZIP of all source code.
Yes. The course pauses until you submit your answer. The answers are kept private and are first and foremost for yourself.