Re: Jargon in rubbish out?
Mmm, I'm still pissed off at the way they threw away all that was good about iPlayer Radio (not least its ability to work pretty much flawlessly on older devices, plus various things about the UI that made getting to what *you* wanted to listen to easy, as well as making it easier on the eyes of those of us with less than perfect vision) and ignored all resultant complaints in the process of lumbering us with BBC Sounds.
Which, despite several years of development since then, is still a bit crap in places where it really shouldn't be if the developers would only control their egos long enough to learn some lessons from the past, and pay attention to the things that really were good about iPR rather than being so determined to reinvent the wheel once again that they end up producing something that has a smashing new logo on the side, but doesn't sit true on its axle so ends up giving the user a rather uncomfortable ride...
And that was just the latest in the ongoing trend of BBC developers to take something that worked pretty well and really just needed a bit of polishing to turn it into something truly world-class, and instead throw all their resources into coming up with a completely new replacement which ignored the lessons learned from the existing product, as well as anything other than 100% positive feedback from users during the transition period where we could still use the old whilst evaluating the new.
Still, they're in good company - it seems to be an annoyingly common trend for developers to now adopt a policy of "if it ain't broke, make up some other excuse for replacing it with something completely new anyway". I'm an R&D engineer earning a living out of coming up with new solutions for problems, which means I'm absolutely not opposed to change where change is justified. I just hate, truly hate, this modern concept of change for the sake of change that too many developers seem to subscribe to.