Just an Update as this thread was originally my questions about majoring in CS. I am now a Junior and will hopefully graduate in a year or so.This is probably the wrong forums but I will give it a shot. The reason I put it here because my questions are for people who code/develop specifically.
Basically I am returning to college this summer to pursue a degree in computer science. I'd like to use it to one to develop games and/or software post graduation. The problem I foresee is job outlook. Most of my friends who majored in comp sci are all IT. None of them actually code. According to some statistics (Occupation Profile - America's Career InfoNet) its a growing job that pays pretty well. Ofc there are other software jobs, I am just using this as a quick example. The website makes it seem like there are tons of these jobs out there but everyone I talk to works IT. Here are a few questions I have for those who do code for a living and/or majored in comp sci.
Does this pay scale seem accurate (average pay $40+ an hour)?
Besides a degree, do i need experience or some kind of portfolio to really get a good coding job?
I am willing to relocate, so location is not a problem but did you guys have a hard time finding a job?
Any suggestions? I am usingO*NET OnLinefor research on the various jobs in programming and development.
Just a quick FYI i have about 90 semester hours already. I was majoring in Physics before I took a break from school to let my wife finish. Money is not a problem. I have a full ride to my degree via Gi Bill. Thanks!
Thats a silly way to look at one of the most important classes to computational thinking.other stupid shit.
I found the class really boring and useless personally, that's all.Thats a silly way to look at one of the most important classes to computational thinking.
Right, but it's important to know which tool to use for the job. For example, a fellow developer was using a List and, before adding to it, would iterate over it to make sure the object wasn't already added. It didn't occur to him, or he wasn't aware of, to simply use a HashSet.Depends on real-world. In a real world you'll pretty much never have to write your own data structure and the algorithms to traverse it. Basically any flavor of Map, Set, List, Tree is already implemented somewhere for you.
Its why i called it an important class in "computational thinking" not in using data structuresDepends on real-world. In a real world you'll pretty much never have to write your own data structure and the algorithms to traverse it. Basically any flavor of Map, Set, List, Tree is already implemented somewhere for you.
I mean that is really just knowing Collections 101. I'm not sure if a data structures class would help that. You could pretty much explain the purpose of when to use a Set, Map, List, Queue in less than an afternoon.Right, but it's important to know which tool to use for the job. For example, a fellow developer was using a List and, before adding to it, would iterate over it to make sure the object wasn't already added. It didn't occur to him, or he wasn't aware of, to simply use a HashSet.
Hmm I did that last semester. Our last data structures were Binary Search Trees and Heaps. Balancing BST screwed me up for a bit because trying to follow multiple recursive methods was just nerve racking. Right now I could not balance a BST without looking some stuff up. Probably the only data structure we went over last semester that I couldn't write without references right now. Like I said though, I think this class is more of the theory behind them. Probably more time complexity calculations. I just picked up the book an hour ago so well see.Depends on real-world. In a real world you'll pretty much never have to write your own data structure and the algorithms to traverse it. Basically any flavor of Map, Set, List, Tree is already implemented somewhere for you.
So a freak in the sackActually, yes. But super introvert, gothy (hates xmas, loves halloween and I'm convinced she doesn't have clothes that don't follow a monochromatic scale), and is a cat lady (by accident, took in a pregnant stray, but still kept them).
Weird chick who is crazy in bed. Who thought Khane would find love in the comp sci thread?So a freak in the sack
The class is big on efficiency (big O, etc)Hmm I did that last semester. Our last data structures were Binary Search Trees and Heaps. Balancing BST screwed me up for a bit because trying to follow multiple recursive methods was just nerve racking. Right now I could not balance a BST without looking some stuff up. Probably the only data structure we went over last semester that I couldn't write without references right now. Like I said though, I think this class is more of the theory behind them. Probably more time complexity calculations. I just picked up the book an hour ago so well see.