Timeline for Good design: How much hackyness is acceptable?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 25, 2011 at 7:04 | comment | added | Winston Ewert | @Kevin, well... yes having the right foundation from the beginning is best. But the situation here is where you've discovered midway into the project that the right foundation has not been laid. Do you rip out the foundation right away to replace it? It clear that you didn't make the correct design decision originally. What makes you think you are going to make the correct decisions now? That's why I think you should wait until you get a better picture of the situation, not the first moment that a hack is necessary. | |
| Aug 10, 2011 at 15:13 | comment | added | Kevin | That works as long as you're the sole contributor to a code base. What if you don't trust the 3rd (random) person to do the right thing? Is it not better to lay the right foundation from the beginning so that other less conscientious developers are not tempted down the line? | |
| Aug 10, 2011 at 7:07 | comment | added | Joris Timmermans | +1 for the golden rule of refactoring/reuse. The first time, just do it. The second time you write the same code, cringe, but do it anyway. The third time you do it, refactor it into a separate function. | |
| Aug 9, 2011 at 22:33 | history | answered | Winston Ewert | CC BY-SA 3.0 |