Timeline for Reconciling contradictory programming advice: get something working and iterate vs. really think it through before coding
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 26, 2015 at 10:26 | comment | added | Mawg | Very deep. I agree. My average professional project is approx 40 -50% up front design work, 10, max 15% coding and the rest for testing. | |
| Oct 11, 2013 at 11:07 | answer | added | user53019 | timeline score: 1 | |
| Oct 11, 2013 at 10:32 | vote | accept | Bernie2436 | ||
| Oct 10, 2013 at 16:14 | answer | added | Evicatos | timeline score: 0 | |
| Oct 10, 2013 at 13:44 | comment | added | fjarri | I do not see how they are contradictory. I first think a lot, and then make something working quickly. | |
| Oct 10, 2013 at 7:41 | review | Close votes | |||
| Oct 12, 2013 at 15:28 | |||||
| Oct 10, 2013 at 7:24 | comment | added | gnat | possible duplicate of Prototyping vs. Clean Code at the early stages. See also: Develop fast and buggy, then correct errors or be slow, careful for each line of code? | |
| Oct 10, 2013 at 6:17 | history | tweeted | twitter.com/#!/StackProgrammer/status/388186465551003648 | ||
| Oct 10, 2013 at 5:58 | comment | added | Thiago Silva | Somewhat related is Kent Beck's essay on "Make it run, then make it right VS. Make it right, then make it run": facebook.com/notes/kent-beck/runright-and-vice-versa/… | |
| Oct 10, 2013 at 5:46 | answer | added | DXM | timeline score: 20 | |
| Oct 10, 2013 at 5:38 | comment | added | Matt D | Do both, at the same time. Iterate, document, iterate, document, iterate and once you've got a clear plan that works. Build it :D | |
| Oct 10, 2013 at 5:37 | answer | added | Jane Panda | timeline score: 1 | |
| Oct 10, 2013 at 5:32 | answer | added | Robert Harvey | timeline score: 5 | |
| Oct 10, 2013 at 5:19 | history | asked | Bernie2436 | CC BY-SA 3.0 |