Baking requirements - Developing with raw ingredients is waste

codebetter.com — have learned an important lesson from my combined experiences at all the places I've worked. That is: raw requirements cause waste. A term I've used (and have heard others use) is that requirements are either "baked" or "not baked". For a development team to plan an iteration, or a scope of delivery, the requirements need to be baked. If we pull the development team into a planning session, we ensure the requirements are fully baked before the meeting. Developers will be asking specific questions about the details of the requirements, and answers need to be readily available. read more...

add a comment | category: ASP.NET | Views: 2

Developer Poetry Series: SharePoint How Sad Are We

codezest.com — SharePoint SharePoint how sad are we Your marketing promise me everything under the sun as far as my eyes can see A hidden cost, a nasty toss, a huge 5 year loss Go hire a whole team, 3rd party pugs-ings, which ends up to very high cost read more...

add a comment | category: ASP.NET | Views: 0

Using TDD to create a new Feature for DimeCasts.net

dimecasts.net — A pairing session where Kyle and Derik use TDD to create a new Feature for DimeCasts.net read more...

add a comment | category: C# | Views: 87

Update on Silverlight 2 - and a glimpse of Silverlight 3

published 5 days, 7 hours ago, submitted by simonech 5 days, 12 hours ago

weblogs.asp.net — ScottGu unveils the plans for Silverlight 3, shipping next year read more...

1 comment | category: Silverlight | Views: 311

Testing is hard but debugging just sucks A$$

published 5 days, 1 hour ago, submitted by Jemm 7 days, 10 hours ago

devlicio.us — "At the users group I asked the question to the group 'who creates automated tests as part of their daily development cycle?'. After I asked this question I followed it up with, and if you don't WHY, WHY, WHY, WHY...... Below are some of the answers I received (btw, not the first time I have heard these reasons)." read more...

1 comment | category: Unit Testing | Views: 330

Creating an ItemDataBound Event Delegate for a Nested Repeater

codezest.com — Today I needed to create a nested grid using repeaters. Pretty common but always a pain in the ass with all Microsoft controls. I needed to nest my repeaters just like you’d nest any other control like the DataGrid or GridView. The issue came up for me when I wanted to create a delegate for my nested repeater (repeater inside my parent). Since a nested control within a control (the nested repeater in this case) is not available at the page level, Intellisense or the compiler will not know that it exists. Because it’s nested inside a parent, it becomes pat of that parent’s collection of objects. read more...

add a comment | category: ASP.NET | Views: 8

Partial Mocks with the StructureMap AutoMocker

devlicio.us — If you have not checked out the new AutoMocking Container that is part of StructureMap 2.5 I would highly suggest you do, it rocks. I thought I would show how simple it is to create a PartialMock on the Class under Test (CUT) when using the RhinoAutoMocker. Our Class we want to mock read more...

add a comment | category: Unit Testing | Views: 5

The simplicity that is the Asp.Net MVC

submitted by wisemx 17 days, 9 hours ago

devlicio.us — Today I was browsing my list of RSS feeds and I stumbled upon a posting that showed some Asp.Net code. This code was nothing out of the ordinary, it was simply someone building a table with a repeater. . . read more...

add a comment | category: ASP.NET | Views: 12