Timeline for What is a good design model for my new class?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 14, 2012 at 0:34 | vote | accept | user66662 | ||
| Oct 14, 2012 at 0:34 | comment | added | user66662 | This thread as a whole has been very helpful, but indeed the first paragraph here is very true. Mostly what I have learned since implementing these directions is that the code will evolve - rapidly. Although I started out with 1 theory of a direction, I went through several structures, tweaking here and there, before I came up with something that works well, feels right, and, has little to do with the original blueprint I had down on paper. Something did indeed emerge. Maybe a topic for another post, but how does a programmer learn to best deal with code evolution? Is this 'refactoring?' | |
| Oct 2, 2012 at 6:45 | history | edited | Steven A. Lowe | CC BY-SA 3.0 | typo |
| Oct 2, 2012 at 1:29 | history | answered | Steven A. Lowe | CC BY-SA 3.0 |