One of the issues that isn’t obvious is the difficulty in actually doing any reported MMJ study, let alone one that was done by respected institutions. While one can argue about the significance of the small sample size, it’s amazing that there’s an actual reportable group
The issue is the THC vs CBD content that’s being provided. Most of the medical/medicinal aspects are focused on strains with more CBD while recreational emphasizes THC
My "favorite" Clearcase server issue was one that took 2 weeks of uptime before it resulted in a crash on a up-to-date AIX installation. I had to wait until we had somewhat identified the timeline before engaging our ops team so they could log the crash and submit it back to IBM so they could investigate/fix
Don't make the job just about the code in front of you.
Use the opportunity you have right now to learn about working in a team (and possibly taking the lead/managing), managing customer requests and expectations, implementing business processes, etc.
All of this will be valuable whether you keep working at this company, another one or decide to work on your own ideas/dreams.
Why would you expect anyone in that position to expose themselves publicly? Although they could give useful feedback, it wouldn't be in their interest to deal with these issues outside of a formal process. Unless of course it's in their job title to handle developer relations. Even then it'd be more setting up coordination and less anything technical.
Granted without knowing what exactly that process could be accessed or what it is, I agree that you need to do something to "start the conversation." However, attacking is unlikely to achieve the results you want. This is especially true considering the imbalance in your relationship with Apple. I've worked a number of years in enterprise software and for large enterprises. You have to learn how to bring attention to issues and escalate them constructively and professionally. You also learn that you don't always get what you want.
Do the blog posts but be aware of the tone. Use the mailing lists. Get others to raise their voice and show that it isn't an isolated incident.
In the meantime, since the issue is out there and details are known, workarounds need to be figured out that can be implemented. Short-term, there should be things that can be done by app developers. Longer-term, a solution probably needs to be put in place in the project that will address the needs of both app developers and Apple. (Apple dropping use of the project may be a possibility but I don't see that as a win for anyone.)
Also realize that an app developer "losing an entire afternoon" is minor in the grand scheme of things. However inconvenient it may be to be that developer, unless it's an absolute show-stopper, any reaction or solution will take time if one is implemented at all.
Past experience with Apple shows that this sort of public attack is the only way that's at all effective to get some sort of fix.
You say that we have to learn how to bring attention to issues. We have, and this is the result. I don't understand why that's so hard to believe.
Once again, if you think you have a better way, I'm all ears, but I need specific suggestions, not useless vague advice to talk to them, as if nobody ever thought of that or tried it before.
The developer who lost an afternoon was me, not Jon. I'm pretty sure the community is used to me having an overly dramatic tweet about everything that annoys me by now. It is minor, and you're right: it'll probably result in no action required from anyone come Monday.
