Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

13
  • 1
    Are you committing the commented code to version control? Commented Aug 20, 2018 at 21:33
  • 4
    If the commented code is not visible in the master branch after you merge back (and you can do that) who will be hurt?. If you feel the need to commit before getting rid of the commented-out code that hints that you might be taking too big steps, but that is a different matter. Commented Aug 20, 2018 at 22:20
  • 6
    It is true that if you cmoment code, you can easily undone it by uncomment it, however if you have change ssome stuff in quite some files and need to go back, you're quite screwed without version control. So "start using source control" should be way above your priority than "not commenting code" :) Commented Aug 21, 2018 at 14:45
  • 3
    Wait, you wrote you have a code base which is large enough that portions of it sometimes "need to be adapted to major architectural changes" - and you are CURRENTLY NOT USING VERSION CONTROL? WTF - seriously? You are joking, aren't you? If that is really true, you have larger problems than the question if your way of working with outcommented code is ok or not. Commented Aug 21, 2018 at 18:14
  • 2
    @DocSalvager You too, like the OP, probably would benefit from a real version control system. Commented Mar 25, 2019 at 23:45