An outlet for my obsession with technology
Kobe: My response to the response.
Let me start off by saying I am so happy with the “New” Microsoft. An engaged Microsoft, an open Microsoft. So to the Kobe team I say “Welcome to the real world”.
There are enough people writing about the amazingly horrible code. I’m upset with the response from the team. The response, at first glance, seems to acknowledge there is a problem and that they will fix the Kobe code.
Then I read it again…
This post is defensive and response laden with manager speak for “fuck off”. More so, they don’t even acknowledge a problem with the Kobe code!
The sample app is not a "reference application" in the context of code completeness. A "sample app" and a "reference app" are quite different in the context of code completeness, and we do not claim Kobe to be a reference app in this context.
Oh!, I am so sorry, I thought it was a "reference application" now that I know its a "sample app" all is right in the world. FAIL. What is that code a sample of anyway? After looking at the code and reading the numerous community responses its quite easy for me to say.
The Kobe code is a sample of how NOT to do ASP.NET MVC
If we now have the same understanding of the word sample; then I agree; Kobe is a sample.
Now, I am aware that Rob and the Scott are stepping in to clean this up…Oxite déjà-vu. But I need to make one final comment about the teams acknowledgement of the problems in the code.
We will review all sumitted feedback and take action to address items within the context of the intended scope & goals of the Kobe project.
That is so so so far from an acknowledgement. This is an acknowledgement.
No related posts.
| Print article | This entry was posted by Eric Polerecky on April 16, 2009 at 10:23 pm, and is filed under Kobe, Microsoft, development, mvc. Follow any responses to this post through RSS 2.0. You can leave a response or trackback from your own site. |