Interview question: NodeJS, part 2 - 2017-05-28
Part two of original post How well do you know Node.js?.
Part two of original post How well do you know Node.js?.
Based on original post How well do you know Node.js?. In it, Samer Buna lists 48 questions which be expects a Node.js developer to be able to answer.
This course will teach you the core Node.js concepts and API modules from simple utility modules all the way to streams and clusters.
The list of 129 books deemed fundamental to the art of programming and includes books for various languages.
This is a guide that anyone could use to learn about the practice of front-end development. It broadly outlines and discusses the practice of front-end engineering: how to learn it and what tools are used when practicing it in 2017
An awesome explanation of GOF design patterns. The only way to learn pattern is to know what problem it solves.
“How could I organize my code?”, “What is the best way to design this?”, “How can I make my application more modular?”, “How do I handle a set of asynchronous call effectively?”, “How can I make sure that my application will not collapse while it grows?”.
If you have such questions without answers, that book is definitely for you!
The aim of this book is to guide you through this emerging world of patterns, techniques and practices, showing proven solution to the common problem.
To rock the interview to achieve what you deserve and to improve your concepts about front end technologies, I have consolidated a list of questions and answers. It’s a one stop solution for front end interview process.
Being a SOLID developer in JS isn’t so as straight forward as in other languages. Some developers consider functional approach. Others chose OOP style. Some stand in both line. And other think that having class is wrong and redundant and prefer factories. But still, SOLID principles are the basic pillars of object oriented programming.
But what are they?
What’s the Difference Between Class & Prototype Inheritance?
This can be a tricky question, and you’ll probably need to defend your answer with follow-up Q&A, so pay special attention to learning the differences, and how to apply the knowledge to write better code.