Jobs in Computer Science/Programming

  • Thread starter Thread starter Deleted member 53669
  • Start date Start date
D

Deleted member 53669

Guest
I had a similar query on computer jobs as the IT thread, but didn't know if that thread was relevant due to the different criteria and application of CS prog.

What I'm basically looking at is a basic IT certs from the U.S. Army's Signal Corps Information Technology specialty. This will basically cram me full of all the ins and outs of cisco systems crap.

What I plan to do afterward is use my G.I. Bill to study for a Computer Science BS degree and learn some code.

Does anyone have experience on this side of the computer careers argument? Software side development and apps is what I'm routing for, and maybe even one day gaming programming.

What are my chances? Is it a dog eat dog Machiavellian profession? What do I need to know? Am I doing this right? How do I shot gun?

Should Brother None just pay me to write for GameBanshee?

If a Bear jacks off in the woods, is it a zen riddle if there are no bears in Japan?
 
you want to change from the hardware side to the software side?


the software side is much harder to get into because there is no unified vendor or set of requirements.


the next big question is what kind of programming you want to do as there are tons of different kinds.

client side of client-server
server side of client-server
standalone server
standalone client
AI
web-page
web-application
OS ( win/linux/unix/apple )
DB

there are shitloads of types of programming. and languages. different languages are better suited for different tasks.

just saying you want to get into programming just tells people you dont really know what you want to do :)

employers want to see college courses and demonstration apps showing your ability.

getting a job purely on college courses is possible, but having something to show them helps a ton.
 
Heh, I want to be at-least knowledgeable in pretty much everything

I'm not into web design though.

The type of programming that is most desirable is app creation for client AND server side.

Creating game engines is desirable.

And I am not pretending to be knowledgeable, that's why I asked.

I'm following a boyhood dream here, out of the blue.
 
I originally had intended to become a game developer but the one thing that prevented me from doing so was this:

I love video games but I realized that I did not want to spend 8-16 hours a day programming them. It sucked the joy out of the hobby I loved most.

Computer science is definitely a good place to start, they will give you a much broader foundation than a college course or a set of books. I often regret not pursuing CS instead of college. Game engine design will also likely involve a lot of heavy math courses.

Software is very diverse. I don't know if I would say it's "dog-eat-dog" but it's experience driven and you will probably start at a lot of entry-level programmer jobs that aren't that great. Experience, skill and having an interest/passion in it will take you far though. It's like anything really.
 
see, thats what i was afraid of.

applications server side and client side are totally different beasts.

they are related but have totally different and at most times opposing goals.
 
From what I understand, CS studies involve in depth theory and the tools that you use to easily learn new languages and applications, while IT is more user/client oriented; involving more business applications rather than actual foundation. This, in turn, makes the CS student more adaptable. In that light, I don't understand why you are so insistent on me having exacting goals involving programming if I want to get into it.

Does anyone actually WITH computer science experience "Besides korindabar" have an opinion?
 
check out the Cavern of Cobol on the SA forums for info if you want, you can learn a lot just by lurking in an entire forum filled with professional software developers (mostly).

I would say start trying some things and see what you like doing. If you're doing this to follow a boyhood dream you might as well do the parts that are fun to you.

Obviously you're going to have to start small.
I'd recommend picking a language (do some research first) and finish a few tutorials. Once you have the grasp of the language and its syntax, try to find some sort of graphics package and make a small game. Pong is always a fun choice.

A great way to get experience (and show off to potential companies) is to help develop a real project. There are plenty of games in development that could use a programmer (even a relative beginner).

http://forums.somethingawful.com/showthread.php?threadid=3376083
this thread could be useful if you're looking for a job (and you're a noob?)

Edit: added link, grammar!
 
I love you, thanks.

Yes, I am a noob. I have no language knowledge, but understand the basics of computing logic.


I am interested in the Job aspect concerning starving to death on a meager salary while drudging away at lines and lines of code. Or atleast keeping in mind to try and avoid that situation while I am learning from the front.
 
No problem.

It's up to you whether or not you want to start with high level or low level languages.
typically high level languages like python are easier to grasp for a beginner (python also happens to have a few incredibly easy to use graphics modules, pygame and piglet)

though, if you're already experienced with computing logic and hardware stuff, maybe you'd like low level stuff like C/Assembly? I dunno.

