throw new Exception("If code is a developer's child, this counts as child abuse.");
One great thing about working with proprietary code is that only a select few will ever see the code. If we ever open source the project, we have a lot to clean up before releasing it, some very embarrassing stuff in there.
@VarunDotCuDotCc I'm afraid the whole discussion misses the point. Your question does not show any prior research, which makes it an unsuitable question for the site regardless of what your motivation for asking it is. Personally, I couldn't care less if you were trying to write malware. Also, I don't have any reason to doubt that you are not trying to write malware.
Also please note that I'm not saying that you haven't done any research (I have no way of knowing that), just that you don't show us that research in your question.
That said, if you had shown prior research then people would had probably been more receptive. Prior research & evident effort is the easiest way of showing others that you are genuinely interested in the subject matter.
Does anyone have any suggestions about how to estimate how long it would take to comment and reorganize the code of an entire project?
I just started doing contract work for a company along with another programmer: he's fixing bugs and I'm reorganizing the code. I'd like to make an estimate of h...
@CodesInChaos unlikely fit, at least without substantial editing: "Does anyone have any suggestions... Any suggestions would be more than welcome." is a huge red flag
comments rather indicate in current for it's NARQ...
What do you mean "comment the code" - are there legal reasons for it? Or you doing it for personal entertainment? In general code is better when you don't need any comments to read it... Or you mean write architecture overview? Or maybe you mean <summary> comments for creating documentation? (or Ctrl+K+C to comment out all code - no time at all :) ) — Alexei Levenkov3 hours ago
The Whiteboard
The Whiteboard