comments from ms-dos 2.0 source
-
Quote:
REV 1.20 ; 06/09/82 Prints "directory" after directories ; 06/13/82 MKDIR, CHDIR, PWD, RMDIR added ; REV 1.50 ; Some code for new 2.0 DOS, sort of HACKey. Not enough time to ; do it right.
In the following years, all us devs stopped adding those kind of comments, because they were redundant. All code is HACKey. There is never time to do it right. :rolleyes: From MS-DOS/COMMAND.ASM at master · historicalsource/MS-DOS · GitHub[^]
I had a sign in my office that read
Why is there never enough time to do it right, but always enough time to do it over?
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
I had a sign in my office that read
Why is there never enough time to do it right, but always enough time to do it over?
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
Sadly, I'm much older than agile. Even before agile, promises made by yes men had the same effect. :mad:
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
I had a sign in my office that read
Why is there never enough time to do it right, but always enough time to do it over?
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.Greg Utas wrote:
Why is there never enough time to do it right, but always enough time to do it over?
I know what I am going to put in the office... thanks
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Quote:
REV 1.20 ; 06/09/82 Prints "directory" after directories ; 06/13/82 MKDIR, CHDIR, PWD, RMDIR added ; REV 1.50 ; Some code for new 2.0 DOS, sort of HACKey. Not enough time to ; do it right.
In the following years, all us devs stopped adding those kind of comments, because they were redundant. All code is HACKey. There is never time to do it right. :rolleyes: From MS-DOS/COMMAND.ASM at master · historicalsource/MS-DOS · GitHub[^]
The one I like most (I assume, according to names present) reflects failed outsourcing attempt: * Author Date Comment *~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * Nilesh Rajbharti 07/12/04 Rel 0.9 * Nilesh Rajbharti 11/24/04 Rel 0.9.1 * Rawin Rojvanit 09/17/05 Rel 0.9.2 * D Flowers & H Schlunder 08/10/06 Much better now (1.0) * D Flowers & H Schlunder 09/11/06 Add base signed types (1.1) ********************************************************************/ Source: Microchip, https://www.microchip.com/forums/download.axd?file=4;429496[^]
-
I had a sign in my office that read
Why is there never enough time to do it right, but always enough time to do it over?
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.A similar one I had is: There is no time to do it right, but there is time to fix it in production.
-
Quote:
REV 1.20 ; 06/09/82 Prints "directory" after directories ; 06/13/82 MKDIR, CHDIR, PWD, RMDIR added ; REV 1.50 ; Some code for new 2.0 DOS, sort of HACKey. Not enough time to ; do it right.
In the following years, all us devs stopped adding those kind of comments, because they were redundant. All code is HACKey. There is never time to do it right. :rolleyes: From MS-DOS/COMMAND.ASM at master · historicalsource/MS-DOS · GitHub[^]
I love line 201:
CMP BX,AX ; enough for EXEC? JB EXECMER ; nope... cry -
raddevus wrote:
There is never time to do it right.
I'll tell you, that is true. I recently moved from a job that had no software development structure to a job where there are comprehensive procedures in place for writing and testing code. I am quite pleased with the new job because when code finally gets released, we are sure that it works.
The difficult we do right away... ...the impossible takes slightly longer.
I guess I was lucky in my career. For the first 20 years I always had time to do it right. I then went to a startup (about a year before the dotcom crash) and things changed. The next place I worked at was pretty much a 'we need it yesterday' mentality (which I ignored).
-
Quote:
REV 1.20 ; 06/09/82 Prints "directory" after directories ; 06/13/82 MKDIR, CHDIR, PWD, RMDIR added ; REV 1.50 ; Some code for new 2.0 DOS, sort of HACKey. Not enough time to ; do it right.
In the following years, all us devs stopped adding those kind of comments, because they were redundant. All code is HACKey. There is never time to do it right. :rolleyes: From MS-DOS/COMMAND.ASM at master · historicalsource/MS-DOS · GitHub[^]
My boss and I once inherited a very poorly designed chunk of software which
cried out for a complete rewrite. But that was never going to happen, so we
often had to write code which we would otherwise never have written. My
boss always prefaced such code with a comment:// May God forgive me for what I am about to write. -
Quote:
REV 1.20 ; 06/09/82 Prints "directory" after directories ; 06/13/82 MKDIR, CHDIR, PWD, RMDIR added ; REV 1.50 ; Some code for new 2.0 DOS, sort of HACKey. Not enough time to ; do it right.
In the following years, all us devs stopped adding those kind of comments, because they were redundant. All code is HACKey. There is never time to do it right. :rolleyes: From MS-DOS/COMMAND.ASM at master · historicalsource/MS-DOS · GitHub[^]
So true, man. I have manager who always give crazy deadline. "Finish this in three days!" "Our client can't wait! This new feature has to be done in one week!" "We have to do with current members!" Me: Well... well... I will simply hack here and there. There's simply no time to code them from the fundamentals.
-
Quote:
REV 1.20 ; 06/09/82 Prints "directory" after directories ; 06/13/82 MKDIR, CHDIR, PWD, RMDIR added ; REV 1.50 ; Some code for new 2.0 DOS, sort of HACKey. Not enough time to ; do it right.
In the following years, all us devs stopped adding those kind of comments, because they were redundant. All code is HACKey. There is never time to do it right. :rolleyes: From MS-DOS/COMMAND.ASM at master · historicalsource/MS-DOS · GitHub[^]
I used to work for Microsoft, in Exchange CPR (Critical Problem Resolution), writing bug fixes for Exchange from version 5.5 through 2007. One of the more notable comments from the Exchange source was in the Information Store Code... // This blows dead goats! A few years back, they started going through the codebase, cleaning up/removing such flamboyant comments.
-
I used to work for Microsoft, in Exchange CPR (Critical Problem Resolution), writing bug fixes for Exchange from version 5.5 through 2007. One of the more notable comments from the Exchange source was in the Information Store Code... // This blows dead goats! A few years back, they started going through the codebase, cleaning up/removing such flamboyant comments.
I-16-741018 wrote:
A few years back, they started going through the codebase, cleaning up/removing such flamboyant comments.
I'm sure it's not everyone in every department, but I can confirm MS has some automated build systems that have rules that match comments/variable names/strings against a...let's call it a list of "reserved words". For one, a check-in will get rejected if your code contains something like:
$ass = Load-Assembly [...]
This is built server-side, and as such I haven't been able to find the actual list. But I'm sure it would make for some interesting reading...
-
I-16-741018 wrote:
A few years back, they started going through the codebase, cleaning up/removing such flamboyant comments.
I'm sure it's not everyone in every department, but I can confirm MS has some automated build systems that have rules that match comments/variable names/strings against a...let's call it a list of "reserved words". For one, a check-in will get rejected if your code contains something like:
$ass = Load-Assembly [...]
This is built server-side, and as such I haven't been able to find the actual list. But I'm sure it would make for some interesting reading...
Yeah, it wouldn't surprise me, especially considering that MSFT has opened up parts of their codebase to specific partners. There were a lot of unusual references to various farm animals back then. LOL!