Python has easily been the easiest of the couple languages I've learned, and though it probably isn't going to be what you'll program AAA games in (though Civ uses it for scripting), it's great to learn basics.


Edit: forgot a crucial step, especially if you see yourself becoming a mindless code-monkey for a large company

learn how to read and understand code written by other people. Really understand it. If the person is an idiot, be mindful of what exactly they did wrong and learn from them.
If the person is a genius, try to figure out what they did.

or, if you're like me (read: really lazy), and you don't want to read tutorials, you can try to figure out how something in the language works by reading some code that exemplifies what you're trying to learn.
I remember trying to understand a small game I downloaded a while back when I was learning Python, and I basically figured out how object orientation worked just from the one program.

word of warning, if you're looking for graphic extensions. be mindful of what version of what you're installing. There are lots of modules that do not work for the most up to date version of X language.
 
Great stuff, mostly I am looking for high level at first to land a basic grunt work gigs while I am still studying the intricacies of more advanced underlying software. Prog sweat-shops are what I'm trying to avoid, I want to be in a more experimental field / Maybe self-employment related position by being a third-party software developer for other companies.

Experimentation and development is one of the biggest reasons I am pursing code/software IMHO, the theoretical construction of technology is something I want the ass end of my life to be based around.
 
))<>(( said:
From what I understand, CS studies involve in depth theory and the tools that you use to easily learn new languages and applications, while IT is more user/client oriented; involving more business applications rather than actual foundation. This, in turn, makes the CS student more adaptable. In that light, I don't understand why you are so insistent on me having exacting goals involving programming if I want to get into it.

Does anyone actually WITH computer science experience "Besides korindabar" have an opinion?

think of it like medicine.

either you can go with a specialty and be able to do one thing very well

go for a generalist and not be able to do any one thing but have an idea how everything works

problem is unlike medicine, everything is not relative.

being a network engineer does NOT mean you can become an AI programmer.

being a client-side app programmer means you could probably do a server-side app, it would not work as well as it should.

and being able to program a client side program does not mean you could turn around and write a server-side database.

programming is not relative. each has different tools and methodologies and goals.

if you spend your entire career creating single player or even client-server games, you would not have a good enough grasp to be able to step into writing programs for roles you didnt do.


im not trying to make it sound like you have to know what you are doing before you go to college.

if you dont, you are wasting your time and money.

"computer science" is not a single "field" or "specialty"

neither is programming
neither is network admin/system admin
neither is hardware architecture
 
definitely try to get a grasp of multiple languages, that'll help a lot (especially if you have to learn another one for a job, the more you learn the easier it is to learn the next one)

also with every language comes constructions and ideas that you take from it.
My old CS teacher (taught a class in Java) gave me a book on Lisp, saying that even if I don't program in it as my language of choice, just learning it will make me a far better programmer (unfortunately I've forgotten much of what I learned).

learn about common algorithms too. Some of them are cool as shit.
 
Maybe you misunderstood wesdude.

I am using a CS degree to overlap the requirements for most IT positions.

Since both involve the same functions, but at macro or micro levels, and I will have experience in both, I'm using the knowledge I gain from both to apply a generalist attitude for IT positions.

And an IT position is open for someone with IT experience and a CS degree, and I would think preferred to just a plain IT degree....Or am I wrong?

When it comes to a specialty involving code and programming, I am....as stated... routing for learning both client and server side software development, and moving into theoretical CS ideas and development.

Software knowledge on server side apps plus IT experience for an IT server admin position equals success? Or is this a false formula I am basing my logic on?
 
I think it's perfectly fine to wait before specializing anyways.
Especially if we're talking about a beginner.

Who would write a server side database before "Hello World?"
 
My basis for what I do later is basically the same as most I guess.

the ratio of Fun:Usefulness:Money

I can ask opinions on this, but I would have to stick my neck out first to know for sure.

Creativity and Fun is defiantly a factor.
 
If you want to probe getting into programming, I think the best advice one could receive is : program.

Give it a try by yourself. This is the only way to know if you'll get any fun from doing this kind of job.
Programming is all about the beauty of creating logical systems. You'll discover soon enough if that's your thing, but you won't know before you try doing it 6-8-10 hours a day.
Learn a language. Find an open-source project, start reading their code, see how things work.

Hoping that university will suddenly uncover a deep interest into this kind of things seems kind of delusory to me : you could very well discover that you want to do something else.

Wanting to make games is fine, but like korindabar said, some people do enjoy programming 8 hours a day, others just don't : if that's your case, just don't do it. Find other ways to get into game design, from other angles.
 
I study CS at the Technichal University of Vienna. Well, you shouldn't be afraid of the "Heavy Maths" and such. You should be prepared to do 6-7 hours of Java/SQl/PL-SQL/JDBC/etc. a day depending on what you're busy with at a certain semester. Be prepared to quit gaming and start programming...A LOT. Maths is the least of the problems you should be able to solve. If you wan't to get into the "Gaming Industry" you're better off studying fine arts or something like that.

and last but not least: I am not very good at programming myself, so i am having a hard time here. :(
 
))<>(( said:
Maybe you misunderstood wesdude.

I am using a CS degree to overlap the requirements for most IT positions.

Since both involve the same functions, but at macro or micro levels, and I will have experience in both, I'm using the knowledge I gain from both to apply a generalist attitude for IT positions.

And an IT position is open for someone with IT experience and a CS degree, and I would think preferred to just a plain IT degree....Or am I wrong?

When it comes to a specialty involving code and programming, I am....as stated... routing for learning both client and server side software development, and moving into theoretical CS ideas and development.

Software knowledge on server side apps plus IT experience for an IT server admin position equals success? Or is this a false formula I am basing my logic on?

a generalist CS degree is best suited for someone going into management of IT groups that do specific tasks.

believe it or not, IT and CS are very general terms that cover whole ranges of specialties. and even though your college may give you a "general" CS degree, the actual classes you take will determine in a large part what positions you are eligible for. the more programming classes you take the more people will hire you for programming jobs.

i have known 4-5 people who got general CS degrees from 4 year colleges.

1) used electives on 2 C++ classes, 2 java classes, 1 pascal class. after he graduated, he got job offers from microsoft and a company that does one-off programming projects for customers. he works pretty exclusively doing java programming for server-side unix backend programs. he tried doing some client-side but it did not work very well. constantly complains how school fucked him over by having their plan and what the actual job requires/is is completely different and now wished he had spent the extra year after getting 4 year and taking diff classes that would have helped with the job.

2) used electives for java, network design, server admin, network planning. got an entry level network engineer job. is now going back to school taking actual networking classes from cisco. constantly complains that school did not prepare him for the job and while the 4 year degree looks nice, did not prepare him at all for the reality and is having to go back to school to actually learn how to do his job.

