I've been a software developer for 25 years. The time it takes to look at a request, determine its importance vs other issues that may be pending, put it on a business plan for the quarter, assign someone to the task, figure out how to make that work with the existing code base, test it, make sure it actually works and schedue it for some kind of release is not instant. You can rest assured that any company that works at all on Internet time is worried first and foremost about the stability of the product, getting features rolled out that were planned in advnace, and then looking at enhancements. Nobody is ignoring you. (I don't work for Pandora at all, disclaimer here) But I'm sure that they, like every other software company on the planet, has a six to twelve month backlog of feature requests to consider even before others throw them on. Sometimes something can be done really quickly - like for example if there was text that was red and green to determine stop/start and that was not working for colorblind folks, switching to an icon is relatively simple. But messing with algorithms, making changes to workflows, and so forth - you can't just throw code changes into the mix and move on, unless you want the next complaint to be "why did this stop working? When is my radio coming back on?" Even the best companies have this happen- anyone remember when Amazon went down for like, a really long time back in the day? That cost them millions. Nobody wants that to happen to their company, so these things can take time. Also consider the workload developers face - there's never enough of them because to be honest there's always shortages. Hang in there.
... View more