I am a senior backend developer, but as team leader I see about front-end development too. I have seen horrors. I have many tips, I think.
Don't blindly believe the things you read. I have read sooo much things like "NodeJS is a great performer" or "React is more suitable for complex projects than Vue/Svelte/XXX", and so it happens that both are lies. As far as I can tell, Vue and Svelte at least, can do anything React can, and can do it simpler. I have asked to the authors of that phrase for explanations, and nothing comes up. The NodeJS one is a blatant lie too. Do you know that there are over 200 other sever setups that beat NodeJS? That's the fact. Yes, I think NodeJS beats 200 other server setups, but would you say that is "great performance"? I wouldn't. I say it's OK. That's it.
If something is called "dangerously", think 3 times before using it.
This one comes in hand with the previous one: If you are using a component framework, then avoid dynamic HTML generation like the plague. Is this not why you are using the framework in the first place???
Redux is not for everything. The team of contractors @ work stored everything in Redux. Every Thing. When I had to work a bug out, it was such a mess I ended up removing the data out of Redux, and voilá, it worked with regular React states. I asked: "Guys, I'm no front-end dev, but isn't Redux for data that is needed in multiple places only?" To which they replied: "We just decided to store everything there".
Learn your configuration system. If you are using dotenv and .env files, use them well. However, this is a sub-optimal configuration system. There are better ones out there, including wj-config, the one I made. Designed for modern JavaScript and works identically client or server-sided.
That's just from the top of my head.
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.
I am a senior backend developer, but as team leader I see about front-end development too. I have seen horrors. I have many tips, I think.
Don't blindly believe the things you read. I have read sooo much things like "NodeJS is a great performer" or "React is more suitable for complex projects than Vue/Svelte/XXX", and so it happens that both are lies. As far as I can tell, Vue and Svelte at least, can do anything React can, and can do it simpler. I have asked to the authors of that phrase for explanations, and nothing comes up. The NodeJS one is a blatant lie too. Do you know that there are over 200 other sever setups that beat NodeJS? That's the fact. Yes, I think NodeJS beats 200 other server setups, but would you say that is "great performance"? I wouldn't. I say it's OK. That's it.
If something is called "dangerously", think 3 times before using it.
This one comes in hand with the previous one: If you are using a component framework, then avoid dynamic HTML generation like the plague. Is this not why you are using the framework in the first place???
Redux is not for everything. The team of contractors @ work stored everything in Redux. Every Thing. When I had to work a bug out, it was such a mess I ended up removing the data out of Redux, and voilá, it worked with regular React states. I asked: "Guys, I'm no front-end dev, but isn't Redux for data that is needed in multiple places only?" To which they replied: "We just decided to store everything there".
Learn your configuration system. If you are using
dotenvand.envfiles, use them well. However, this is a sub-optimal configuration system. There are better ones out there, including wj-config, the one I made. Designed for modern JavaScript and works identically client or server-sided.That's just from the top of my head.