- NEW!
by HungryGuy on February 17th, 2008
Yes: debugging undocumented code.
by Ghost Rider on December 30th, 2007
Yes: Documenting someone else's code
by PrettyPirate on July 23rd, 2007
Natural childbirth.
by Frank Tank on July 23rd, 2007
No, but undocumented code means I have the privy to rewrite it at my will.
by Jodie44 on July 23rd, 2007
Any longer than five seconds in stiletto heels.
by zee-ster on July 23rd, 2007
yeah, having to rewrite a program with no documentation in or outside the code!! oh, and the variable names aren't helpful either. arg.
by Derek DuCote on February 17th, 2008
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.
by nunya on December 18th, 2007
Yes - working with code that is not documented.
by JimmyG on September 12th, 2008
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;
by Mushen on April 29th, 2008
Only one thing and that is being the unlucky sod who has to write the Help file for the damn application.
by just helping on April 29th, 2008
Yes! tweaking code in HTML or a website design to get the right look.
by Takei-Shihan on December 18th, 2007
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.
by TofuBug on February 27th, 2009
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.
by JakobA I^_^I the alooney on January 6th, 2009
Yes. Answering the production depts questions about the code you wrote (and did not document) 5 years ago.
by JJeffrey on February 17th, 2008
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!!!
by Lilibuth12 on February 16th, 2008
sliding down a rusty razor blade!!! lol!
by Shawnothius on December 16th, 2007
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.
by rdrainer on July 23rd, 2007
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.
by bigbore on February 17th, 2008
getting stabbed or shot, ive been through all 3 and id choose Documenting code any day of the week.
by Borderlinux on February 17th, 2008
documenting disassembled code
by patio4it (tumblr) on November 16th, 2008
Understanding the documentation if it's written in a language you never learned.
by suMit on February 26th, 2008
to understand flow of program using someone else code that is not documented.
by web 2.0 on February 22nd, 2008
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
by iortizvictory on February 7th, 2009
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.
Would you be fired if you did 25% of your job wrong?
by Mister_Bromide on December 15th, 2010
| 3 people like this
Wondering how to find the "loopholes" in a website running directly from a server so that code can be entered into it. "Manipulation"
by SUPAZONG on December 1st, 2010
| 1 person likes this
Why, given its broad range of features and performance in W3C compliance tests, has the Opera browser failed to notably up its market share?
by Andrew_C9013 on November 21st, 2010
| 1 person likes this
what is the programing language that was created to honor lady Ada Lovelace?
by Rakhitha91 on January 9th, 2011
| 1 person likes this
Please help me get started with this assembly language question, any help would be appreciated!
by Sandeep_S1594 on January 9th, 2011
| 1 person likes this
You're reading Is there anything more painful than documenting code?
Your favorite Q&A site is on Facebook! Become a fan to connect with the ever-growing community of Answerbaggers, share your thoughts and find out what Answerbag's up to next!
Comments
You beat me to it. Of course, it *is* an obvious answer.
by Cyanotic Wasp on August 28th, 2008
Thats the first thing i thought of. Especially when the code is badly written in the first place
by paulthom12345 on May 19th, 2009