My daughter just went to Japan, where she was invited to a Zen temple among other things. I asked her immediately if she had seen “the error”. She was puzzled as I said it, and I had to explain myself. You see, every single Zen temple contains one “error”. Either a column is raised upside down, a window is skewed, or some other part of the temple is erroneously erected somehow. This fact has a lot of philosophical reasoning behind it. However, I like to think that the error gives us room for improvement. Something that is perfect can never be improved upon. But if there is an error, a random mutation so to speak, then we can improve upon it.
Humans are the same. Unless they are willing to admit that there is something wrong with them, they can never improve themselves. Hence, a perfect being, will stagnate, and never be able to develop. Articles are the same too. Frameworks and software libraries are the same, etc, etc, etc. No matter how perfect we create something, there will always remain one “error”. Only when we are willing to acknowledge this, we can improve upon our ideas and code, and such evolve ourselves as human beings.
In my upcoming MSDN article, that is scheduled for being published 1st of June 2019, there is also an “error”. Can you spot it? Are you a better developer than me? Can you improve upon it, such that it becomes better? At least two developers have so far improved upon the library or “starter kit” that I describe in the article. One colleague of mine, in addition to James behind the .Net Core podcast.
Can you spot the error in my code/article …?
Good luck 😉