by 
EL1 2
ANSWERS: 25
-
Natural childbirth.
-
Any longer than five seconds in stiletto heels.
-
1) Running it through SDLC. 2) Rekeying it after the source member is lost. 3) Producing a Test Case document when the Baseline cases aren't mirrored in the Parallel runs. 4) Removing the debugging code you worked so hard to put into it because the shop standard requires no debugging code when a module is promoted. 5) Being one of a dozen programmers working on the same piece of code at the same time. ... about a few other things in the same vein ... but that's enough for now.
-
No, but undocumented code means I have the privy to rewrite it at my will.
-
yeah, having to rewrite a program with no documentation in or outside the code!! oh, and the variable names aren't helpful either. arg.
-
documenting code isnt hard, just give a brief description of what is happening, and trust me you want documents when you need to find an error in 30 pages of code.
-
Yes - working with code that is not documented.
-
Certain pressure point pinches ... but just barely ... I have had the pain of rewriting the interface for a "robotic spindler" that wraps wire to make electric motors, transformers, and electromagnets. It was written in Assembler to run on a Unix mainframe with absolutely no documentation, and the interface that existed was in Mandarin Chinese (my fifth language) and I had to find and fix the "it won't run" bugs, and then both translate the whole thing into a bilingual French/English interface and also write full documentation for exactly what every line of code is for.
-
Yes: Documenting someone else's code
-
sliding down a rusty razor blade!!! lol!
-
YES!! NOT documenting code and then have the next programmer try to figure out what the IDIOT before him was doing!!! Documentation is part of programming!!!
-
getting stabbed or shot, ive been through all 3 and id choose Documenting code any day of the week.
-
Having a dislocated limb relocated. Fortunately I've never had to go through that, but remembering the screams of patients I have seen whilst having that done, haunts me.
-
Yes: debugging undocumented code.
-
documenting disassembled code
-
of course, that is nothing to do at all.. if you're doing coding for a living, then you shud really b feeling luck to have codes to write, and happy as well, if you think you're in the wrong field, i think you shud quit, and do what you're happy at
-
to understand flow of program using someone else code that is not documented.
-
Yes! tweaking code in HTML or a website design to get the right look.
-
Only one thing and that is being the unlucky sod who has to write the Help file for the damn application.
-
Painful because they're two different disciplines. Most people are uncomfortable outside their own discipline. Programmers' documentation, when they bother, often sounds like code: //Multiply interest times principal yield = interest * principal;
-
Understanding the documentation if it's written in a language you never learned.
-
Yes. Answering the production depts questions about the code you wrote (and did not document) 5 years ago.
-
Hey check out the open source tool NDoc http://ndoc.sourceforge.net/ . This tool will assist in writting your documentation based on the comments that you input.
-
Wow I'm actually surprised no one has even mentioned it. Ever had a code review with someone who knows nothing about programing yet constantly asks really stupid unrelated questions just to make themselves sound smart. That or trying to explain to a head strong executive that no programing language is a "magic wand" and that their "brilliant idea" just isn't feasible for one technical reason or another. I spend more time at the office in meetings about pointless stuff than I do actually developing software. Compared to that I actually look forward to documenting my code.
-
Yes, having a clueless manager.
HungryGuy RELATED QUESTIONS
Copyright 2023, Wired Ivy, LLC