Re: [Wonder-disc] [SPAM] - Re: Style - Email found in subject

[Kantala, D. R. <dka...@mo...>]

Consider the letter¹s audience.  #4 looks funny in the example sentence you
provided.

They may think you have a typo in your resume, which could lead to bad first
impressions.  Not enough attention to detail, etc...

DK | Software Engineer



From: David LeBer <dle...@co...>
Date: Mon, 29 Jun 2009 13:38:35 -0400
To: wonder Project <won...@li...>
Conversation: [SPAM] - Re: [Wonder-disc] Style - Email found in subject
Subject: [SPAM] - Re: [Wonder-disc] Style - Email found in subject


On 29-Jun-09, at 1:00 PM, Mike Schrag wrote:

> TECHNICALLY it's #4, but I refer to it as #3 when i refer to it
> formally these days ...

I prefer #3 as well. Even if #4 is correct, it seems a little hokey to
me.

> On Jun 29, 2009, at 12:54 PM, David Avendasora wrote:
>
>> Hi all,
>>
>> I'd like to get a definitive (if possible) answer to how I should
>> refer formally to Project WOnder in my resume:
>>
>> 1) Wonder
>> 2) WOnder
>> 3) Project Wonder
>> 4) Project WOnder
>>
>> For example: Extensive experience with Project WOnder frameworks.
>>
>> Dave

;david

--
David LeBer
Codeferous Software
'co-def-er-ous' adj. Literally 'code-bearing'
site:  http://codeferous.com
blog:  http://davidleber.net
profile: http://www.linkedin.com/in/davidleber
twitter: http://twitter.com/rebeld
--
Toronto Area Cocoa / WebObjects developers group:
http://tacow.org





----------------------------------------------------------------------------
--
_______________________________________________
Wonder-disc mailing list
Won...@li...
https://lists.sourceforge.net/lists/listinfo/wonder-disc


Confidential & Privileged

Unless otherwise indicated or obvious from its nature, the information contained in this communication is attorney-client privileged and confidential information/work product. This communication is intended for the use of the individual or entity named above.  If the reader of this communication is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.  If you have received this communication in error or are not sure whether it is privileged, please immediately notify us by return e-mail and destroy any copies--electronic, paper or otherwise--which you may have of this communication.