I know GGP wrote about "computer scientists", but I've seen similar things spoken (even here) about software engineers - that they have "binary thinking", they "reason in ones and zeros", etc. Which infuriates me to no end, because it's hard for me to think of another domain except hard sciences that forces you to think quantitatively, in numbers and orders and probabilities. Excelling in software requires the opposite of "black and white thinking".
I think the stereotype is that Computer Scientists are black and white thinkers, and that's true for some. But a senior software engineer should be skilled at thinking with nuance and considering uncertainties, biases, etc.
Your comment is an example of the fallacy fallacy.
> since the fallacy fallacy is itself a fallacy, it cannot be used to label an argument's conclusion as false without committing it in the process. "You have used the fallacy fallacy, therefore you are wrong"
But unless you will argue that "logical thinking" is the correct term in this case I will submit that you have delivered a faulty argument yourself (since you invalidate my whole comment and not just the relevant part). Not sure which logical fallacy that represents though ...
Furthermore, quantitative thinking is itself logic.
Therefore, your lawyer friend likely has never thought about what logic is, or what a scientist does, and how physical reality with experiments is a harsh and unforgiving master, and therefore believes that everything is what he does – i.e. rhetoric.