Something I highly recommend is code linting, it's essentially a code scanner that analyses your code for bugs and other issues such as stylistic conventions.
For example, Python has PyLint (there are other linters available too), it's really useful. They should be available on a majority of editors and IDEs I believe. A cool thing about PyLint is that it follows the PEP8 guidelines where it kindly reminds me that my variables should be snake case instead of camel case or that I need to add a docstring to my new function. Definitely worth a look!
is there a quick fix auto applied when possible. I once had set up something like that and after adding --fix or something like that I never had to worry about cases for that project.
Aslo faling on warning in rust was a good eay to learn proper language style
Something I highly recommend is code linting, it's essentially a code scanner that analyses your code for bugs and other issues such as stylistic conventions.
For example, Python has PyLint (there are other linters available too), it's really useful. They should be available on a majority of editors and IDEs I believe. A cool thing about PyLint is that it follows the PEP8 guidelines where it kindly reminds me that my variables should be snake case instead of camel case or that I need to add a docstring to my new function. Definitely worth a look!
I work on a project where the build fails if you break the linting rules. It's awesome.
is there a quick fix auto applied when possible. I once had set up something like that and after adding --fix or something like that I never had to worry about cases for that project.
Aslo faling on warning in rust was a good eay to learn proper language style
yep auto fix, which works up to a point. I'd rather have it manual that completely trust the linter to fix everything though, oldschool like that :)