Very basic article
We have interviewed some people and we think *they* are doing it wrong. Let’s try explaining to them that we are going to ask them to guess that arrays-only solution is actually “guess that you need to implement your own hashmap”. And ask a lot of computer science stuff because we heard that google uses it.
Apart from that a decent article for some aspects of interview preparations.
That’s a useful observation, but it doesn’t worth writing a whole article.
I’ve heard about the following cheap and dirty solution against spammers not targetting a specific site:
Add visible checkbox: “I’m not a robot” and a hidden one.
Bots will either check both or none.
I don’t understand what’s the problem with creating an instance of a component manually (just with `new`) and calling methods in a regular way. If calling `componentDidMount` in a “detached” way (BTW you can call it with `.call`) is OK.
Nice overview actually w/o comparing apples to oranges.
Ah, LogRocket, who spams and cannot tell apart a person and a company. The article is OK, though.
The same thing. As for TODO it’s completely out of row.
Zero TODO policy might be a good practice from the standpoint of issue tracking and project management.
From the perspective of code quality a better argument would be “todo’a in code encourage people to postpone refactorings and write bad code”. That’s arguable, but is at least about code quality, not something different.
After glancing over the article I can identify at least those points;
- helpers, many of them, but at least think about if/each/with
- template syntax validation at compile-time
- strict check of data
- auto-escaping (is it context-aware?)
- syntax highlighting for templates
technically all of them except highlighting could be solved with templates and several lines of code, but it’s like jQuery vs native DOM API. The former is more convenient.