Timeline for What should take precedence: YAGNI or Good Design?
Current License: CC BY-SA 3.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 17, 2011 at 15:32 | comment | added | Seth Spearman | Great answer. He is facing an uphill battle. Getting it done will be difficult if there is no management buy in. And you are right that question is premature and does not address the real problem. | |
Sep 16, 2011 at 17:59 | comment | added | Incognito | @sehe that's not his decision :p. | |
Sep 16, 2011 at 16:56 | comment | added | sehe | Erm..... I think the driving goal would be 'you want to have a good, valuable product'? | |
Sep 16, 2011 at 14:59 | comment | added | Incognito | That's fine, it's going to be a bit slower, but you need to speak to their worries then. Explain that this YAGNI/Useless-code problem is wasting time, suggest the roadmap, give him a roadmap, explain it will make work faster. When he's bought in, come in with the problems that poor standards have to the speed of development, suggest the better ones. They want the project done, they just don't know how to manage the thing, you'll either need to replace him or baby him... or quit. | |
Sep 16, 2011 at 14:56 | comment | added | Wayne Molina | We don't have one, sadly. The Development Manager either is more concerned about getting things done fast than about standards/quality, or would make the standard practices like using raw DataSets everywhere returned directly from classes, VB6 style coding and everything in code-behind with duplicate logic copied and pasted all over. | |
Sep 16, 2011 at 14:54 | history | edited | Incognito | CC BY-SA 3.0 |
added 158 characters in body
|
Sep 16, 2011 at 14:49 | history | answered | Incognito | CC BY-SA 3.0 |