July 08, 2013
You might think that i was a bit naive to have recognised the problem, but that’s ok. The important thing is i did realize the problem. And now i am trying to fix it.
Let me list down the why’s in a list because i know that’s how you like it.
If you like programming, automating anything will make you happy. I can’t stress it enough. A happy programmer is a more productive programmer. For me, this is the most important reason to write tests. Writing tests makes you write better code. And the only way to come to terms with this fact is by trying it yourself. Write some code without test. Now redo the exercise by first writing a test first. See the difference? No? Then maybe go back to the first point. Research shows that writing tests for your code reduces bugs. We don’t like bugs, do we? Except while taking macro photographs. If you are working in a team, answering why to write tests is a no brainer. Hope the above reasons convince you that writing tests is good.
Also getting into react-native of late and loving it. `react-native` might be the future of mobile development.
Loves functional programming. Knows a little bit of purescript, haskell and elm. You can ask me about functors 😜.Follow me on TwitterLook at my open source work on github