Comments on: What advice would you give to an embedded newcomer? http://www.embeddedinsights.com/channels/2011/10/19/what-advice-would-you-give-to-an-embedded-newcomer/ Shedding Light on the Hidden World of Embedded Systems Mon, 28 Jul 2014 16:18:37 -0400 hourly 1 http://wordpress.org/?v=3.0 By: Paul A. Clayton http://www.embeddedinsights.com/channels/2011/10/19/what-advice-would-you-give-to-an-embedded-newcomer/#comment-8722 Paul A. Clayton Fri, 21 Oct 2011 21:55:11 +0000 http://www.embeddedinsights.com/channels/?p=643#comment-8722 Doesn't “If it ain’t broke, don’t fix it” lead to accumulated cruft, making the system increasingly more fragile and less portable? (I understand that engineers face the seduction of perfection or "just a little bit better" which must be reined in by resource constraints, but saying no to every improvement that is not immediately necessary can also lead to frustration and failure.) Anecdotal evidence seems to point to there never being enough time to refactor, only enough time to fail at some later date (when adding a new feature or even a new usage pattern mysteriously breaks the system or a change required by the discontinuation of a part takes four times longer than expected). (Note: I am just a technophile, having no experience in embedded systems development and having written less than 200 lines of code [probably less than 100].) Doesn’t “If it ain’t broke, don’t fix it” lead to accumulated cruft, making the system increasingly more fragile and less portable?

(I understand that engineers face the seduction of perfection or “just a little bit better” which must be reined in by resource constraints, but saying no to every improvement that is not immediately necessary can also lead to frustration and failure.)

Anecdotal evidence seems to point to there never being enough time to refactor, only enough time to fail at some later date (when adding a new feature or even a new usage pattern mysteriously breaks the system or a change required by the discontinuation of a part takes four times longer than expected).

(Note: I am just a technophile, having no experience in embedded systems development and having written less than 200 lines of code [probably less than 100].)

]]> By: Eduardo http://www.embeddedinsights.com/channels/2011/10/19/what-advice-would-you-give-to-an-embedded-newcomer/#comment-8698 Eduardo Thu, 20 Oct 2011 16:27:37 +0000 http://www.embeddedinsights.com/channels/?p=643#comment-8698 Choose the right processor for the job. Unless there are tight restrictions involved, it is always better to choose an MCU or MPU that has a little bit more performance than needed, rather than one that you're not sure if will fit the project. In the same vein, prefer processor that have pin-compatible derivatives and a nice and public roadmap. On the software side, don't assume you'll never have to use an RTOS nor assume that all projects need one (this last sentence felt a little bit zen). Choose the right processor for the job. Unless there are tight restrictions involved, it is always better to choose an MCU or MPU that has a little bit more performance than needed, rather than one that you’re not sure if will fit the project. In the same vein, prefer processor that have pin-compatible derivatives and a nice and public roadmap.

On the software side, don’t assume you’ll never have to use an RTOS nor assume that all projects need one (this last sentence felt a little bit zen).

]]> By: Jon Titus http://www.embeddedinsights.com/channels/2011/10/19/what-advice-would-you-give-to-an-embedded-newcomer/#comment-8695 Jon Titus Thu, 20 Oct 2011 15:27:27 +0000 http://www.embeddedinsights.com/channels/?p=643#comment-8695 Don't give up easily. You'll find many sources of helpful information in forums, discussion groups, and on manufacturer's Web sites. Don’t give up easily. You’ll find many sources of helpful information in forums, discussion groups, and on manufacturer’s Web sites.

]]> By: D. @ LI http://www.embeddedinsights.com/channels/2011/10/19/what-advice-would-you-give-to-an-embedded-newcomer/#comment-8692 D. @ LI Thu, 20 Oct 2011 14:19:13 +0000 http://www.embeddedinsights.com/channels/?p=643#comment-8692 Aside from the technical stuff, read the book, authored by Edward Yourdon, titled Death March. Your destiny will include working on many such projects, best to quickly learn how your management is marching. Aside from the technical stuff, read the book, authored by Edward Yourdon, titled Death March. Your destiny will include working on many such projects, best to quickly learn how your management is marching.

]]>