Recently, I have been doing some mini projects to learn new things or practice skills. But how can I get to know I am following best practices? How to improve the quality of code and implement better logic?
What are your thoughts on this? How you improve your code and how you do code reviews for your side projects?
Top comments (6)
Hi Yogini, depending on the programming language you use, there are tools to help. For example, ESLint for Javascript projects.
Another suggestion I have is to create pull requests for your side projects. Once created, review your own code and pretend to explain what's going on to a coworker. Sometimes, simply reading our own code helps identify areas we can improve.
Lastly, I suggest you follow people online who share their experience. Blogs, videos, live streaming but also read books such as The Pragmatic Programmer or Clean Code.
There is an actual term for this called rubber duck debugging and it's a great practice.
Thanks for sharing this! Rubber Duck Debugging is a new term I came to know today.
If you code in front-end, one way to make sure to write a quality code is to have linting rules.
Below is the project where I've added linting rules for TypeScript, SCSS & and GIT commit messages:
github.com/SaurabhLpRocks/vscode-w...
The same project is explained in my medium blog:
“VS Code Workflow for Dockerize Asp.Net Core & Angular App” by Saurabh Palatkar link.medium.com/cnSZujPyU3
Great work with done with minor details! Glad you shared it with us Saurabh. Linting is always a good option, but I am talking more about improvement in logic and code structure.
Sharing the code with sites like Reddit and discord channels is a great way to get feedback.