tag:blogger.com,1999:blog-12111089.post6593141749137035752..comments2023-09-23T10:26:27.730-05:00Comments on Mondegreen II: Design Before Writing Requirements?Unknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-12111089.post-51280984012945307562008-12-12T21:15:00.000-06:002008-12-12T21:15:00.000-06:00Great point, Matt. It reminds me of an article I r...Great point, Matt. It reminds me of an article I read, comparing software methodologies that include hiring great developers, to a recipe for winning track races that says:<BR/>1) Meditate night before race<BR/>2) Wear lucky shorts<BR/>3) Eat and hydrate well<BR/>4) Run really, really fast<BR/>5) Win race<BR/><BR/>So yes, if you know the domain well enough to run the business, that is a big advantage. Joel has written about that, too--that is why so many developers want to start a business selling coding widgets and bug-tracking software.mondegreenhttps://www.blogger.com/profile/05577640953398043316noreply@blogger.comtag:blogger.com,1999:blog-12111089.post-13401590158294646382008-11-25T06:22:00.000-06:002008-11-25T06:22:00.000-06:00Interesting article. There is one giant leap that...Interesting article. There is one giant leap that developers have to make for his system and it is step number 1 - Understand the domain. <BR/><BR/>I've been a developer for over 10 years now and I have really never understood the domain of the systems that I have written (at least not to a level that I would comfortable "running the business"). I don't think there are very many developers who stay in the same domain long enough to gain that kind of knowledge.<BR/><BR/>You think the buy in needed for writing requirements is big, just wait until you have to tell management that we need to train the developers for the next 6 months before they can start designing the system.Matt Brownhttps://www.blogger.com/profile/12609553728867141441noreply@blogger.com