ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

Main Area and Open Discussion > Living Room

How Success Killed Duke Nukem - A heartbreaking story of developer failure

<< < (2/4) > >>

JavaJones:
Good article. I have to say, Wired has some real gems sometimes.

- Oshyan

40hz:
i think a harder and more subtle lesson for people to come to terms with is how many benefits there are to be gained from just getting something finished and working, even if it's flawed and not as good as you want it to be.  And how much focus and determination and it takes to do that while the siren song is calling out to you to extend the project longer and spend more time improving things.
-mouser (December 22, 2009, 02:35 PM)
--- End quote ---

I agree.

But isn't that exactly what FOSS developers get so harshly criticized for doing?  :)

sajman99:
Wow, this is a truly sad tale--Duke Nukem Fornever. ;)

lanux128:
a good insight on the whole operations. blowing $20million on the project and still without an end, that is telling something. i wonder what happened to ken silverman who wrote the original Build engine?

Lashiec:
a good insight on the whole operations. blowing $20million on the project and still without an end, that is telling something. i wonder what happened to ken silverman who wrote the original Build engine?
-lanux128 (December 22, 2009, 08:38 PM)
--- End quote ---

He wrote PNGOUT, and still maintains it :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version