Mail Archives: djgpp/1997/08/14/20:17:15
On Wed, 6 Aug 1997 13:35:31 +0100, Kris <jan AT wishingtree DOT demon DOT co DOT uk>
wrote:
>In article <01bca12e$a4748b00$492ccccf AT bubbas>, "Robert W. Largent"
><rlargent AT dimensional DOT com> writes
>>You have think about what you are trying to accomplish. Are
>>you trying to write the next best graphics lib, sound lib or
>>installation utility? Or, are you trying to write a kick ass game?
>>
>>I come from a business programming background, so maybe I
>>am a little biased on this topic, but, I love having specialized
>>libraries that I can rely on. Instead of spending all of my time
>>researching the nuances of different graphics cards and sound
>>cards, I can program what I want to be programming: the game.
>I dunno, can you get a job by using a library though? I'd have thought
>most companies wouldn't employ someone who could only use libraries and
>not able to program their games from scratch. Personally, I try to
>avoid libraries, because their too easy to get comfortable with.
Sure you can. If you get a job, you'll be using libraries there too.
The big difference, however, is that they usually have written this
library themselves as well. Generally, you'll have some people
working on the libraries, others working on the engine, and others
working on everything else. Here where I work, we have one guy who
works on the graphics library, and the rest of us just use it. That's
one programmer out of 7 that writes a library, and 6 out of 7 that
just use it instead. So it depends on if you want a job writting
libraries or not. If you do, then you shoud probably do your own
libraries. Otherwise, focus on what you want to become best at and
get a job doing. The better you are at that, the more likely you'll
get hired to do that.
-Jason
- Raw text -