Skip to main content

C++ knowledge for jobs

Submitted by mongolian on

I'm only 14 years of age, and I'm very interested in taking part in the game industry, namely programming. I'd like to know how much C or C++ knowledge is needed for joining a game company (i.e. Ubisoft, id, Blizzard, etc.). I'm just beginning with C++.

Also, any clues as to which aspect of C or C++ programming I should give special attention to?

This would help very much. Thanks.

Submitted by Jacana on Fri, 11/06/04 - 6:01 PM Permalink

You want to join a company like that *grin* I would say you should expect to at least have a Bachlors degree if not a Masters degree.

One of the lead programmers at Bioware has a masters in AI - just for reference.

Submitted by Barry Dahlberg on Fri, 11/06/04 - 7:09 PM Permalink

At this stage you're probably best to make sure you work on all areas of programming until you have a solid knowledge of the basics, don't specialise to much. Later on when you are more familiar with it you might find something interests you more than anything else, or you might decide to stay as a general purpose coder.

You will need a pretty solid understanding of programming to get into the industry, most have a degree of some kind though it's not strictly necesary. To get started I'd find one of the popular game programming libraries on the net (Allegro, SDL etc) and work on making a very simple game (very simple, eg pong), try to finish it to a level where you are proud to show it, and your source code, off to others.

Don't be afraid to ask silly questions and listen to peoples advice, most of all, have fun!

Submitted by Daemin on Fri, 11/06/04 - 10:58 PM Permalink

Yeah, I would say just try and learn the basics of Programming, not necessarily of C/C++. Programming is a wide field, with many different languages out there, and Games programming now is using more and more different languages. C and C++ is pretty much the standard, but some games are using Java (on the Mobile Phone market), Python, Lua and other scripting languages are being used for game scripting, and then there are the numerous shader languages that a programmer might need to learn.

So I say stick with it, but learn the general stuff while you're young, man you've got at least 3-4 years until you finish high school, and a lot can change in that time. I've known people that did C programming and were totally into computers back then, and now they're stricly musicians, playing all over the place and basically doing nothing with computers or programming. Things will change so don't take a career path too seriously at the moment.

Submitted by WiffleCube on Thu, 05/08/04 - 2:58 PM Permalink

Seven pointers from a Big Kid to a Slightly Less Big Kid ;)

1. Try and concentrate on maths and physics in class, and indeed
don't let your schoolwork slide. The 'war games' days where you
could do that and have a job lined up disappeared some time ago.
2. Set yourself very simple C/C++ projects that work; each one will
boost your self-esteem as a programmer.
3. Get a textbook on algorithms, browse around the store for
one that you like. Make yourself classes for lists and trees etc.
4. Watch out for code guilt when you get bugs, a common complaint
in programmers!
5. Remember by the time you're out there programming the landscape
will have changed dramatically, so don't specialise in a current
technology early. Keep it general.
6. Have a play with gmax (it's free) for designing 3D graphics, and UnRealEd for designing levels.
7. When you do play games, try and develop a critical eye as to how you would code the behaviour you see in the game.

WiffleCube

quote:Originally posted by mongolian

I'm only 14 years of age, and I'm very interested in taking part in the game industry, namely programming. I'd like to know how much C or C++ knowledge is needed for joining a game company (i.e. Ubisoft, id, Blizzard, etc.). I'm just beginning with C++.

Also, any clues as to which aspect of C or C++ programming I should give special attention to?

This would help very much. Thanks.

Submitted by Barry Dahlberg on Thu, 05/08/04 - 7:44 PM Permalink

quote:Originally posted by WiffleCube
4. Watch out for code guilt when you get bugs, a common complaint
in programmers!

Code guilt?

[?]

Submitted by WiffleCube on Sat, 07/08/04 - 7:28 AM Permalink

quote:Originally posted by Barry Dahlberg

quote:Originally posted by WiffleCube
4. Watch out for code guilt when you get bugs, a common complaint
in programmers!

Code guilt?

[?]

Code guilt I think was mentioned in a S.E book by Pressman; it's basically when you are feeling guilty that your code has bugs in it.
The aphorism (Goethe) "Failures are portals for success" generally works for me!

Submitted by Kalescent on Sat, 07/08/04 - 11:32 AM Permalink

To throw my 2 cents into the fray from a different perspective.

I have a diploma of IT specialising in Games programming from QANTM. Now, not for a second do i consider myself a 'programmer' nor do i choose to persue that path - BUT as an artist i found it possibly more valuable to me than the artist diploma ( as we basically mixed in with each other anyhow )

Yes I can dabble with c++ - and from scratch with a blank sheet of paper, i wrote my 'hippy pong' a psychadelic funky hypnotic pong with multi coloured almost neon balls a very bright soundtrack and sound effects. I had alot of help - but the satisfaction of being able to use what i was taught - to start with a blank sheet of paper and NO reference material and create a finished game was for me an achievement im proud of.

My experience was valuable - i got to sit down and see the reasons right there why i needed to stick to restrictions, why i need x bones per vertex, why i needed to reset the xform, why i needed to stl check my models to check for open edges and other artifacts.... the list goes on and on.

I got to experience the problems that arise from any small details that are often overlooked by artists, and experience how frustrating they can be to fix.

This has almost no relevance to this thread, but if anything for such a young guy - just 14 [:D] if i could hope for you to take anything away from the ramblings of an old man, it would be simply to take the time to experience what it is that you are doing.

And learn as much as you can, about what it is you want to do. Dont specialise too soon - learn about GAMES, youll eventually 'fall' into a groove that youll like. [:)]

