I find that "great" software usually evolves from simple beginnings. Concocting a spec upfront often leads to inferior solutions. Specs are often driven by market realilies - they are about forming alliances to take on a common enemy. Regards, David www.testdriven.com
----- Original Message ----- From: "J. Merrill" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, February 09, 2004 8:16 AM Subject: Re: [ADVANCED-DOTNET] Microsoft's future plans for Component Services and ORM > If the specification is done via interfaces, and the implementation environment cleanly and easily supports enhancement using newly specified interfaces (as does .NET), how can that be bad? That technique supports an imperfect initial spec much better than does a "reference implementation." =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
