* * * * *

            If a bug is found and no one cares, is it still a bug?

I've been enjoying reading The Codeless Code [1] over the past month. It's
been helping me to accept the process [2], but I'm not entirely sure what to
make of “The Codeless Code: Case 219 Nothing Really Matters [3],” especially
in the light of a recent event at work [4] dealing with undefined behavior.
To place the story in context, I'm the senior monk Wangohan, my team leader
is the junior monk, yet has the attitude of master Kaimu.

The story is to inform us that since the language and and the tooling around
the language didn't warn of the issues, then the junior monk was right in
ignoring them, and Wangohan was wrong for chastising the junior monk. But in
my case, it was undefined behavior—tools might not catch it [5]! And I'm
already weary of my team leader's dependence upon testing [6], using it (in
my opinion) as a crutch [7].

I have to meditate on this.

[1] http://thecodelesscode.com/
[2] gopher://gopher.conman.org/0Phlog:2022/02/11.1
[3] http://thecodelesscode.com/case/219
[4] gopher://gopher.conman.org/0Phlog:2022/01/07.1
[5] https://brilliant.org/wiki/halting-problem/
[6] gopher://gopher.conman.org/0Phlog:2021/06/07.3
[7] gopher://gopher.conman.org/0Phlog:2009/11/03.1

Email author at [email protected]

You are viewing proxied material from gopher.conman.org. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.