1. 5
  1.  

  2. 5

    My bug tracker is mostly full of feature requests for tracking purposes.

    1. 2

      Not to knock the article, I think the content is good, but it could use some proofreading.

      1. 3

        Happy to fix anything you find amiss. My proofreading apparently did not catch what you see.

        1. 3

          A couple of little things I saw in a quick scan:

          • “Yea” -> “Yeah”
          • “eachother” -> “each other”
          • “human’s” -> “humans”
          1. 3

            Fixed! Thanks

            1. 2

              I think joshuacc got everything, I’ll let you know if I find anything else ;)

              EDIT

              Found another one: “Theres no way around it…” should be changed to “There’s…”.

              1. 3

                Fixed! Thank you

                1. 1

                  No problem, and great post! :)

        2. 2

          The initial tweet feels too dumb to merit any response. I don’t even know where to start, so how about the empirical finding that bug count correlates linearly to codebase size; in light of this, the tweet reduces to “think about what it means: you have written more than a few hundred lines of code”. Is this supposed to be some kind of insight? (It feels like that from every angle.) And where do you go from there – we should all out-NASA NASA? That is what would be interesting: not the fact that there are so many bugs that you need a machine to keep track of them (thanks for that, Captain Obvious) but what do you do about it? And how? Which is a question this “whoa man, have you ever looked at a bug tracker? I mean really looked at it?” stuff leaves totally open.