I’ve never been able to give my main product the full quality treatment I’d like. Possibly like many of you, my main testing strategy is to release an update and await customer feedback.
Code review, apparently, is a really good way to improve software quality, but this isn’t easy to do when there is just one programmer in the company. Rigorous system testing falls by the wayside too, like many useful but tedious parts of running a business when it all depends on you.
After six years, I’ve finally got a QA guy on board for a short term spell, and it is doing wonders for improving my product, Poker Copilot. I wrote about the experience here. An excerpt:
Until now, quality control in Poker Copilot has been a combination of unit testing, my own haphazard system testing, and customer feedback. It is clear to me now that this is not enough. Having a person dedicated – even for a few weeks at a time – to quality control is unbeatable for making a software product top-notch.
I’m keen to hear any ideas you have for improving product quality in a sustainable way for the one-person company.