I knew when I submitted the article I'm An Idiot... (And Other Lessons From The IT Department) to slashdot I'd get a reaction. I was prepared for sarcasm, vitriol, and anger. And I got it. I got a lot of it.

Some readers agreed with me, others, not so much; some comments were funny, others simply asinine. But there were several common themes that warrant a reply. After all, I started this.

"You've never worked in IT, so you don't know that it's like."
Actually, I have worked in IT. I was a software developer for five years, then moved into management (cue the slams on IT management in 3...2...1...NOW!). I spent 10 years in the field. I worked late evenings and weekends, fixed plenty of user mistakes, and experienced the same frustrations as many of the people who posted their comments. I do know what I'm talking about.

"How dare you tell me I'm not a professional!"
People were divided on this one. Some argued IT wasn't a profession; others took great offense at that very suggestion. Most of the e-mails I received were from people who felt that by questioning the profession, I was questioning their professionalism. Fair enough, but that wasn't the argument I was making.

The Federal government provides a very clear definition of a "profession" (these criteria are examined in much more detail by author Steve McConnell). Among other things, a profession must :

  Have a requirement for extensive training,

  Have a code of ethics imposing a high standard,

  Have A disciplinary process for violators of the code,

  Have a requirement that practicioners be licensed.

The debate about whether IT is a profession turns on the fact that some of these criteria don't apply to the field today - especially the last two items. While there may be certain jurisdicitions where licensing is required, there's nothing in IT that's equivalent to an engineering, medical or teaching certification. Given the critical role IT plays in society, I believe there should be.

---