"You remind me of a friend that has been waiting for 2 years to get some experience in order to give advice to beginners."
Your friend is right. When I see advice like the ones in the article, I usually say "I hope your doctor and your lawyer are better at their job than this."
I've handled over a 100 front-end interviews for my employers and code like that would seriously hurt candidates chances.
It's pretty obvious that these tricks do not make your JavaScript more readable, they're not supposed to help with readability.
The purpose is to show the reader that things in JavaScript can also work this way.
I'm sure you're an expert in the bleeding edge technology that your employer is using and you're really good at those interviews, but it seems you just missed the point of this article.
"of, relating to, or manifested in practice or action : not theoretical or ideal"
" capable of being put to use or account"
"The purpose is to show the reader that things in JavaScript can also work this way." - even you yourself describe this precisely as theoretical. Practical is "here is how this should be done".
Look, I would not be commenting here, if I haven't seen over and over again junior devs reading such articles and rushing to use tricks from them everywhere. The best course of action for you would be to remove half of the tricks you've written, since only harm can come out of them. The question is - are you willing to admit you were wrong or is your ego more important to you than your readers?
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
"You remind me of a friend that has been waiting for 2 years to get some experience in order to give advice to beginners."
Your friend is right. When I see advice like the ones in the article, I usually say "I hope your doctor and your lawyer are better at their job than this."
I've handled over a 100 front-end interviews for my employers and code like that would seriously hurt candidates chances.
It's pretty obvious that these tricks do not make your JavaScript more readable, they're not supposed to help with readability.
The purpose is to show the reader that things in JavaScript can also work this way.
I'm sure you're an expert in the bleeding edge technology that your employer is using and you're really good at those interviews, but it seems you just missed the point of this article.
merriam-webster.com/dictionary/pra...
Practical:
"The purpose is to show the reader that things in JavaScript can also work this way." - even you yourself describe this precisely as theoretical. Practical is "here is how this should be done".
Look, I would not be commenting here, if I haven't seen over and over again junior devs reading such articles and rushing to use tricks from them everywhere. The best course of action for you would be to remove half of the tricks you've written, since only harm can come out of them. The question is - are you willing to admit you were wrong or is your ego more important to you than your readers?