First, you're two paragraphs are completely contradictory.
If you do manage to get hired by a game company out of college (or high school), you probably already have a pretty solid understanding of the basics, or at least show a sign of hope. Unfortunately, 9 times out of 10, you'll end up a script monkey--with a miracle--tools programmer of some sort.
Furthermore, companies are now only hiring those who have at least released 1 title.
But, if you do get in and are innovative (what I consider a pro), you can make some bucks...
This is pretty meaningless for airline since they're talking to ATC almost 100% of the time and may get warnings/updates via many other channels. Whereas a GA pilot flying a little 152--or more to the point--a Lancair PropJet (350+ kt cruise), may be happily flying VFR and suddenly find two F-16's on his wing because he busted a "pop-up" TFR...
We need a system of communication and coordnation among ALL aircraft.
Another sad addition to this statement is the fact that when the states start passing these little ditties in retaliation for getting "pissed on", many other ligitimate companies will get mangled in the process...
To step on a huge company like Microsoft it's going to take a big mofo boot, and in the act of stepping, your bound to take out many helpless ants...
For example changing headers that two developers need... The only headers that two groups need should be interface headers, these should be set early and not need a lot of change, with any change taking both developers changing the code internally...
I work on a core technology team whom are all very experienced programmers originating from many different software universes (embedded, games, DB, etc). Based on the evil of past experiences, we set out to develop the interface system before starting *any* actual project (or projects). This took a little over a year of design and development evolution with no actual product releases (some protos). In spite of such a long "generation" process it took us only 3 months to release (spit out) one particular product...
I truely believe in taking time to dream and design--construction is the easy part.
Slashdot Mirror
If you do not know assembly, you might produce simply beautiful code, but then have no clue why it runs like a three-legged dog.
My three-legged dog runs faster then most with four...
First, you're two paragraphs are completely contradictory. If you do manage to get hired by a game company out of college (or high school), you probably already have a pretty solid understanding of the basics, or at least show a sign of hope. Unfortunately, 9 times out of 10, you'll end up a script monkey--with a miracle--tools programmer of some sort. Furthermore, companies are now only hiring those who have at least released 1 title. But, if you do get in and are innovative (what I consider a pro), you can make some bucks...
This is pretty meaningless for airline since they're talking to ATC almost 100% of the time and may get warnings/updates via many other channels. Whereas a GA pilot flying a little 152--or more to the point--a Lancair PropJet (350+ kt cruise), may be happily flying VFR and suddenly find two F-16's on his wing because he busted a "pop-up" TFR... We need a system of communication and coordnation among ALL aircraft.
The landing gear system on both aircraft are actually different. One uses pneumatics and the other is simply spring loaded.
Well, artists (those who have troubles computing powers of 2) are not the only ones learning Maya. Why not include the SDK for us programmers? :|
Another sad addition to this statement is the fact that when the states start passing these little ditties in retaliation for getting "pissed on", many other ligitimate companies will get mangled in the process...
To step on a huge company like Microsoft it's going to take a big mofo boot, and in the act of stepping, your bound to take out many helpless ants...
For example changing headers that two developers need... The only headers that two groups need should be interface headers, these should be set early and not need a lot of change, with any change taking both developers changing the code internally... I work on a core technology team whom are all very experienced programmers originating from many different software universes (embedded, games, DB, etc). Based on the evil of past experiences, we set out to develop the interface system before starting *any* actual project (or projects). This took a little over a year of design and development evolution with no actual product releases (some protos). In spite of such a long "generation" process it took us only 3 months to release (spit out) one particular product... I truely believe in taking time to dream and design--construction is the easy part.