Skip navigation
Help

Software development process

warning: Creating default object from empty value in /var/www/vhosts/sayforward.com/subdomains/recorder/httpdocs/modules/taxonomy/taxonomy.pages.inc on line 33.

For novel ideas about building embedded systems (both hardware and firmware), join the 25,000+ engineers who subscribe to The Embedded Muse, a free biweekly newsletter. The Muse has no hype, no vendor PR. It takes just a few seconds (just enter your email, which is shared with absolutely no one) to subscribe.

Embedded systems are typically so complex, with so many
interrelated components, each of which must be perfect, that practically anyone
can do an very effective job of botching a development project.

 Still, it's instructive to examine some of the
habits of the most defective engineers, some of whom have honed dysfunctional
development to a high art.

 It's important to understand the dynamics of
embedded systems: promise the world, start writing code, and let the project
fall completely apart. There's no penalty for non-performance! As the
deadlines draw near, and then pass by, and then fade away as old forgotten
memories, your employer will have so much vested into you and the project
there's no chance you'll be disciplined, no matter what bizarre work habits
you display.

 In fact, a few carefully placed comments about
greener pastures may result in winning a bonus from your panicked employer!

 So, here are a few ways of maximizing your job
security through proper dysfunctional design and management of your next
embedded project.

0
Your rating: None

Stack Exchange

This Q&A is part of a weekly series of posts highlighting common questions encountered by technophiles and answered by users at Stack Exchange, a free, community-powered network of 90+ Q&A sites.

lurkerbelow is the only developer at his company writing unit tests. Management, developers, everyone says they want to write unit tests, but nobody does. To bring developers into line, lurkerbelow has introduced pre-commit code review (Gerrit) and continuous integration (Jenkins). Not working. "How do I motivate my fellow coworkers to write unit tests?" he asks.

Practical deomonstrations help

jimmy_keen Answers (32 votes):

Read 22 remaining paragraphs | Comments

0
Your rating: None