It's all just a matter of positioning it. I need to be *honest* about what it delivers and what the "cost" is (other than money) and ...

...to not sell it as a magic bullet to our problems. Given that management is infatuated with Design Patterns. I think positioning it as...

...TDD oriented Patterns which hail from a Functional Programming background and provide the value of having it make us more efficient.

Because it enables us to have code generators, or more immediately I plan to use it to generate a shit-ton of patterned/scenario specific...

...parameteriz-able test inputs across large swathes of code and have it intelligently equivalence-case chunks out. Is going to be HAWT.

mildly tempted to just do it on the sly, and when people ask why I'm the magic man out performing everyone, after I have evidence.

in some ways it's easier to ask for forgiveness than permission.