3 ms·
Every time I've had to deal with troubleshooting weird firmware or hardware (and good luck sometimes knowing which it is), I've been continually amazed at the g
by kbenson 9y ago
Every time I've had to deal with troubleshooting weird firmware or hardware (and good luck sometimes knowing which it is), I've been continually amazed at the giant mess that's being pushed as commercial or "enterprise" equipment. It appears every product enters a special phase of a few weeks to a few months right before shipping where time constraints force whoever is responsible for the code to wildly shovel crap fixes into place until the hardware "works".
An alternate explanation is that most this code is written by electrical engineers that while smart, don't quite have enough experience managing larger code projects yet and are still prone to some of the newbie software developer mistakes, and probably without good mentoring on that front because those that have already weathered this storm and learned enough to sail through smoothly have either jumped ship for greener pastures or been promoted enough to be out of the trenches but not enough to have sway to fix the problem.
- bravo22 9y agoIt is definitely not lack of experience. Some of the best coders I've known have been hardcore low level EE guys. The issue is organizational priorities and available bandwidth. As soon as the product ships the core people are moved to the next project. Maintenance is done by a few guys whose job it is not to break anything. If there is something they can't fix, it goes back to the core guys who are already busy working on the new project and can only dedicate so much time to addressing this issue.