|>>|| No. 19581
Bad coding is really prevalent in the tech world though.
I bought a radio for my car a few years ago, a Kenwood KDC-BT SD 92. It's jam packed with features and offers amazing sound quality and DSP for its original £250 price tag, so that I decided to not buy an amp since it's a compact car anyway. But the software was programmed PISS POOR. There are plenty of display bugs, the display often goes black suddenly in the middle of a song and you have to remove the detachable display module and reattach it. And sometimes, there is no sound at all, so you have to push in the tiny little reset button behind the display module with the tip of a key. After which you have to redo all your DSP and loudness, fader and equaliser adjustments and what-have-you, because the reset also resets the memory of all those settings. The same happens when you disconnect it from the battery. Either this is a genuine design flaw in the code, or they thought it would have killed them to spend an extra 35p on a flash or EEPROM-capable chip to store a few bytes of settings data on. And also, if you are browsing folders on an SD card for a song while the radio is pairing with your phone, you will get thrown out of the folder menu again with every status message during the pairing process. There were one or two software updates available during the radio's retail run, but inexplicably, you had to burn them onto a CD instead of just putting them on an SD card, after all it did come with an SD slot.
I guess with a price target of 250, something had to give and the coding had to be farmed out to Bangladesh or something, where a C programmer can feed a family off £6 an hour. But I gladly would have paid 20 quid more if that would have meant it didn't have all those coding flaws.