Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] Programming vs Engineering



On Jan 22, 2012, at 12:06 PM, Robert Krawitz wrote:
> 
> This analogy is wrong.  It isn't construction workers, but people who
> participate in the design of a bridge.  They don't all need to be PEs; a
> PE ultimately may have to sign off on their work (at least for public
> infrastructure), but that's it.

No, this is the heart of the matter.  Mechanics are not Mechanical Engineers.  Electricians are not Electrical Engineers.  Bricklayers are not Civil Engineers.  They are all skilled tradesmen but they are not Engineers and they typically are not part of the design process.  That isn't their expertise.

We don't expect mechanics to know how to design a supertanker.  We don't expect electricians to know how to design a power grid.  We don't expect bricklayers to know how to design a skyscraper.  But programmers -- people who's expertise is writing code -- are expected to design programs.  Or, to turn that around, people who's expertise is designing programs are expected to spend more time writing code than getting the design right.  I think that this is a major factor in why so many applications, especially embedded applications, are such wrecks.

--Rich P.





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org