Slashdot Mirror


Embedded Developer's Survival Guide, 2005

An anonymous reader writes "LinuxDevices has published the full keynote address delivered at the Embedded Systems Conference 2005 by Wind River CEO Ken Klein. The hardnosed speech presents a five-point action plan for device software developers who are interested in keeping their jobs -- as opposed to becoming "roadkill," as Klein puts it. The speech is decidedly short on warm fuzzies, but does offer a few practical considerations for engineer job survival in the post-recession era."

1 of 19 comments (clear)

  1. summary by klossner · · Score: 4, Insightful
    It's all pointy-haired boss stuff. Starts out with an incorrect premise:
    We [engineers] don't do development well: More than half of embedded designs are completed 3-4 months behind schedule; 24 percent -- nearly a quarter -- get cancelled
    In my twenty-mumble years of engineering, pretty much every time these problems have occurred it's because the requirements were changed in mid-project. Often for excellent reasons, but the consequences do not reflect an engineering deficiency.
    Don't write new code, leverage existing software. Buy it from us.
    Hardly unexpected.