3) spent 6 years in school got major in robotics and minor in programming. he spent the extra time in school getting the classes and experience in college to actually prepare him for his job making robots and the AI to make them work. got some assembly classes and electrical engineering classes in. barely got his 4 year degree and almost skipped entirely the 4 year degree because what employers wanted and what the school wanted were at odds for most of it. by his 5th year he had all the stuff employers wanted in, and started working and spent the last year just finishing up the reqs to get his 4 year degree.

i have known a few others and all of them complained that school never actually prepared them for the jobs they got other than #3. school is far too general unless you go in there knowing what you want and take the classes you want to get you there. very few jobs in IT actually require programming and those jobs that do programming are pretty specialized goals and aims.

yes, you can go in with a general 4 year degree in CS. yes you can take multiple electives in different areas to get your feet wet. just realize that unless you take coherent and single-line electives you wont qualify for anything other than entry level or intern positions. thats what i have been trying to impress upon you.

programming something that will run on a server and interact with clients is very different than writing something that runs on a client and interacts with a server. a lot of it has to do with "assumed technical knowledge" of the person/group using your app.
 
Ok, I understand now. Sorry about that.

So, I guess since I don't have a clue about what I want to specialize in, and certain universities have different course-ware, I was fucked before I started?
 
I get the feeling you aren't necessarily doing this for a career but for your own sake (and fun 'n stuff?). In which case I think worrying about how well your particular university will prepare you for a discipline you know little about is kind of silly.

Test the waters a little bit. Arr0nax had some good advice. It really isn't hard to get started, and once you get started, you can figure out what you want from there.

Maybe I'm stupid, but I feel like Wes is just scaring you into not trying out something you may have a passion for.
 
Back
Top