There are more than 100 HTML tags for a reason. Learn them. Use them. Don't just use divs and spans.
Practice DRY (don't repeat yourself) but use the least complex abstraction necessary to achieve it (e.g. if you can get the job done by declaring a function, then declare a function; don't abstract it out into factory patterns or some other crazy thing just to make yourself look smart).
Prefer using the native features of your programming environment before bringing in a dependency (e.g. use vanilla JS instead of a JS library where possible).
Prefer upgrading existing programming interfaces rather than replacing them or abstracting them beyond recognition (e.g. use progressive enhancement instead of replacing the web with frameworks wherever possible).
Build technical credit rather than technical debt (i.e. when forced to choose between fast, good, and cheap, it's almost always better to choose good before the others; otherwise you'll lose fast and cheap too in the long run due to technical debt).
It's usually best to avoid JS frameworks on the frontend. Most web apps don't need them. Vanilla JS + a collection of small JS libraries is usually better.
Learn the frameworks anyway. Even though it's over-engineering to use them most of the time, most jobs require you to know them because some overpaid architect over-engineered their app, so you gotta learn how to use the frameworks and be a good citizen of the framework's best practices in order to be a good team player. Some day when you're an architect, don't repeat the mistake: prioritize architectural simplicity and do your junior devs a favor.
Do you think it's right to use vanilla JS inside reactJS project sometimes while triggering events? I really need an advice about it because recently I did that with my chat app project... I haven't been able to figure out how to do with just ReactJS hooks and features that it provides, so I used a little vanilla JS code to handle what I really wanted to do and it worked. What do you think about that?
Typically you'd want to use React's facilities as much as possible instead of directly manipulating the DOM with vanilla js. However, for some edge cases, its absolutely fine to do so.
Just make sure its an exception rather than rule.
If there is a React feature to do what you're trying to do, and it's already a React project, then most likely the best way to go is to use the React way of doing it. It's important to use the best practices of the framework you're using.
If i listened to the two last tips my motivation to learn will go down to zero.
As a Junior cs student I have very limited time to learn and the main focus right now is on getting a job.
Maybe its true that all you need is js but if what they are looking for is react dev than its a waste of time.
I think i slowly beginning to understand that its not about what is best for the job but about what people use.
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.
Do you think it's right to use vanilla JS inside reactJS project sometimes while triggering events? I really need an advice about it because recently I did that with my chat app project... I haven't been able to figure out how to do with just ReactJS hooks and features that it provides, so I used a little vanilla JS code to handle what I really wanted to do and it worked. What do you think about that?
Thanks.
Typically you'd want to use React's facilities as much as possible instead of directly manipulating the DOM with vanilla js. However, for some edge cases, its absolutely fine to do so.
Just make sure its an exception rather than rule.
If there is a React feature to do what you're trying to do, and it's already a React project, then most likely the best way to go is to use the React way of doing it. It's important to use the best practices of the framework you're using.
If i listened to the two last tips my motivation to learn will go down to zero.
As a Junior cs student I have very limited time to learn and the main focus right now is on getting a job.
Maybe its true that all you need is js but if what they are looking for is react dev than its a waste of time.
I think i slowly beginning to understand that its not about what is best for the job but about what people use.