The first time I ran an end-to-end test of a web service I was developing I had tears come up to my eyes from joy and relief. You can feel like that too. If you always write at least one end-to-end test as soon as you start developing a new project or a module in your project. Why?
I’ve spent the last year and a half developing the software part of a bigger product as the only software engineer in a startup that I cofounded. It had many benefits but also made me realize these surprising benefits of having more experienced colleagues around.
It’s to a programmer like a pandemic to a society. It creeps up on you. Slowly. There are some tiny signs of it at first but… who would bother? Then it becomes more and more obvious but to an untrained eye, it still seems ignorable. I mean, it’s not like it’s that bad, right? Life’s a bit harder: it gets harder to focus, things are getting a little bit out of control, few bugs here and there creep into the application. But for sure, that can’t yet justify the effort that would have to be applied to resolving it, can it?