News for hackers. Stuff that matters.
Re:Why Taxpayers Pay McKinsey $3M a Year for a Recent Colleg... by slg on Thursday December 05, 2019 @03:10PM (#21715971)
Thanks. At this point I should probably go ahead and hire an editor to review my comments before publishing.
Re:Why Taxpayers Pay McKinsey $3M a Year for a Recent Colleg... by braythwayt on Thursday December 05, 2019 @07:00PM (#21718033)
Speaking as a frequent commenter and author, I suggest this is teh system working as intended. There are not letters to the editor you put in in envelope and mail away.

When HN "published" your letter to the editor, it's not printed on atoms and distributed all over town, or mailed out to subscribers.

You can post a comment, edit it, and maybe even fix something based on feedback. I suggest that without being completely slipshod, it's better to go ahead and make a comment when you have a coherent thought.

The community will help you sort out any spelling, grammar, or attribution hiccups. I think this is a good thing for everyone, reducing friction and eliminating even self-gate-keeping.

Mixing up two homophones is not a tragedy. Someone not contributing because they fear that they'll be snubbed for getting a word wron? That's a tragedy.

JM2C, &c.

Re:Why Taxpayers Pay McKinsey $3M a Year for a Recent Colleg... by antjanus on Thursday December 05, 2019 @03:49PM (#21716320)
if you don't want to feel like you're pandering to HN comments, you can probably hire a consultant to do the proof reading for you! =D
Re:Why Taxpayers Pay McKinsey $3M a Year for a Recent Colleg... by ineedasername on Thursday December 05, 2019 @04:07PM (#21716506)
I cut out the middleman and just pay people to comment for me entirely. This one cost me $34, one dollar per word. But punctuation is free so it is not a bad deal.