Main > Everything Else

I hate my job and want to switch rant

<< < (21/26) > >>

Wade:
Chad, you expect too much of an MIS degree.  I wouldn't expect an MIS grad to know the first thing about database or programming.  When I was working on my undergrad, the MIS students only had to take 2 or 3 programming classes, and those were Cobol.  The CS students had to take a lot more difficult and "nuts and bolts" types of programming classes, and the majority of them took a lot of "special topics" classes that covered things like VB, VC++, Java, etc.

Essentially... the MIS were the folks didn't have the capacity or courage to get through the CS program (and the 30 hours of math scared off a lot of folks).  Interestingly, it was rare to see an MIS student in the Comp Sci special topics classes.  Your school may vary, and things might be different today, but it was a very obvious line at my school.  There was the same line between the engineers and the printers (most who went into printing admitted it was because it was easy).

Wade

ChadTower:

--- Quote from: Wade on February 15, 2008, 02:48:20 pm ---Chad, you expect too much of an MIS degree.  I wouldn't expect an MIS grad to know the first thing about database or programming. 

--- End quote ---

Knowing the difference between a single user app and an enterprise level app, specifically the local execution architecture vs a client/server architecture, is well within the MIS program.

MIS programs are much more involved now than they were ten years ago.  Much deeper.  They wouldn't be of any use in today's multilayered architectures the way they used to be.

ChadTower:
EDIT:  eh, forget it, it was a good post but I have too much to do this afternoon than waste time while jim argues a profession he hasn't been in with people who have been in it a long time.

shardian:
Yeah, you computer nerds are speaking greek to me right now. ;) ;D :P

zaphod:

--- Quote from: pinballjim on February 15, 2008, 02:58:34 pm ---There's a world of difference between the application design process and the actual coding of it.  It's two completely different skill sets and generally two completely different personality types.  A computer science major comes out knowing lots of technical information but absolutely nothing about business processes or needs, unless they took some electives.  A MIS major comes out knowing basic business principles, application design, and some soft skills on the actual coding... unless, again, they took some electives.
 

You hire a compsci guy to write code.  You hire an MIS guy to develop software, meet with users, and manage the programmers. (there, look, I got a dig in, too ;D )




--- End quote ---

I do both, the complete design, and all programming (in whatever language/db is best suited).  Because of the variety and say in how projects develop and turn out, I love my job.  A grunt coding job would not be fun for me.

I should state I have a 'Masters in Information Systems' not an Undergrad MIS degree (undergrad is actually double major Business Admin/Comp Sci).  I do expect a graduate degree MIS applicant to know quite a bit more about business processes out of the gate than I would a 4-yearer.

Oracle, IBM's DB2 and MS's SQLServer aren't really "niche" databases, IMO.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version