Facade

Last month (i.e May of 2020), during the lockdown, I started wandering over the npm community and the ways to build an npm package, so that I have my signature on the open-source world. I was working as a full stack developer then, and my front-end work was in reactjs. Initially, I was frightened to develop something in react but then I fall in love with the idea of reactjs.  My work became my hobby and loved the idea of reusable components with less amount of code. The component re-usability and the ease of developing one ignited an idea of another npm package. But unlike last time ( LNFC ), I was not so set on building one npm package for react components. So I started learning how to create one and then managed to do so. The package is called nuoreact, simply an acronym for nuomorphism and reactjs. Nuomorphism is a design concept, that is well explained in this blog post  here I was intrigued by the concept of nuomorphism, and the mediocre nuomorphism component packages in ...

So lately I published my first npm package. It gave me immense joy to share it with you here. But it's not something I was planning to do. Things happen you know. Quickly and unexpectedly. I was working on a MEAN stack project for the last 2-3 months. When working on the backed of stuff, I was going on creating files and doing the same or somewhat same set of codes over and over again. If it's something related to user, then the file name of the controller is user.controller.js and the service file name is user.service.js. With method, names are getUser, or getUsers, or deleteUser. And if it's on some other stuff, say a device, most of the logic remains the same, except this time the name of the method and files changes to deleteDevice and device.controller.js etc. You get the point. So which means I am wasting a lot of time on somethings that I could automate, time which I could easily focus on optimizing the code and making it bug-free. So I wanted to hav...