1. 30
  1.  

  2. 10

    I was expecting a short post about a funny typo, instead I got a short post about life, and a wonderful thought I’m delighted to be reminded of.

    1. 6

      FWIW fixing typos is a great way to get started with projects, getting familiar with the test infrastructure and CL procedure. Probably half of my commits to the Go standard library are typo fixes.

      1. 5

        There should be a “documentation” tag.

        1. 3

          You can suggest tags using the meta tag.

          1. 3

            They’re pointing out that there is no such tag as “documentation” right now, not that this story doesn’t have it.

            In any case, I think “practices” applies.

            1. 5

              Right, I’m saying that if they want the tag to exist, they should create a submission that suggests adding a documentation tag and post the story using the meta tag.

        2. 5

          If you want to explore the reality behind your last paragraph, you can consider reading “Zen Mind,Beginner’s Mind” by Shunryu Suzuki: https://amazon.com/Zen-Mind-Beginners-Shunryu-Suzuki-ebook/dp/B00I8USOM0

          1. 5

            A suggestion that I have heard for proofreading for these kinds of errors is change the font and read it again. Changing the visual appearance of the text apparently helps get around the fact that you tend to skip over it because you’re already (too) familiar with it.

            1. 2

              Another trick i’ve heard is to use a screen reader. It’s easier to hear when there’s something off about a sentence than to read, as your brain won’t auto correct as much.

            2. 1

              Nice! I think most of my PRs to public repos are typofixes to their READMEs actually. GitHub makes this so easy since I can edit the file in a browser and they’ll transparently create a fork for me if necessary. The only gripe I have is I’d like for my fork of the repo to go away automatically after it’s merged… #firstworldproblems