Slashdot Mirror

← Back to Stories (view on slashdot.org)

Are Programmers Engineers?

Posted by timothy on from the let-the-french-academy-decide dept.

The Llama King writes "The Houston Chronicle has an interesting story about a debate in the Texas Legislature over whether programmers are really engineers. A quote: " 'It's one of the silliest issues we're having to deal with this session, but it's also one of the most important,' said Steven Kester, legislative director of the American Electronics Association, an organization of computer companies." Are you really an engineer? Or just a code-monkey?"

4 of 963 comments (clear)

  1. Depends by menasius · · Score: 5, Insightful

    I think there are three types of people who program.

    Code-Monkeys: these guys do exactly what they are thought to do: Grind out code. Usually not innovative, usually no technical achievement. Nevertheless, they'll get the job done especially if its something that they can base off other things.

    Computer Scientists: These guys use code to test new ideas and methods. This is the research side, but its not always practical research. An analogy I can make is you can't a bridge without math but advanced number theory really doesnt make better bridges.

    Computer Engineers: These are the practical counterparts to somputer scientists. Usually innovative but in a sense that they comstruct useful things. What an engineer makes a code-monkey will be able to replicate soon. Just like it takes an engineer to design an engine, but Joe-mechanic can rebuild one or even "modify" it to get some use out of it.

    I dont want to put a negative spin on any of these as they all serve their purpose in my mind. Perhaps you will dis/agree.

    cheers

    -bort

    1. Re:Depends by Arandir · · Score: 5, Insightful

      I'm definitely a Software Engineer. Not only does my job title say so, I do the work of one. I am NOT a code monkey. 90% of my time is spent on requirements, specifications, design,validation, verification, and reviews. Excepting the calculus and state licensing, I do the same things an engineer in any other field does.

      Unfortunately the upper management is full of people who don't understand that. They think we're still code monkeys and think I'm being sarcastic when I give them an estimate of 6-8 weeks for a bug fix.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
  2. Don't Water Down "Engineer" by jeramybsmith · · Score: 5, Insightful

    The term "engineer" has already been besmirched by Novell and Microsoft. Lets not water it down futher. The answer is simple. Someone with a computer engineering degree from a 4 year university is an accredited engineer. Someone with an IS, IT, MIS, ITM degree is _not_ an engineer. Sorry but if you wanted to be an engineer, you should have studied engineering. Someone who drops out of college and learns VB or perl or something is not an engineer. The term engineer implies some form of accreditation. I applaud Florida who makes it illegal to expand the term "MCSE" on a resume or in a business letter unless you are an actual engineer.

    --
    Never overestimate the end user. -jeramy b. smith
  3. Re:Dubya by Dark+Nexus · · Score: 5, Insightful

    It's a simple matter that in most areas, engineers are liable (criminally liable in cases) for a failure of anything they've signed off on.

    Would any MCSEs be willing to be liable for problems in their code? Open to lawsuits for failures, regardless of any EULAs?

    There's a reason for laws like this, and that's because of the legal responsibility and liability that comes with being an practicing engineer.

    --
    Dark Nexus
    "Sanity is calming, but madness is more interesting."