3 ms·
Wolfenstein 3D played a large part of driving my interest in computers and learning how they really work under the hood when I was young. Plus the release of Ma
by jimwalsh 13y ago
Wolfenstein 3D played a large part of driving my interest in computers and learning how they really work under the hood when I was young. Plus the release of MapEdit really made you feel powerful and a young kid getting involved in computers.
Doom is the point where I became interested in programming and it got me looking to how you actually made these games. id Software eventually open sourcing Wolf3D really helped spur that on. On top of that, Carmacks talk and his always interesting .plan file (a blog before blogs) made him seem very accessible and really opened up the world of game programming. I still enjoy going back and reading parts of the Wolf 3D or Doom code to see how they handled certain problems/limitations.
I'd agree with the other poster that 'Masters of Doom' is a great read and worth it to grab if you haven't read it already.
- fdej 13y agoDitto! Making Doom mods was the main reason that I taught myself programming. And I probably learned more about development (in a general sense) from making Doom maps, than I ever did in school...
- azmenthe 13y agoAlmost same exact story although I never got into Doom modding but did make my own games in high school because of doom. Actually reading "Masters of Doom" truly planted the seed for my entrepreneurial spirit, the first time I realized "I can get good at something and create something just for me. I can value just from sheer will"
- petercooper 13y agoIt's also worth reading his some of his .plan archives as well which have been stored in various places. Lots of interesting bits of wisdom, insight into his thought processes, and even odd practices like going away to a hotel for a week to just spend time alone to learn new tech or code :-) (something I'd love to try someday..)