🧰
Baseline tooling and plugins
The collective impact of several (on their own) small tools can make the difference between misery and joy very tangible.
Really, one of the very first things you want to make sure of is that the code looks and reads the same, regardless of who wrote it. Using these tools, now you can.
When it comes to more IDE-centric plugins in the security department, I highly recommend the Snyk Vulnerability Scanner (the successor to vulncost) for Visual Studio Code. Other nice ones include:
🎯 Example: You'll see that this project has configuration files such as
.eslintrc
and .prettierrc
laying around.Last modified 1yr ago