3 ms·
> Write your code for this game only, not for a future game. You’re going to be writing new code later because you’ll be smarter. This alone is worth the read
by headShrinker 10y ago
> Write your code for this game only, not for a future game. You’re going to be writing new code later because you’ll be smarter.
This alone is worth the read for me. I wish I could shadow this team.
- favorited 10y agoI'd recommend checking out this post[1] by Wil Shipley (a longtime Cocoa dev), which includes a story about how Carmack doesn't re-use code. The whole blog post is a fun read. [1] http://blog.wilshipley.com/2013/12/my-doom-20th-anniversary-stories.html http://blog.wilshipley.com/2013/12/my-doom-20th-anniversary-...
- asimuvPR 10y agoGreat link. Thanks for sharing.
- adrianratnapala 10y agoBear in mind the next thing the article says is >(And of course there was no Unity or Unreal Engine to license.) But advice like "don't reuse" and "use an external framework", actually have a common root because the difficult thing in programming is not banging out code, not even when you have your QA in place. The really hard thing is getting knowledge: figuring out the right thing to do and how to do it. Once you have figured it out in one app, you can do it again only better in the next app you write. You are re-using knowledge that is stored in your head. But when someone writes an engine, they are also storing knowledge, but now inside code. Again, knowledge is being re-used.