Hi Kurt. Thank you for your comment.
Do I think the code tells “the truth” about the software’s behavior? Sure. Good enough to instruct a machine to execute the behavior based on it. That’s what I tried to focus on in the article.
Do I think the code tells “the whole truth”? Definitely not. The earth revolves around the sun. Gloves keep my fingers warm in winter.
The code alone is bad at telling the “why”: why was a feature implemented? Why was it implemented like it is? Some people say the why is more important than the “what”, the domain of the code. I can empathise with that, as the consequences of getting the “why” wrong may be even more dramatic than getting the “what” wrong. (Still, it’s comparing apples with oranges).
So, are we in the same “crowd” now? I’ll leave that up to you. I’d be glad to.
P.S. Fun fact: I am employed by the same company for 10 years now. Just sayin’. :-)