The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
So I have my undergrad in Accounting from a fairly well off public school (Uni of South Florida) and got my minor in Management Info Systems. After interning in a bit for a accounting and seeing the work I will be doing, I realize that I would rather slam my dick in a doorway for the next 35 years.
However, in my current job I work closely with IT occasionally and I realize thats that what I want to do. So, obviously my first step is to go back and transform that minor into a 2nd major for MIS. Then what? What sort of entry level jobs should I be looking for? Should I get any certs or something that is usually expected by the industry?
If it helps im in Tampa, which is a pretty big city and has a lot of businesses around - so hopefully I wont have a problem finding a company.
edit: If it helps, I really enjoyed my database class the most in school. So I think it would be cool to work with that if possible for an entry level position. I have a pretty good working knowledge of SQL select statements and SQL Server 2005
What is it in IT that appeals to you, or what is it in accounting that you don't think you'll be able to tolerate? I've been in IT for about 7 years now, and most of the time it's felt like what you hope to avoid in accounting (though I'd characterize it as a slow death of a thousand cuts rather than slamming my dick in a doorway). What I enjoy the most is system building and diagnosing problems that occur in complex systems, and I get to do this about 2% of the time. I spend a considerable amount of time documenting stuff, interpretting licensing agreements, and trying to convince people not to do stupid stuff.
System building is to be distinguished from "prototype building" or "proofing of concept" which is fucking horrible (at least the way we do it).
IT's a big field, and my perspective is no doubt skewed by my experience. Your post sounded to me like you're completing a track of education, and foresee a lot of boring time in the workplace ahead of you, and you've seized on IT as an interesting world in which to work. IT's no different then accounting I'm sure, once you've familiarized yourself with what you have to do there's a lot of boring application punctuated by occasional bouts of much more interesting shit. Have you talked to the IT with whom you work to get a balanced picture of what they do?
Shit, I'm thinking of quitting IT and going into catering or something.
Posts
System building is to be distinguished from "prototype building" or "proofing of concept" which is fucking horrible (at least the way we do it).
IT's a big field, and my perspective is no doubt skewed by my experience. Your post sounded to me like you're completing a track of education, and foresee a lot of boring time in the workplace ahead of you, and you've seized on IT as an interesting world in which to work. IT's no different then accounting I'm sure, once you've familiarized yourself with what you have to do there's a lot of boring application punctuated by occasional bouts of much more interesting shit. Have you talked to the IT with whom you work to get a balanced picture of what they do?
Shit, I'm thinking of quitting IT and going into catering or something.