Wandering into a slightly different sub-area of CS is fascinating. We seemingly have all the same problems and techniques but everything is called something different. As a security person with an engineering degree who has previously been a software engineer, for instance, I assumed “field bugs” had to do with improper input handling. I also couldn’t tell you what a mutant is or why anyone would want to kill one, before yesterday?! That doesn’t mean calling these things emergent behaviour or equivalent test cases is any more or less valid. It just makes it hard for us to talk to one another 🤔

@kaoudis my problems with physics started with the 3 different notations of derivation...

@buherator if we could stop making up more ways to describe the same old crap that’d be dandy

@kaoudis Ironically the whole point of this vocabulary is to make communication with other professionals more efficient. Is tech linguist the next big career move?

@kaoudis Many years ago, while at a party and a few drinks in, I tried to tell some guy about what I was working on. He was a mechanical engineer or something. I kept trying to use the word "error", in the sense of "program that transitions to an error state", and the guy kept being like, "*how much* error?", in the sense of "margin of error", and I kept being like "just an error!!" and utterly failed to communicate anything at all.

@lindsey oh my goodness 😆