Just found this one blogged by Yoyo: Play movie Now that's fun :)

Last friday, Eric Jarvi blogged about the Color scheme used by the code coverage tools of Visual Studio Team System. His post made me think about code coverage another time. Beyond the fact that people tend to misunderstand the green color, there is maybe a more general misunderstanding of code coverage. The code coverage rate can easily be overestimated; Badly covered code is of course also badly tested code, well tested code sure has a good coverage rate. But well covered code is not automatically...

With ASP.NET 2.0, Microsoft ships a session management implementation that look like a nice solution. Sadly, however, it looks like this is not designed for reusability. It seems to be tightly coupled to ASP and not usable outside of web application. We are currently developing a component framework for .NET. Thus we need session management, and we need it for normal client-server applications, too. Sure enough, we do not want to create a new session management implementation if we don't have to....

I have recently had the opportunity to get some experience with pair documenting. While a lot of folks are talking and writing about pair programming, not quite as much is heard about pair writing. Our recent practice made some advantages obvious: The documentation quality rises enormously Many inconsistencies, falsifications and typos can be omitted Documenting is definitely more fun Think about the fun aspect - I don't know any developer that loves writing doc. That's maybe the number one reason...