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 | Blog | 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



Allow me to join your rant Richard, with minor adjustments.
Yes, undoubtedly the word " Engineer " is easily and cheaply used in the
software and IT world, but some folks in the software world do justify
the title. People that take nothing, or close to nothing and make a
working system out if it . (builder(s) of Unix, the C language, The Perl
language ,Cisco IOS - the actual writers, to name a few), pardon my lack
of name memory,those distinguished folks did earn the title "Engineer"
in my book. With that said, it will be better for all if the word
Engineer would be used with more caution.

Guy Gold


On Sat, 2012-01-21 at 16:37 -0500, Richard Pieri wrote:
> On Jan 21, 2012, at 1:39 PM, Mark Woodward wrote:
> > 
> > Does anyone have any comment?
> 
> Yeah, but it's more rant than anything else.  You've been warned.
> 
> 
> The title "Engineer" has a specific, legal meaning.  Professional use of the Engineer title requires rigorous education, testing, internship and licensure.  None of these exist for professional programmers.  Therefore, there are no Professional Software Engineers, regardless of what is on our business cards[1].  All of this also applies to the "Architect" title.  Architects have similar education and testing requirements to Engineers, and like Engineers they must be licensed to practice professionally.  Use of the Engineer and Architect titles for computer specialists is nothing more than aggrandizement.
> 
> In my book, your exemplar "good software engineer" is really a good programmer, and your "good programmer" is anything but good.  He is terrible.  He'll write "correct", "clean" code that will be five to ten times slower than the good programmers' painstakingly optimized code.  Then he'll go and rewrite their code to "clean it up" to match his own and check it in without telling anyone.  Then the next release candidate suffers catastrophic performance problems and a mad scramble to figure out why ensues.  Someone at a previous job of mine did this, and the senior management was not amused.  Bad programmer, no biscuit.
> 
> Rant off.
> 
> [1] My title at my last gig was "Senior Systems Engineer".  I hated that title and I hate putting it on my resume because it is a lie.  I'm no Engineer.
> 
> --Rich P.
> 
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://lists.blu.org/mailman/listinfo/discuss





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