Tim Chambers

@dkubb Absolutely - having the type in the report would much more quickly allow me to recognize it than having to back into what is it trying to tell me....

This is probably OT but one of the time-wasters I find is when I discover a sequence of unkilled mutations that are BIZARRELY and obviously NON-EXECUTABLE which eventually I trace...

@dkubb I like the reek documentation as well - although it is somewhat _buried_. I do it though. That kind of documentation should be near the code, but it also...

I spoke elsewhere of the friction to mutation testing, and things such as the above (requiring experience to deduce the action to take, and to recognize patterns quickly), are where...

@mbj your continued openness _and willingness_ to entertain these discussions given your declining interest in Ruby is from where I sit remarkable. I tend to step back and look at...

@dkubb I inferred that would be a logical discussion given the sentiments around Ruby. I too have dabbled with Haskell. You can probably see that my viewpoint is around what...

I wanted to add that you can include me as a person with "mouths to feed and arms pulled in many directions". Why do I use this tool? Because when...

My process of code improvement involves the following: - Detect a code issue or smell (either by observation or bug-driven) - See if it is a single case or a...

@dkubb I see the tagging of a type of mutation, and the classification of a tag or group of tags as intertwined. While broader classifications may be sufficient to the...

Seems appropriate test for next version of Ruby as well.