My colleague Joe Walnes pointed me to a fascinatingly simple tool developed by our colleague Chris Stevenson. TextDox (part of AgileDox) is a tool to automatically generate documentation from JUnit test cases. Sounds ridiculous, but then that’s what Wardish ideas are like. via [Martin Fowler’s Bliki]  

Go To The Source Luke

< blockquote dir=”ltr” style=”MARGIN-RIGHT: 0px”> The standard answer to the people wanting to really understand how .NET works is to go to the source, i.e. the Rotor source code. Now, there is one step better: these great presentations from the Rotor Conference (scroll to the bottom) from people like Peter, and <a title=”” href=””” xmlns=””>Jason […]

Future Visions

Eric Kidd has written an eloquent post dismaying of the future for small ISVs. He sees the future dominated by two forces: Microsoft and Open Source. He laments for a third way, where “30 person companies” can be significant. He has some good points: Microsoft and Open Source are going to be around and they are […]

Whence keycodes?

How do people make license-restricted software? You know, 30-day trial edition, but when you enter your name, company, and keycode, the software says “Yeah, that’s fine.” Do people roll their own (and, if so, are there “best practices”), or is this a commercial market in which there are a few players (a la installers)?