The latest articles on DEV Community by Emmanuel Watila (@devsgnr_). https://dev.to/devsgnr_ https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F623639%2Fca1692f3-fac1-4706-b76c-e6c3ac876a21.jpeg https://dev.to/devsgnr_ en Emmanuel Watila Sat, 16 Apr 2022 15:35:19 +0000 https://dev.to/devsgnr_/house-keeping-3m72 https://dev.to/devsgnr_/house-keeping-3m72 <p>After working as a React developer for over 2+ years now, there are some things I have learned and some that I have rapidly unlearned. I have worked on numerous projects ranging from fintech, edutech and all the way down to health and lifestyle.</p> <p>In my day to day, React and Next.js are my daily drivers but Next.js more than React.</p> <p>And during these times there was one thing that had always bothered me, some devs don't do enough "house keeping".</p> <h2> House Keeping? </h2> <p>Yes, house keeping.</p> <p>In a bid to move fast and deliver projects to client we sometimes leave webs of mess behind. Does the code work? Yes, Is it at it optimum? Maybe not. At the end of the day, the application is delivered to the client and that's the end.</p> <p>Recently, I started building a project/product of my own, written in Next.js with some extra stuff and a BaaS (back-end-as-a-service).</p> <p>After reaching a particular milestone, I added a ticket and raised a Github issue named <em>"Implement proper code documentation in form of comments and code optimization"</em>.</p> <p>What this does is that it serves as a reminded that coding or programming is an art as well as it is science, things need to have a definite structure. </p> <p>It also saves me from having to start cleaning code when the codebase starts to become a little bit thicker.</p> <p><a href="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ffex0kk715og2f1esnxd6.png" class="article-body-image-wrapper"><img src="https://media.dev.to/cdn-cgi/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Ffex0kk715og2f1esnxd6.png" alt="Github issue for code cleanup and optimization" width="800" height="94"></a></p> <h3> Benefits of House Keeping </h3> <ul> <li><p><strong>Code is clean</strong><br> At the barest minimum this is what you want to achieve, clean code. Readable, maintainable and extensible.</p></li> <li><p><strong>You'll be happy writing clean code</strong><br> This is the first time in a long time, that I have actually enjoyed writing code, and also the first time in a long time that I want to continue working on a project.</p></li> <li><p><strong>Confidence, Typescript is the GOAT</strong><br> Working with Typesscript has given me confidence when it comes to writing code, I feel safe knowing things will function the right way. Not just Typescript but any language that has static type checking will help you have confidence in your codebase.</p></li> <li><p><strong>Easier documentation</strong><br> Documentation becomes way more easier when your code is clean and when each component is where it's supposed to be.</p></li> </ul> <h3> Conclusion </h3> <p>I have had the best time writing code on this project, for once I have some much confidence in the work I'm doing. There's a new stride in my step and a new found love for coding that I have never experience before.</p> typescript react webdev productivity