Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?
 
PerlMonks  

comment on

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

Before writing the body, it's a summary, so you should have an idea what you're going to say before you start typing. Think of it as a requirements document for the rest of the email.

But what if the the idea changes, as it so often does? I can't tell you how many times i did exactly this, and then had to change it later. You may call me fickle, though i think it has to do with "getting into it" and allowing things to change.

After the intent to write, and the writing itself, a summary would be accurate. As the ideas are already worked through, i think it a much better time to write a summary.

A good subject line also gives the reader a reason to read it.

The subject line gives a good reason to read it, but so does the sender. Indeed, i bet i read more email based on sender than subject line. Further, i find the subject line is much better to review when looking at old email, not new email.

That is, when i receive an email, i will most likely read it if it is from family or friends, regardless of subject line. I'm reading it--please excuse my disagreement with you--simply because they sent it. However, when i need to find an old email from said persons, who sent it is simply not enough (any more), a summary is, however. And not an intent of what they wanted to write, rather, what they actually did write.

If, though, the sender is unknown, the subject line is an indicator as to my want to read it. Perhaps then, the intent to write is better than the summary, as the function is now one of advertisement instead of summary for later review. Indeed, as these emails are not from family, friends, or soon to be friends, i am unlikely to be looking back to even require a summary.

I want to thank you for your message, it is well thought out. I happen to disagree, but i enjoyed reading and responding to it.


In reply to Re^2: Email subject lines should be written: by chacham
in thread Email subject lines should be written: by chacham

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
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (4)
As of 2021-08-02 07:24 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    My primary motivation for participating at PerlMonks is: (Choices in context)








    Results (21 votes). Check out past polls.

    Notices?