upvote
>He did not edit

He edited his reply to me multiple times... which is what made me suspect an edit to the original comment. But whatever, I'm happy to acknowledge his original intent even if he did state it more harshly.

>What we really don't need is paragraphs of someone arguing because their own definitions differ slightly from the OP

This is unnecessary. OP came out with "AUTHOR IS INSANE" even on the most generous of interpretations. Even if we allow for nuance OP is claiming, there is little constructive about his contribution. I feel fine about calling it out.

reply
> He edited his reply to me multiple times...

I got the sense from your reply that some extra clarity would be beneficial.

> This is unnecessary. OP came out with "AUTHOR IS INSANE" even on the most generous of interpretations.

I did not actually call the author insane, I called their decision to explicitly disallow testing insane. It's an insane decision. I am not _literally_ calling the author insane.

reply
> I did not actually call the author insane...

If you think this distinction really matters wrt the point I'm trying to make, then it's time for you and I to bug out conversationally. Sometimes two individuals have such different ways of communicating that the pain of exegesis isn't worth the squeeze. No hard feelings. I'm sure 50% responsibility is at least mine, but it's not going to be worth it for either of us figuring out exactly what.

reply
I'm not really arguing with your point, I'm correcting your incorrect description of what I'm saying.

To argue with your actual point: I don't really care about the overall context, actively disallowing tests in a codebase is a _bad decision_. Look how it worked out for them.

> it's time for you and I to bug out conversationally

Fine with me

reply
deleted
reply