Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I don't know what the OP meant, but I remember reading it and noting that the section on not using the passive voice used the passive voice. There were probably more things like that.

Unrelated, but in general I think the advice of Nassim Taleb is good: most people looking to improve their writing style are really lacking something to say.



That's not practical advice.

Especially in the workplace, you have plenty to say. It may not progress humankind, but you definitely need to say it. You may be discussing a design decision, announcing a promotion, negotiating a contract, etc. In these cases, one might get better at writing and say the same thing more effectively.

This is where a person would need practical advice to improve his writing style. I've run into plenty of people in professional settings who would be more effective in their jobs if they could write better. They often don't realize it themselves until a colleague suggests revisions.

I read Strunk & White at some point. It has its contradictions, sure, but much of its advice is good if you treat it as advice, and not a rulebook. For example, you might occasionally need the use the passive voice, but it's very good advice to strongly prefer the active voice and to use the passive only when you really need to. Some people really do have a problem using way too many passive verbs, but few realize it until they try writing with active verbs.


> I don't know what the OP meant, but I remember reading it and noting that the section on not using the passive voice used the passive voice. There were probably more things like that.

Are you sure that wasn't a joke? I recall that the writers often would cleverly break their 'rules' to make them examples of what to avoid.


No, they gave examples of the active voice that were actually passive voice, just better written.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: