3 ms·
I tend to take a bit of a “hybrid” approach. Unlike many, I won’t start with a duct-tape-and-baling-wire chimera that barely works, as MVP. I like to start wit
by ChrisMarshallNY 5y ago
I tend to take a bit of a “hybrid” approach.
Unlike many, I won’t start with a duct-tape-and-baling-wire chimera that barely works, as MVP. I like to start with a very solid baseline. Good quality, well-tested, extensible architecture, etc., and work up from there.
I like to maintain what I call “constant beta,” where the project is what I consider “bug free,” at all times (although incomplete). This means that, as I develop a project, I am constantly testing (usually by writing a test harness in parallel with the principal codeline[0]). If I encounter any bugs (even “little” ones), I stop all forward feature development, until the bug is either fixed, or converted into a “stable” TODO.
As you can imagine, this was not popular with my employers; even the ones obsessed with Quality. I had to wait until I was released on my own recognizance, before I could try working this way.
The results have been quite good.
One example of how this pays off, is that I can start using Apple’s TestFlight beta-testing service, very, very, very early in a project. This allows the project to be distributed to many testers, evaluators, and stakeholders, for feedback and design review, at an extremely early stage. Sort of an “internal MVP,” with a great deal of control over the testing.
Works a treat. It’s definitely a bit of a risk, that the ultimate end-users are not being used as the “fuzz testing pool,” but it does help to ensure a fairly stable future for the project. Risk is basically the lifeblood of entrepreneurship. Releasing questionable-quality product, too early, carries significant risk, as well.
One issue, that I frequently encounter, is that people refuse to consider the price paid for shoddy quality. The only cost they consider, is initial development, with a “we’ll fix that down the road” mentality.
In my experience, bad quality can easily result in extinction-level events (E.L.E.) Brand damage, being one example. Brand damage can be unrecoverable. It’s also quite difficult to quantify.
But in today’s climate, end-users don’t seem to care about Quality, so I do it for my own satisfaction.
[0] https://littlegreenviper.com/miscellany/testing-harness-vs-unit/ https://littlegreenviper.com/miscellany/testing-harness-vs-u...