On Apr 27, 9:23 am, Mark Murphy <mmur...@commonsware.com> wrote: > I suggest that you calm down, ease up on the childlike ALL CAPS AND > EXCLAMATION POINTS!!!, get rid of the profanity, and simply state that > you believe that there has been a regression.
If I didn't just spend the majority of my weekend and past couple of days (~35-40) hours painstakingly tracking down this issue then I'd be more in a tolerable mood. It also doesn't help that I wrote this after an all night 15 hour "session" finishing up the search for this issue. I didn't wake up in the morning refreshed and decide to post a rant. Heh.. I don't think I've written many posts on the Interwebz with caps... These kinds of failures of Android really make me displeased at this point... And I love Android and am a major advocate of it, but know to treat quality matters with kid gloves. > Then, most likely, it would have taken you less time and less typing > to write a test case that demonstrates the regression, then provided a > link to it as part of your post. Uh.. maybe.. It could take several more hours to produce a thorough test case. I don't work for free, sorry.... I've already lost ~40 hours of productive time towards launching my product / platform and I have every right to be unhappy with the lack of quality of Android over all OS releases for low level dev. > Bugs happen. Cursing, shouting, and insulting developers will neither > make the bug go away nor improve the quality of future code. Moreover, > claims of bugs without reproducible test cases are next to useless, as > any professional developer should realize. If Google wishes to engage my services at my corporate contract rate I'd be glad to provide a fully vetted and professional test case. I don't have to prove anything for free. > > Should I file a bug? > > Yes. I cannot tell if there already is a bug report for this on > b.android.com, because "duplicate" appears in quite a few issues, > courtesy of issues being flagged as "duplicate". However, there > doesn't seem to be any hits on both "duplicate" and "nio", so I am > guessing that it is not there. > That being said, don't bother if you're not going to provide a > reproducible test case. > If quality was your top priority, you would not have wasted your time > on the rant. Instead, you would have written the test case and > therefore provided the evidence in a fashion that could be reproduced > by other engineers. This might lead to a solution, either in the form > of a fix to Android (if there is a bug) or a fix to your code (if what > you were doing is outside the NIO contract but just happened to work). I simply "wasted" my time on a rant because it feels good.. ;P I'll get around to conceivably filing a bug, but I simply can't afford to work for free at this point creating test cases for bugs or not especially for a corporation with excess cash. While I have pinpointed the source of the problem I am uncertain how long ($$$) it will take to create a well engineered test case. Probably a couple hours, but I'll only take initiative if I'm paid as I believe I have a workaround even if it's not fixed. A couple hours at my corporate rate is good $$ $. I am a bootstrapped single founder startup and I only have ~6 months of remaining runway until I am completely tapped out and run my ship into the ground _again_. Working in waves sucks and I have invested all my earnings into this beast. I will barely launch my product that I've been working on mind you for ~8 years by that time (long story / will be told another time). I simply do not have time to work for free and this issue has cost me plenty already in lost productivity. I also was pulled away from some very complex final refactoring work by this "intrusion". My exasperation isn't over this one matter, but a series of repeated failures through almost every Android release. Apologies if I may hurt some other engineers feelings; write better code. Sure this email thread may not present my efforts in the most professional light, but I'm simply annoyed and this was a very difficult bug to find and it hard crashed my entire platform / product. I'm "terrified" that future Android releases will crash my entire product that I will be selling. I have every right to be concerned over the quality of Android as the lack of it has been clearly apparent. The culture of beta and 80% software "pioneered" by Google is not acceptable. --Mike -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
