Okay, I'm #Dijkstra on this one.
Stop calling them #software "bugs." Language matters for understanding.
The original bug crawled up in a computer system and got trapped in a 𝗿𝗲𝗹𝗮𝘆, causing the program to error out. Not the programmer's fault, you would say.
Now, when a hobbyist hacker (security researcher) drops a #0day exploit on macOS which has been lying dormant, untested, for 15 years ...
That is a programmer ｅｒｒｏｒ, a systems design ｅｒｒｏｒ. Y'all fucked up, not the moth.
This diagram is by far one of the most instructive I have seen on this topic of software errors.
𝚃𝙷𝙴 𝙴𝚁𝚁𝙾𝚁 𝙰𝚅𝙰𝙻𝙰𝙽𝙲𝙷𝙴
I wish it could gain some currency in the #softwaredevelopment world, and not just DoD systems engineers.
@jcdietrich @uranther It's basically a play on cumulative errors
So every step in the process is bound to have an error, but that error acts as a shelf for further errors in the steps to follow following to rest on. It may be more accurate to call them stairs. The bottom is gonna be much wider because each step protrudes errors of their own
@uranther I get the theory, but am having trouble making 100% sense of the diagram.