https://medium.com/@sreeramvenkitesh/errors-the-ultimate-architect-of-everything-7891575f7f8d

I was programming the other day, and quite like every other day, stumbled into some errors. I tried to fix them and run it again, only to realize that I have run into some other errors now. I was feeling frustrated and closed my laptop. After starting work on this project around 3 months ago, there is this little exercise that I do whenever I jump into an endless loop of compilation mistakes and other frequent crashes — I look back at all that I have done up until now. There were plenty of instances where I had thought that I won’t be able to crack this one, and would have to give it up for the other, more experienced members of the team, but finally ended up solving them myself. There has been no hurdle which I faced, that I couldn’t solve by myself. Some of them took a day, some other took weeks, but I had resolved every one of them in the end.

No matter what the platform, whatever language or framework, there is one thing that is common in every software stack — errors. Errors are the stones with which we build software. Well, we don’t literally build stuff with code full of errors, but you get the point. Every new feature that you envision in your mind is born into this world, covered with errors in the first code you write. Just like a new born baby, you have to clean it up with help from Stack Overflow, the mid-wife.