[SGVLUG] Embedded Software position

Emerson, Tom (*IC) Tom.Emerson at wbconsultant.com
Fri May 29 17:05:55 PDT 2009


-----Original Message----- Of Kathy Magel

I'm a recruiter working with a leading developer of image processing and security identification systems ... full-time position responsible for the development and enhancement of a wireless, hand-held device used by military and law enforcement personnel.
=========================================

Hi Kathy - sounds like an interesting job (and an intersting moral delima - after all, it's not a question of whether or not you want "big brother" to be watching you in the first place -- that's pretty much a given at this point -- but the question now is "do you want BB watching you with open or closed products?") (*)

In fact, I think that could lead to a lively discussion and/or presentation (if your client is willing) on the state of surveilance and security with respect to "open source" ideals and products.

Tom

(*) arguments can be made on both sides, and some of the arguments are along the lines of "submarine patents" - i.e., waiting for the results of a closed application to convict "the wrong guy", and therefore push to reveal the underlying code and in order to invalidate all past, current, and possibly future "convictions" based on results of the analysis of the proprietary device.  Case in point: the source code for a breathalyzer was recently subpoenaed and examined/reviewed - the result of the study included notes like this:

   " Base One, however, did an extensive evaluation, finding 19,400
potential errors in the code.

Among its findings are:

      1. The Alcotest Software Would Not Pass U.S. Industry Standards for
Software Development and Testing: The program presented shows ample evidence
of incomplete design, incomplete verification of design, and incomplete
"white box" and "black box" testing. Therefore the software has to be
considered unreliable and untested, and in several cases it does not meet
stated requirements. The planning and documentation of the design is
haphazard. Sections of the original code and modified code show evidence of
using an experimental approach to coding, or use what is best described as
the "trial and error" method. Several sections are marked as "temporary, for
now". Other sections were added to existing modules or inserted in a code
stream, leading to a patchwork design and coding style.

[and so on...]
[full details here: http://www.dwi.com/new-jersey/state-v-chun/]
[and .pdf here: http://www.nj-dmv-dwi.com/pdf/DRAEGERALCOTEST7110MKIII-C.pdf]



More information about the SGVLUG mailing list