Skip to content
markdown guide

I was not writing any test for any kind of projects before. Then, I realized I'm doing too effort to test something manually to check if it is broke or not. Also, I can't be brave to refactoring or deleting piece of code. So, I decided to write test to improve my productivity and self-confident. I don't force myself to write test for every piece of code but I try to write test for important parts or for parts which are too many times I've made manual test on.

So it does not matter if it's side-project or main-project. It's related about the productivity I think.
I don't want to make manual test over and over any more. :)

Classic DEV Post from Mar 28 '19

How to publish packages to npm (the way the industry does things)

It's not simple to publish and update packages to npm according to industry standards. We'll go through the steps involved and what you have to watch out for

Usman Suleiman profile image
Love learning new stuff