Sometimes, The Elegant Implementation Is Just A

It's Nice To Have A Game That Sells A Million Copies.

The Important Point Is That The Cost Of Adding A Feature Isn't Just The Time It Takes To Code It. The Cost Also Includes The Addition Of An Obstacle To Future Expansion. Sure, Any Given Feature List Can Be Implemented, Given Enough Coding Time. But In Addition To Coming Out Late, You Will Usually Wind Up With A Codebase That Is So Fragile That New Ideas That Should Be Dead-simple Wind Up Taking Longer And Longer To Work Into The Tangled Existing Web. The Trick Is To Pick The Features That Don't Fight Each Other.

One Of The Big Lessons Of A Big Project Is You Don't Want People That Aren't Really Programmers Programming, You'll Suffer For It!

I Wanted To Remain A Technical Adviser For Id, But It Just Didn't Work Out. Probably For The Best, As The Divided Focus Was Challenging.

If You're Willing To Restrict The Flexibility Of Your Approach, You Can Almost Always Do Something Better