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.
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.