Peter Arrenbrecht's Blog

I googled for "Documentation Driven Development" and came up with a number of links (why the heck did I not do this sooner?). SpliceIt seem to be doing it, but don't cite tests. There is no mention of integration with use-case-level tests. Vincent Massol had the experience when writing books about frameworks - always improved the underlying code. The message is: you have to be serious about writing good docs. Otherwise the effect is lost. Korby Parnell just thinks about it, but some comments point to people with experience doing it. IEEE has an article about DDD for real time systems. Also seems to take it as far as code-generation. I haven't read it. Miguel dos Santos has little to add, but there is a nice comment by someone called "Tania" about applying the idea of documenting the "why" more generally. In the groups , I got: Ilja Preuss 's take is a bit too limited for me. In my experience, good DDD docs focus on tasks, not classes and

I've recently read Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries by two lead architects on the .NET Framework. A mixed experience, I have to say. The book does offer good advice, but somehow, hardly anything seemed truly new. Maybe that is because I've already read Josh Bloch's Effective Java , but, I suspect, mostly because I have accumulated a fair bit of framework design experience myself (and, like them, learned from many mistakes). It was quite eerie at times, as it felt like they'd written down my own thoughts. So, it has still been a rewarding read, seeing as this eminent source confirmed a lot of my design creeds. A lot in the book is quite .NET specific, though I can hardly blame the book for that. And while it is tedious reading to someone looking for higher-level insights, I still wholeheartedly agree with the authors that consistency down to detailed naming conventions matters a lot in framework design. The most g