Hacker News Reader

>Another way of describing this is that the non TDD teams weren't actually done when they shipped.

Was ANY code, TDD or not, ever "done" when it shipped?

Absolutely. Off the top of my head, the first thing that comes to mind are video games that were shipped on ROM cartridges. Bugs or not, when shipped, it's done.

Those days are long gone. Even in an deeply embedded world like automotive or AV equipment, code is (or can be) frequently updated.

In the very deeply embedded world, there are often no update mechanisms, period.

Possibly pacemaker firmware? I have no real knowledge of the subject, but I'm guessing it'd be kind of risky to equip a pacemaker with Bluetooth to accept over-the-air firmware updates.

There were headlines in 2012 about pacemaker vulnerabilities. Apparently, they could be commanded to deliver an 830 volt shock, probably fatal, by someone with a laptop nearby.

You'd probably be right about the risk. But a buddy of mine has a pacemaker, and the version he has now allows wireless updates and tuning. It's possible that a firmware update still requires direct access, but it's possible it's wireless.

Of course, you'd better be darn sure the update works (firmware updates always scare me a little, never mind on a pacemaker!)

Reply on news.ycombinator.com