Skip to main content
13 events
when toggle format what by license comment
Jul 25, 2016 at 21:59 audit First posts
Jul 25, 2016 at 22:00
Jul 25, 2016 at 7:50 audit First posts
Jul 25, 2016 at 7:50
S Jun 30, 2016 at 11:12 history suggested grooveplex CC BY-SA 3.0
improved code spelling
Jun 30, 2016 at 11:11 review Suggested edits
S Jun 30, 2016 at 11:12
Jun 29, 2016 at 17:17 comment added Eric Lippert @krillgar: I write some "new code", I check it in, I go get lunch and when I get back, my "new code" has magically turned into "legacy code". How'd that happen? :)
Jun 29, 2016 at 15:57 comment added krillgar Yeah, I know. Sorry for being ambiguous. If the code is that fragile, it would be unmaintainable as soon as it gets checked in.
Jun 29, 2016 at 15:43 comment added corsiKa @krillgar It umm... doesn't... that's just a number I plucked off the top of my head to represent a period of time between when you set down the code and have to pick it up again... so, yeah...
Jun 29, 2016 at 11:59 comment added krillgar @corsiKa Why wait 6 months for it to be unmaintainable?
Jun 29, 2016 at 9:23 comment added corsiKa I'd also add that if the code can't be reviewed right now, it can't be maintained 6 months from now.....
Jun 29, 2016 at 9:22 comment added corsiKa Indeed, imagine if 'complex' was replaced with 'long' or 'poorly styled' or 'poorly documented' or any other negative feature we'd say "That's not a good reason to review - let's fix those problems so it is reviewable!" and this is no different.
Jun 28, 2016 at 20:28 history edited Christophe CC BY-SA 3.0
added 249 characters in body
Jun 28, 2016 at 20:12 history edited Christophe CC BY-SA 3.0
added 157 characters in body
Jun 28, 2016 at 20:01 history answered Christophe CC BY-SA 3.0