Skip to main content

Writing Tips

When we are writing emails some time we may not care much about small things.But it will create difficulties to recipient. As well as it reflects sender.This is a good post on it. It highlights necessity of the good writing.It mention simple example as follows;

Compare the following two job applications. The content of the emails are identical – but who would you give the job to?

i’ve attached my resume i would be grateful if you could read it and get back to me at your earliest convenience. i have all the experience you are looking for – i’ve worked in a customer-facing environment for three years, i am competent with ms office and i enjoy working as part of a team. thanks for your time

Or

Dear Sir/Madam,

I’ve attached my resume. I would be grateful if you could read it and get back to me at your earliest convenience. I have all the experience you are looking for:

* I’ve worked in a customer-facing environment for three years
* I am competent with MS office
* I enjoy working as part of a team

Thanks for your time.

Yours faithfully,

Joe Bloggs

So think twice before your writing

Comments

Popular posts from this blog

The transaction is in doubt

Sometimes you may get this error when you use transaction scope . The transaction is in doubt I also got this error recently and able to find the reason for it. That is because of the some of the readers had not properly disposed. Actually in this case you can use Using keyword to overcome this. Exception : System.Transactions.TransactionInDoubtException was unhandled by user code Message="The transaction is in doubt." Solution : using (reader) { }

Dead Code Problem

Problem Actually this problem occurred when i was doing integration two projects. [Phase1 and phase2 of a project] . Phase 2 is developed on top of the phase1. Parallel phase1 had changed lot . Mean time those were working on phase2 has commented existing phase 1 code without comments . Phase 1 and phase 2 merged with some conflicts. So we commented such places with the descriptive comment . After merged the result code base has merged those phase 2 commented parts. Also there was some of already dead code in phase 1. So it is difficult to understand weather this is actual dead code or commented one from phase 2. Mistake Had left dead dead code and missing comments . Lesson learned Normally developers leave dead code in their original code with the mind of future purpose. But this not a good habit to continue.As long as you use source control ,earlier code may exist. Problem will occur if you are not using such version control. In such a situation you can keep dead code with des