Rise of the Shaman Programmer
blog.sourcerer.io
blog.sourcerer.io
Sometimes I have been new to a system and had to fix a problem in a hurry and had an incomplete understanding.
Sometimes six months later I understand what really went wrong.
Years ago there was a bug in the Linux 2.4 kernel that I understood so far as "sometimes there is a null pointer in this particular place" and was able to make a patch that mitigated the effect of the null pointer. I never understood why there was a null pointer in that place and it wasn't worth doing because Linux 2.4 was hopelessly broken.
The potential(actual?) problem with this is it can necessitate crippling specialization. Who maintains an overview? Who directs goals and avoids harmful drift is the overall direction?
Maintaining the overview is perfectly practical, but who does it, what is their motivation, and how is it legitimized?