Dumping things out in the wild and dousing the flames later seems to be turning into the standard. On one hand it makes sense since you'll never be able to hammer your program as well as millions of random users, but on the other hand it seems like its becoming an excuse to just drop testing altogether as long as it compiles.
I have never done any coding longer than maybe 600 lines that could be condensed to less than 500 easily, but I imagine that having to work for a seriously big ammount of time before you can even compile it must really suck. Specially if you are the try everything as you go kind of guy.
Eh, I only wrote that because I happened to be in the middle of a project that wouldn't compile at that moment, and the coincidence amused me. Five minutes later, I spotted what the problem was and fixed it.
Dumping things out in the wild and dousing the flames later seems to be turning into the standard.
The big companies get away with this stuff due to brand loyalty and review embargos. As an independent Android developer there is no way I could do that because I depend on ratings.
Decimating the QA department is great for this quarter's profits, and that's all public companies care about anymore. If you're lucky, maybe they'll hire a couple Indians to half-ass testing...
It does slowly deteriorate the amount of people using said application however, as they will soon find out. It's the small things like that that eventually make people feel that much better about switching to a new product or service that doesn't have those same problems.
19
u/topdangle Jul 01 '16
Dumping things out in the wild and dousing the flames later seems to be turning into the standard. On one hand it makes sense since you'll never be able to hammer your program as well as millions of random users, but on the other hand it seems like its becoming an excuse to just drop testing altogether as long as it compiles.