faq
code
awards
journals
subscribe
older stuff
rob's page
preferences
submit story
advertising
supporters
past polls
topics
about
bugs
hof
|
This discussion has been archived.
No new comments can be posted.
|
Feature: Why Being a Computer Game Developer Sucks
|
Login/Create an Account
| Top
| 238 comments
|
Search Discussion
|
|
The Fine Print:
The following comments are owned by whoever posted them.
We are not responsible for them in any way.
|
First post? Doubt it (Score:1)
by Anonymous Coward on Friday August 20, @04:24AM (#1735683)
|
Its axiomatic that most software projects fail, whether they be games or other more generic business ventures. I work for a company that repeatedly sets projection completion dates before 1) they have ironed out the requirements 2) they have investigated what that entails. So what happens is you get behind the proverbial 8-ball before the project even starts. I work in a group where the full time permament employees frequently work 80-100 hour weeks. Thankfully, I'm a contractor. Early on, I worked for a game company. In my (very limited) experience, game software projects fail for the same reason other software projects fail: poor management, poor handling of personalities involved. Game development is more sensitive, because you get more of the geek coder type where pride (as in "I'm right and you're not") comes before project. Its not the real world. But then, neither is business. Sometimes I wonder how software companies make money at all.
|
[ Parent
]
|
|
|
|
 |
|
|
Tcl tends to get ported to weird places like routers.
-- Larry Wall in <199710071721.KAA19014@wall.org>
|
All trademarks and copyrights on this
page are owned by their respective owners. Comments
are owned by the Poster.
The Rest © 1997-2002 OSDN.
|
[
home |
awards |
contribute story |
older articles |
OSDN |
advertise |
self serve ad system |
about |
terms of service |
privacy |
faq ]
|