Quote:
Originally Posted by Mr. Goodbar
I'm not sure there is enough forum space for that level of precision  I think your comments were very clear in the context of the discussion. As a past and current software industry executive, there are always bugs if the application does anything relevant or useful  |
There's an awful lot of tech geeks in the room here. I think I count at least 3-4 people who claim to be part of the software industry (not including myself, so that makes 4-5).
And the point you bring up gets worse the more hands you have in the pot. In practically all eReaders on the market, you have some variant of Linux. Then you have Adobe's SDK on a chunk of them too. And then in the case of the nook, you have Google's GUI render and other bits on top of Linux... and then you have B&N's code.
So not only is B&N responsible for working on their own code, but they are likely responsible for understanding Google's code and fixing it if needed, as well as finding patches/etc for the Linux code. And if there's a bug in the Adobe SDK? Well, you just gotta work around that. It's a mish-mash.
I know when I first got hired by the company I work at, it took nearly 6 months for me to get familiar with the code that my team worked on that was already written. It took a year before I was nearly as productive as the rest of the team. Software development on this scale (even for such a small and 'simple' device) is maddening at times at just how much can go wrong, and no one person will ever understand it all.