Timeline for How to stop gold-plating and just be content to release working developments [closed]
Current License: CC BY-SA 3.0
14 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Dec 27, 2022 at 21:31 | comment | added | Thorbjørn Ravn Andersen | @AndyBowskill Wait with cutting out the re-use API until you have had at least three independent projects using it. You do not have enough information before then. Test Driven Development helps making the code clean. | |
Oct 14, 2012 at 18:11 | vote | accept | Andy Bowskill | ||
Oct 11, 2012 at 21:47 | history | closed |
Jim G. user8 ChrisF♦ |
not a real question | |
Oct 11, 2012 at 5:16 | history | edited | DeveloperDon |
edited tags
|
|
Oct 7, 2012 at 1:08 | answer | added | duanev | timeline score: 8 | |
Oct 7, 2012 at 0:45 | review | Close votes | |||
Oct 11, 2012 at 21:47 | |||||
Oct 7, 2012 at 0:29 | answer | added | DeveloperDon | timeline score: 15 | |
Oct 6, 2012 at 21:01 | history | tweeted | twitter.com/#!/StackProgrammer/status/254687848031207424 | ||
Oct 6, 2012 at 17:12 | comment | added | Andy Bowskill | By gold-plating I mean striving to perfect a design (perhaps to try and encourage its re-use in future) that already fulfils its requirements, not necessarily adding new functionality. | |
Oct 6, 2012 at 17:02 | answer | added | David Hammen | timeline score: 27 | |
Oct 6, 2012 at 16:05 | comment | added | Thomas Owens♦ | Define gold-plating. To me, gold plating is adding unnecessary things (in Lean terms, producing waste such as unnecessary functionality, too much documentation or non-value adding documentation). It seems like you aren't adding things that aren't needed, but are just spending time refactoring rather than pulling down new work products. | |
Oct 6, 2012 at 15:35 | answer | added | Bernard | timeline score: 26 | |
Oct 6, 2012 at 15:20 | review | First posts | |||
Oct 10, 2012 at 15:39 | |||||
Oct 6, 2012 at 15:17 | history | asked | Andy Bowskill | CC BY-SA 3.0 |