2,137 karma · joined September 11, 2016
As an example, suppose I have a static method that takes in an object and returns a result based on the state of that object. Now I have conditional logic in the unit under test that has a dependency on the result of that static method. In my unit test, I don't want to go to the trouble of creating the state of the object to force the delegate call to return a certain result that determines the execution flow, I want to just force that call to return the result I need.
In fact, dependence on mocking frameworks is a huge code smell because it covers over the common practice of not coding to an interface. If you want to expose poor design in a code base, remove the mocking decencies and see how hard it is to rewrite the tests.
You mean like string concatenation? Come on man. As far as evolution goes, that’s what semantic versioning is for.
Can the HTTP spec just add a CALL verb already?
Alex Berenson did.
This shouldn’t make a difference because in theory they would be doing 2x more work which is essentially cutting their salary in half. I realize that the dev team being twice as efficient doesn’t necessarily double the unit’s revenue but it’s some multiple.
By this logic it's equally valid to question the motivation of someone hand waving the questions away as "copy pasta" rather than just answering them. The Socratic method is a perfectly valid way to further an argument.