3 ms·
Well, if it's a one-track project, estimates can be treated casually. However, I spent the majority of my career at hardware manufacturers, where software was
by ChrisMarshallNY 4y ago
Well, if it's a one-track project, estimates can be treated casually.
However, I spent the majority of my career at hardware manufacturers, where software was actually kind of an "annoying extra requirement" (I'd like to think that's changing, these days, but not so sure. Contempt for software seemed to be a fundamental pillar of hardware engineers).
Our projects were always done by fairly massive, interdisciplinary teams, and everything had to "sync up," at the correct time. If the hardware would be ready at a certain date, the host drivers needed to be ready then, because the SDK people and the QC team needed them, etc.
And even though engineers love to rag on marketing, they have to have very complex projects, to generate buzz, advertise, ship, distribute, etc. Hardware is a lot more difficult to distribute than software.
Also, Quality was really important. A recall of hardware is a nightmare. Sometimes, we could be heroes, and save customers from hardware defects (like having an image processing filter to correct some chromatic aberration). Other times, we could brick the unit, or wipe out customer systems (I once wrote a SCSI driver that wrote to sector zero on hard disks -oops).
Estimates -not just software estimates- were critical.