Slashdot Mirror

← Back to Stories (view on slashdot.org)

Embedded Developer's Survival Guide, 2005

Posted by timothy on from the don't-put-your-fingers-on-the-grindstone dept.

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. Re:summary by DrZombie · · Score: 2, Informative

    A browse through McConnell's "Code Complete" gives a fairly good synopsis of why a lot of projects fail, and it usually has to do with upstream work. Business requirements, system requirements, architecture. These things all have huge impacts further down the line, especially when they have problems. The cost analysis in the book is enough to scare any managers with an ounce of sense into putting some more work in at the front of the project. On another note, I'm curious how to get into the embedded development field. I have a degree in CS and a lot of work experience writing software systems, just not in that area.