2 ms·
Or their hardware, some of the impact of those bugs could be built into the physical hardware. By that point. Edit:fixed a typo.
by emeraldd 8y ago
Or their hardware, some of the impact of those bugs could be built into the physical hardware. By that point.
Edit:fixed a typo.
- ethbro 8y agoAdd in qualification of specific hardware inside specific operating conditions. The "move stuff and break stuff" crowd forgets there's a market for "move slow and rarely break stuff" too. So if you have qualified hardware w/ a certain driver version, you don't just ship a bunch of code fixes to a customer, you ship the bare minimum change set required to fix any specific issues they experience. Because you're sure as hell not recertifying every part revision with every driver version.
- civilitty 8y agoI am definitely not one of those "move fast and break stuff" people, especially since I often have only a few months to design something that is expected to be in service until oxidation is a legitimate concern. My personal ventures are largely web based so I've also become rather too personally acquainted with the other extreme - the madness that is node_modules/, implicit *.d.ts imports, and browser impedance mismatches. The problem in the hardware industry is far more insidious. Unlike with software dev, there is no concept of "full stack" or "devops" in manufacturing. The entire field is so hyperspecialized that youve got people dedicated to tuning reflow temperatures to +-5C depending on humidity and local weather. No one person can have a proper big picture view of the situation so the entire industry is dominated by silos each with their own micro-incentives and employees competing with each other for notoriety.