Some of the things which I generally find common across all the novice front end engineers is that, in essence to meet sharp deadlines and for ease of use they all tend to use libraries and frameworks. As a result, they miss the basic beauty of the language. Assume it like this. Libraries are a dashboard to control and use the language who sits between you and the main language engine. You can perform all the actions and functions which are available on the dashboard but the problem arises when it comes to perform some action which is not available on the dashboard and you never bothered to look into actual engine to implement the action yourself. The real path of learning should be, first you understand the language and it’s insights, then you can jump into a library/framework which helps you rapid development your stuff.
Very few were aware that instead of making lot of DOM getter methods and filtering the nodes by writing long complex code just because you want nodes matching some particular selector rule, now you can use the new DOM selector api <element>.querySelector or <element>.querySelectorAll to avoid unnecessary filtering of nodes. Also, I explained them why you shouldn’t do DOM manipulations blindly. Reflow and repaints are costly and can significantly impact your web application performance if not taken care of. Use of timers can help your browser restart run away time and restart it’s stack call trace to avoid browser crash.
It was really fun talking to developers there and talking about some of their common code problems. And, I also learnt a lot while explaining the stuff to them. I really thank Verchaska for inviting me