This is amazing. There's a long reddit thread and some additional instructions here: http://www.reddit.com/r/Android/comments/2gv035/you_can_now_...
From the README:
> Soundcloud - Works, crashes when playing sound
Funny definition of 'works'.
From the README:
> Soundcloud - Works, crashes when playing sound
Funny definition of 'works'.
"It's done; it just has some bugs that need fixing."
To be fair, I've said this sentence myself in earnest several times.
You can say it will probably never be done, or you update your definition of "done" to "it has no bugs stopping a release". Personally I prefer the latter.
Often there are tons of TODO comments left in the code (including TODO comment this class), unit tests are non-existent, a simple smoke test will cause a null pointer exception or not even deploy, or they committed schema migration SQL scripts but did not change the entities/data objects corresponding to those tables so the - now mandatory - new columns cannot even be FILLED by the app.
Stuff like that, that isn't DONE, it's deserving a punch in the face. OTOH, it may be symptomatic of our don't-blame culture that the consulting firm in question isn't fired on the spot or the much needed punch in the face isn't delivered. Those are days I wish we had US-American at-will employment and hire/fire culture.
It's not malicious. You could argue it's negligent, but I would only agree with that assessment if the Dev in question doesn't include the "it just has some bugs that need fixing" bit and is attempting to see what he/she can squeak by QA because he/she doesn't want to work on that thing anymore.
Otherwise it just reflects the difference in focus between writing code and building a product.
That's like a winedb entry that says "game works" followed by "crashes after intro video"!