9 events
when toggle format what by license comment
Dec 16, 2019 at 18:42 history edited KeithS CC BY-SA 4.0
added 15 characters in body
Oct 2, 2014 at 20:44 history edited KeithS CC BY-SA 3.0
added 4 characters in body
Nov 20, 2012 at 18:01 comment added Songo +1 I think I'll name ur rule: "Practical refactoring" :)
Sep 21, 2011 at 3:13 comment added 13ren @KeithS: It seems John Carmack did something similar: "source code of Quake II ... unify Quake 1, Quake World and QuakeGL into one beautiful code architecture." fabiensanglard.net/quake2/index.php
Sep 20, 2011 at 20:31 comment added Richard Neil Ilagan On the fourth pass, make it AWESOME.
Sep 19, 2011 at 23:15 comment added 13ren Yes. When I used to design-for-reuse/extension upfront, I'd find that when I wanted to reuse or extend it, it would be in a different way than I had anticipated. Prediction is hard, especially concerning the future. So I support your 3-strikes rule - by that time, you have a reasonable idea of how it will be reused/extended. NB: an exception is if you already know how it will be (e.g. from previous projects, domain knowledge, or already specified).
Sep 18, 2011 at 10:05 comment added Filip Dupanović I second the awesomeness.
Sep 16, 2011 at 15:38 history edited KeithS CC BY-SA 3.0
added 375 characters in body
Sep 16, 2011 at 15:31 history answered KeithS CC BY-SA 3.0