Glenn Block

Sponsors

The Lounge

News

  • View Glenn Block's profile on LinkedIn

    Me

Advertisement

Images in this post missing? We recently lost them in a site migration. We're working to restore these as you read this. Should you need an image in an emergency, please contact us at imagehelp@codebetter.com
On Oxite

Lots of posts on Oxite. I won't reiterate what they've said, though Rob Conery has done a great analysis here. I'll just share my own quick brutally honest thoughts. There is no excuse for this. There are tons of folks both internal to Microsoft or external that can help people who want to learn good practices for developing software. The fact that the MVC team was not even consulted by the Oxite guys is literally stunning. Not to mention all the other folks we have internally like patterns & practices, folks in our evangelism team, and TDD and Agile email discussion groups which have hundreds of folks. I really wish the "Look what we can do" mentality would become a thing of the past.

As others have said, I do applaud the team for their efforts at delivering Oxite as an application that the community can learn from. I think however that they should have used a different approach on how they delivered it.

My parting thought before I head to bed, if you want to develop something that will be useful to the community as guidance, don't built it behind closed doors, build it WITH the community. Don't tell them it's good guidance, let THEM tell you.

As the great Forest Gump once said "And that's all I have to say about that."


Posted 12-19-2008 2:46 AM by Glenn Block
Filed under:

[Advertisement]

Comments

DotNetKicks.com wrote On Oxite
on 12-19-2008 6:58 AM

You've been kicked (a good thing) - Trackback from DotNetKicks.com

karl wrote re: On Oxite
on 12-19-2008 8:40 AM

I know you can't speak directly for this, but why hasn't this been pulled yet? Remove it, fix it, re-release it. Seems like they are just waiting it out until we stop bitching about it (which is bound to be pretty soon). EVERYONE admits the code is poor, what's the harm in removing it and saying "we're gonna make this better, stay tuned" and simply admitting a mistake was made?

Dew Drop - December 19, 2008 | Alvin Ashcraft's Morning Dew wrote Dew Drop - December 19, 2008 | Alvin Ashcraft's Morning Dew
on 12-19-2008 10:40 AM

Pingback from  Dew Drop - December 19, 2008 | Alvin Ashcraft's Morning Dew

robconery wrote re: On Oxite
on 12-19-2008 1:17 PM

@karl I've been on the team non-stop to pull it from Codeplex and up to now they've decided not to. The main issue is the holidays - people are just gone. I'm still working on it... I'm trying :).

karl wrote re: On Oxite
on 12-19-2008 1:30 PM

@rob, thx for the update.

Casey Charlton - Insane World wrote Oxite - An Example of How Not To Write MVC Applications
on 12-19-2008 1:34 PM

You may have missed the release of Oxite recently, and some of the hype and comments around it. Having

Community Blogs wrote Oxite - An Example of How Not To Write MVC Applications
on 12-19-2008 2:45 PM

You may have missed the release of Oxite recently, and some of the hype and comments around it. Having

Coderies | taggle.org wrote Coderies | taggle.org
on 12-23-2008 3:30 AM

Pingback from  Coderies | taggle.org

Kent's thoughts wrote An interesting development: Oxite
on 12-24-2008 7:22 PM

<p>It used to be that a sample from Microsoft was guidance that would be copied into thousands of programs. Now, not so much.</p> ...

Oxite: Some Thoughts at Mark Needham wrote Oxite: Some Thoughts at Mark Needham
on 12-30-2008 10:29 AM

Pingback from  Oxite: Some Thoughts at Mark Needham

Add a Comment

(required)  
(optional)
(required)  
Remember Me?