• The core is always “write for your audience”, and god so many places suck at it. If you’re writing a technical article for developers and include “deliver value” or similar, you’re doing it wrong - that’s something you’d write to appeal to executives and managers, not someone who’s trying to figure out how the latest JS framework works.

    With regards to formality, I find it more important to just be true to yourself, including ignoring some grammatical rules if that’s what you do. I only have a basic spell checker while writing mine.


    score 1 · canonical

    • In case you want to fix it, I’ll share a minor mistake I saw in that linked blog post:

      We are all speaking some sort of language, but none of us follow all the rules, and we all have some of our own. You might have noticed that in the previous sentence I joined two separate but related sentences with a comma. This is not grammatically correct in English - you’re supposed to use a semicolon.

      Don’t worry, I’m not talking about a grammatical mistake you’re making to prove a point. I’m talking about an accidental lack of grammatical mistake.

      The first sentence of my quote is already grammatically correct. The rule violation you’re describing is a comma splice, but the sentence is not an example of that. Because you added the coordinating conjunctions “but” and “and”, the commas are grammatical, and replacing either with a semicolon would make the sentence ungrammatical. The missing intentional grammatical mistake distracts from that paragraph’s main point.


      score 1 · canonical