This is the long-delayed part 2 of a mini-series looking at what it might take to build the Stack Overflow Tag Engine
I first heard about the Stack Overflow Tag engine of doom when I read about their battle with the .NET Garbage Collector. If you haven't heard of it before I recommend reading the previous links and then this interesting case-study on technical debt.
In Part 1 I looked at some of the more general performance issues that can be learnt from Stack Overflow (the team/product), in Part 2 I’m looking at some of the examples of coding performance lessons.
Typemock & JustMock are 2 commercially available mocking tools that let you achieve something that should be impossible. Unlike all other mocking frameworks, they let you mock sealed classes, static and non-virtual methods, but how do they do this?
There is an update to this post, based on feedback I received.