4 ms·
Leaving dead code in is not good practice?? I would love more explanation here because that sounds like crazy talk to me.
by rkuykendall-com 3y ago
Leaving dead code in is not good practice?? I would love more explanation here because that sounds like crazy talk to me.
- gumby 3y agoYou'll have to ask the author of the article.
- fphhotchips 3y agoYour original comment is somewhat unclear. Are you advocating for leaving old code in because the system works and it's more stable that way, or taking it out to force the necessary refactoring steps and understanding that will bring?
- gumby 3y agoI'm sorry I wasn't clear: I re-read my comment and couldn't think of a decent edit. It was the author whom I was quoting as saying "why would someone have old code lying around." It seems obvious why that's a good idea and it seems commenters in this thread (including you) agree with me and not the author. Sorry again if I was unclear.
- deleted 3y ago[deleted]
- lionkor 3y agoIt may not be obvious that it's dead code - in a lot of popular interpreted languages, it's impossible to tell if a given function can be called or not
- OtherShrezzing 3y agoChesterton's Fence states that you shouldn't make a change until you understand something's current state. Removing code because it's dead is folly, if you don't understand 1) why it's there, and 2) why nobody else removed it yet.
- meiraleal 3y agoAs this is a postmortem, it was proven dead code. There is nothing in the text that mentions that they didn't know what the code did (which then wouldn't be dead code).