Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

The next exponent is uncomfortably close now. It doesn't get any easier.

I keep a paper log, in a loose-leaf binder that sometimes contains printed pages. I don't always keep it at the workplace, preferring instead to read it in the morning and to update the latest notebook in the evening. When I write in it, I use a number-two pencil and a big fat artist's eraser. It slows me down, and I do that on-purpose.

You forget a lot of things. We all do. That's why documentation is so important. I was recently asked to unearth some code that I'd written in-preparation several months ago and to quickly put that code into service. Well, the first thing I had to do was (literally...) to find it. Then, I had to manage to understand it in only a couple of days. It was tough, but I did it.

  • “Find” it?
  • “Understand” it?
  • “In only a couple of days?”
  • It was “tough?” (Like, dude, didn't you write it?!)

Yes, of course I did write it, but when confronting that work today ... it was the work of a complete stranger. I was at-first no more equipped to deal with that code than anyone would have been who was seeing it for the first time, as I for all intents and purposes was.

Fortunately, “the person who wrote it” left lots of notes. In the version-control system there was a complete design-document, which I re-read. And there was the logbook. And finally, lots of comments in the code. These sources pointed me to other related systems that I had not at first (re-)discovered. Most assuredly I would have been floundering around for a week or more just getting my feet on the ground, and there was not “a week or more” to be had.

I don't think that any of this has anything to do with that “next exponent.” Rather, I think that a lot of us have very sloppy, very slap-dash work practices (and plenty of excuses and plenty of books to say that this sort of thing is par-for-the-course, or necessary due to the nature of the work, or even brilliant because we're all such geniuses...). And, yeah, I say “we.” A self-inclusive pronoun.

Engineers in other professions are taught and required to keep lab-notebooks. But we're not. Companies plying other professions maintain project-plans that are thousands of items long:   we attempt to substitute obstinacy.

We should know better. They do...


In reply to Re^2: Work practices: log books, notes files... by sundialsvc4
in thread Work practices: log books, notes files... by doom

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others examining the Monastery: (4)
As of 2021-06-16 19:24 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    What does the "s" stand for in "perls"? (Whence perls)












    Results (78 votes). Check out past polls.

    Notices?