Posted by mongolian on

I'm only 14 years of age, and I'm very interested in taking part in the game industry, namely programming. I'd like to know how much C or C++ knowledge is needed for joining a game company (i.e. Ubisoft, id, Blizzard, etc.). I'm just beginning with C++.

Also, any clues as to which aspect of C or C++ programming I should give special attention to?

This would help very much. Thanks.


Submitted by Jacana on Fri, 11/06/04 - 6:01 PM Permalink

You want to join a company like that *grin* I would say you should expect to at least have a Bachlors degree if not a Masters degree.

One of the lead programmers at Bioware has a masters in AI - just for reference.

Submitted by Barry Dahlberg on Fri, 11/06/04 - 7:09 PM Permalink

At this stage you're probably best to make sure you work on all areas of programming until you have a solid knowledge of the basics, don't specialise to much. Later on when you are more familiar with it you might find something interests you more than anything else, or you might decide to stay as a general purpose coder.

You will need a pretty solid understanding of programming to get into the industry, most have a degree of some kind though it's not strictly necesary. To get started I'd find one of the popular game programming libraries on the net (Allegro, SDL etc) and work on making a very simple game (very simple, eg pong), try to finish it to a level where you are proud to show it, and your source code, off to others.

Don't be afraid to ask silly questions and listen to peoples advice, most of all, have fun!

Submitted by Daemin on Fri, 11/06/04 - 10:58 PM Permalink

Yeah, I would say just try and learn the basics of Programming, not necessarily of C/C++. Programming is a wide field, with many different languages out there, and Games programming now is using more and more different languages. C and C++ is pretty much the standard, but some games are using Java (on the Mobile Phone market), Python, Lua and other scripting languages are being used for game scripting, and then there are the numerous shader languages that a programmer might need to learn.

So I say stick with it, but learn the general stuff while you're young, man you've got at least 3-4 years until you finish high school, and a lot can change in that time. I've known people that did C programming and were totally into computers back then, and now they're stricly musicians, playing all over the place and basically doing nothing with computers or programming. Things will change so don't take a career path too seriously at the moment.

Submitted by WiffleCube on Thu, 05/08/04 - 2:58 PM Permalink

Seven pointers from a Big Kid to a Slightly Less Big Kid ;)

1. Try and concentrate on maths and physics in class, and indeed
don't let your schoolwork slide. The 'war games' days where you
could do that and have a job lined up disappeared some time ago.
2. Set yourself very simple C/C++ projects that work; each one will
boost your self-esteem as a programmer.
3. Get a textbook on algorithms, browse around the store for
one that you like. Make yourself classes for lists and trees etc.
4. Watch out for code guilt when you get bugs, a common complaint
in programmers!
5. Remember by the time you're out there programming the landscape
will have changed dramatically, so don't specialise in a current
technology early. Keep it general.
6. Have a play with gmax (it's free) for designing 3D graphics, and UnRealEd for designing levels.
7. When you do play games, try and develop a critical eye as to how you would code the behaviour you see in the game.

WiffleCube

quote:Originally posted by mongolian

I'm only 14 years of age, and I'm very interested in taking part in the game industry, namely programming. I'd like to know how much C or C++ knowledge is needed for joining a game company (i.e. Ubisoft, id, Blizzard, etc.). I'm just beginning with C++.

Also, any clues as to which aspect of C or C++ programming I should give special attention to?

This would help very much. Thanks.

Submitted by Barry Dahlberg on Thu, 05/08/04 - 7:44 PM Permalink

quote:Originally posted by WiffleCube
4. Watch out for code guilt when you get bugs, a common complaint
in programmers!

Code guilt?

[?]

Submitted by WiffleCube on Sat, 07/08/04 - 7:28 AM Permalink

quote:Originally posted by Barry Dahlberg

quote:Originally posted by WiffleCube
4. Watch out for code guilt when you get bugs, a common complaint
in programmers!

Code guilt?

[?]

Code guilt I think was mentioned in a S.E book by Pressman; it's basically when you are feeling guilty that your code has bugs in it.
The aphorism (Goethe) "Failures are portals for success" generally works for me!

Submitted by Kalescent on Sat, 07/08/04 - 11:32 AM Permalink

To throw my 2 cents into the fray from a different perspective.

I have a diploma of IT specialising in Games programming from QANTM. Now, not for a second do i consider myself a 'programmer' nor do i choose to persue that path - BUT as an artist i found it possibly more valuable to me than the artist diploma ( as we basically mixed in with each other anyhow )

Yes I can dabble with c++ - and from scratch with a blank sheet of paper, i wrote my 'hippy pong' a psychadelic funky hypnotic pong with multi coloured almost neon balls a very bright soundtrack and sound effects. I had alot of help - but the satisfaction of being able to use what i was taught - to start with a blank sheet of paper and NO reference material and create a finished game was for me an achievement im proud of.

My experience was valuable - i got to sit down and see the reasons right there why i needed to stick to restrictions, why i need x bones per vertex, why i needed to reset the xform, why i needed to stl check my models to check for open edges and other artifacts.... the list goes on and on.

I got to experience the problems that arise from any small details that are often overlooked by artists, and experience how frustrating they can be to fix.

This has almost no relevance to this thread, but if anything for such a young guy - just 14 [:D] if i could hope for you to take anything away from the ramblings of an old man, it would be simply to take the time to experience what it is that you are doing.

And learn as much as you can, about what it is you want to do. Dont specialise too soon - learn about GAMES, youll eventually 'fall' into a groove that youll like. [:)]