Both Ian Cooper and Scott Bellware wrote excellent posts comparing dynamic and static languages, and how type mocking is dangerous when your using a static language (e.g. C#, VB.NET). Scott said: "Type mocking might save your bacon when you have made poor design decisions along the way..." I couldn't agree more! Ian also talked about how dynamic languages leverage Duck Typing to overcome this danger.
Take a look at my friend's Duck Typing library - it's made to be used within a static language. It too can "save your bacon" when you need to isolate legacy, tightly coupled code that you need to change and test.
a79f2e8c-ad15-4bb4-be12-2f9fd9274174|0|.0
A friend of mine, David Meyer, recently released the latest version of his Duck Typing library for public consumption. It's written in C# and the source is available. I'm looking forward to using it when working with "legacy code" to break dependencies. Anyways, check it out and let him know what you think...
1101fcf0-0193-43d6-a6b0-5b6f407cc3e9|0|.0