Now, I'm a "Production Support Engineer" - when the crap hits the fan, we figure out a lot of the junk ahead of time. We also write secondary support systems. We fall under Operations. If you've ever taken MIS courses, you'll see I'm a little.. misplaced. Some texts call me a "user developer".

I've been called a programmer. But not all solutions involve code. Sometimes I just have to reject a request and ask why don't they use something that exists. I.e. why install majordomo if you just want to do group mailings in the company. Just create an alias.

I've also been a Senior Software Engineer, which feels more right. I've evaluated softare systems, from bugs in the OS, minor network issues when interacting with software as well as general software architecture. Some say this is hooey... I'm just a developer or programmer. As you can see though, software engineering is not just coding. It's about building. If you supply the parts or not, that's up to you and the situation.