<p>u<em>u</em>d, I don’t really agree with your definition (and I have experience with at least 25 different companies as an employee or consultant in the computer area). The lines are very gray for usage of those terms. I just don’t want the OP to think that he has this down if he just takes your post at face value, because he would be confused if he tried to apply that at many of the companies I have worked with…</p>
<p>I have never worked for a company that split those two into different departments, at least in the global sense. Generally a company has one technology department (reporting up to the CIO in most cases, but the CFO in some companies). It can be called a variety of things (Information Systems, Information Technology, Technology Group, etc. – if you can think of it, someone has called it that!). Within that group below the top level, then there is generally a split between application support and infrastructure (like network, information security, database management, etc.). The application support does tend to have more interaction with the business areas.</p>
<p>Programming positions exist in many types of companies; certainly those that develop and sell software, but there are still a lot of companies that “roll their own” and write (or maintain) their own code. Or they buy packages, and modify the heck out of 'em, which requires coders. And you are right that there are plenty of people on the infrastructure side that don’t create code, but do scripting and configuration.</p>
<p>You can still manage coders with a business background. But it helps a ton if you were a coder at some point in your career, you will be a much better manager even if the technology has changed. Some companies are willing to take a business major who has some kind of computer related minor on in a coding or technical position so you can get that experience.</p>