﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Haacked commented on Kobe – When the documentation is the only delivery that matters</title><description>I wrote a follow-up comment to my post that talks about this a bit and asks the question of how we can make it better.
  
  
[haacked.com/.../code-sample-taxonomy.aspx](http://haacked.com/archive/2009/04/16/code-sample-taxonomy.aspx)  
  
The review was informal. They showed us some slides of the high-level architecture. They told me about their data access and they were using the Repository pattern.
  
  
Then we looked at an action, a view, etc... Some of it was clean, some of it wasn't. I gave them some feedback, and we went our merry ways.
  
  
What I didn't do was go through a line-by-line code review, nor did I explore the source. Obviously now, I wish I had. But at the time, I was pressed for time and their questions were really focused on how to do things the MVC way. I warned them about Oxite, which they were aware of, and went on my way.
  
  
If you don't mind, please comment on my post if you have suggestions how we should handle this better in the future.
</description><link>http://ayende.com/3951/kobe-when-the-documentation-is-the-only-delivery-that-matters#comment3</link><guid>http://ayende.com/3951/kobe-when-the-documentation-is-the-only-delivery-that-matters#comment3</guid><pubDate>Fri, 17 Apr 2009 16:36:00 GMT</pubDate></item><item><title>josh commented on Kobe – When the documentation is the only delivery that matters</title><description>I'm gonna guess haack's high level review meant looking at the documentation and some developer overview of the app concepts without much discussion of the code.
</description><link>http://ayende.com/3951/kobe-when-the-documentation-is-the-only-delivery-that-matters#comment2</link><guid>http://ayende.com/3951/kobe-when-the-documentation-is-the-only-delivery-that-matters#comment2</guid><pubDate>Fri, 17 Apr 2009 15:21:26 GMT</pubDate></item><item><title>Kyle Szklenski commented on Kobe – When the documentation is the only delivery that matters</title><description>What exactly is a "high-level review"? A discussion on the documentation? A look at the general design of the application, maybe in some form of UML or other design language? I can't imagine it's the latter - any repository interface that has something like 60 functions should automatically send up a warning signal. Hell, any interface at all that has 60 functions ought to cause the person who wrote it to be fired.
</description><link>http://ayende.com/3951/kobe-when-the-documentation-is-the-only-delivery-that-matters#comment1</link><guid>http://ayende.com/3951/kobe-when-the-documentation-is-the-only-delivery-that-matters#comment1</guid><pubDate>Fri, 17 Apr 2009 13:14:08 GMT</pubDate></item></channel></rss>