Hacker News new | ask | show | jobs
by FigBug 4111 days ago
I've been working at home for the last 5. Doing iOS, android, desktop apps and firmware. I find the firmware the most frustrating, probably because I'm the least experienced at it. Trying to debug things by sharing screenshot of a USB scope is a pain. Having to drive in every time I need a mod done. Even worse is driving in and whatever piece of equipment I wanted is at somebody else's house (or forgotten at mine).

I've had a better experience when doing firmware upgrades for mature products, but has anybody had a good experience developing hardware products with a work from home team?

1 comments

The IHV that I worked for had most of the hardware team local in California, and most of the software team remote. We had a great lab team that could install bits, move cables, etc. All machines had serial consoles & power controllers (or IPMI). One source of frustration was that most of the locals did not arrive until 10am Pacific, and I was on the Eastern time zone. So if I needed a cable moved, I had to wait until after lunch. Though I sometimes asked one of the secretaries to do it (she arrived at 6am Pacific).

By the time I had hardware access, we always had jtag or more advanced access methods working.

A big frustration was using tools like PCIe logic analyzers remotely. Luckily, these were mostly controlled by PCs, and we could access them via an IP KVM solution (but again, we had to wait for on-site labstaff to hook up physical connections).