6 ms·

Also a "Solo dev for an app with hundreds of thousands of users" I just test everything myself. On one OS (Mac). The worst part is having to run VMWare with ol

by feelix 8y ago

Also a "Solo dev for an app with hundreds of thousands of users" I just test everything myself. On one OS (Mac). The worst part is having to run VMWare with older OS versions sometimes, but not usually. I find that bugs are almost never OS specific, and are rather just logic errors. I find that having other people test my code adds little value, as I can literally just test it myself in the OS that I write it in most the time. I know that this goes against all advice that you read, and all the "common knowledge" that is out there... but I've been doing this for 15 years and have got over 1 million users in total probably, and I almost never get support emails regarding bug reports. So, in my experience, I really find that everything I have heard is wrong. I realize that other people may have other experiences but found this point of reference interesting.

j45 8y ago
Experience building software can lower the testing requirements. I find the degree of testing needed can be relative to the difficulty of the problem, the unnecessary complexity of the solution, and the average skill of the developers working on all 3. Clever (simple) architecture will often beat clever programming in the long run.
- newsbinator 8y ago
  > Experience building software can lower the testing requirements. This is a good point. The longer I've been at this, the less often, "this is likely to work" is a thought that I let go unchallenged.
  - retbull 8y ago
    "This is totally going to work" is only said when I am completely sure that it is going to fail catastrophically. If anything works I feel mild distrust with my code from that point forward.
    - j45 8y ago
      Knowing the difference between thinking less about yourself vs less of yourself is important when taking your work seriously but not taking yourself too seriously. I have a healthy doubt of my own work that seems to end up making it work well first by keeping it as simple as possible. Keeping the mindset of an innocent beginner is critical as a developer with experience. Everything is easy in the beginning, not the long term - I like to see what code bases people have worked on for many years instead of being able to neatly start from scratch.
      - retbull 8y ago
        Yep. I try not to get caught up in worrying by adding lots of tests and making my code easy to change. When I find an old crusty piece of code I actually have the most fun because it takes me completely immersing myself in it to find all the crap floating around.
    - pier25 8y ago
      I think it's only fair, as a developer, to live in a state of constant fear and paranoia. (joking)
      - deleted 8y ago
        [deleted]
  - j45 8y ago
    Absolutely. It doesn't mean testing isn't required - it's absolutely the case when something is business critical, or average / inexperienced devs are painting unicorns and rainbows everywhere. I have a healthy skepticism of my own work, it keeps hubris in check. This combined with a preference to keep things simple (to come back to later and to let others join easily), I find encourages everyone to build a code base they want to work on long term.
logicallee 8y ago
you don't mention or allude to automated testing. You don't have any? (i.e. 100% test coverage except flip the 1?)
10dpd 8y ago
I think you misread the question - the question is about "user testing" not "QA Testing".

by feelix 8y ago

j45 8y ago

Experience building software can lower the testing requirements. I find the degree of testing needed can be relative to the difficulty of the problem, the unnecessary complexity of the solution, and the average skill of the developers working on all 3. Clever (simple) architecture will often beat clever programming in the long run.

newsbinator 8y ago
> Experience building software can lower the testing requirements. This is a good point. The longer I've been at this, the less often, "this is likely to work" is a thought that I let go unchallenged.
- retbull 8y ago
  "This is totally going to work" is only said when I am completely sure that it is going to fail catastrophically. If anything works I feel mild distrust with my code from that point forward.
  - j45 8y ago
    Knowing the difference between thinking less about yourself vs less of yourself is important when taking your work seriously but not taking yourself too seriously. I have a healthy doubt of my own work that seems to end up making it work well first by keeping it as simple as possible. Keeping the mindset of an innocent beginner is critical as a developer with experience. Everything is easy in the beginning, not the long term - I like to see what code bases people have worked on for many years instead of being able to neatly start from scratch.
    - retbull 8y ago
      Yep. I try not to get caught up in worrying by adding lots of tests and making my code easy to change. When I find an old crusty piece of code I actually have the most fun because it takes me completely immersing myself in it to find all the crap floating around.
  - pier25 8y ago
    I think it's only fair, as a developer, to live in a state of constant fear and paranoia. (joking)
    - deleted 8y ago
      [deleted]
- j45 8y ago
  Absolutely. It doesn't mean testing isn't required - it's absolutely the case when something is business critical, or average / inexperienced devs are painting unicorns and rainbows everywhere. I have a healthy skepticism of my own work, it keeps hubris in check. This combined with a preference to keep things simple (to come back to later and to let others join easily), I find encourages everyone to build a code base they want to work on long term.

logicallee 8y ago

you don't mention or allude to automated testing. You don't have any? (i.e. 100% test coverage except flip the 1?)

10dpd 8y ago

I think you misread the question - the question is about "user testing" not "QA Testing".