6 ms·

I'm not sure if it would've been John Carmack in this particular case. He was more concerned with the engine and rendering side of things, less with the gamepla

I'm not sure if it would've been John Carmack in this particular case. He was more concerned with the engine and rendering side of things, less with the gameplay logic stuff. More likely it would've been either John Romero or John Cash who wrote this code, but it's hard to say for sure. Best thing we can hope for is that John Romero pitches in with his impeccable memory :D

midasuni 3y ago
So the only requirement to work at iD back in the day was to be called John?
- brookst 3y ago
  That’s what my buddy said, yeah. Good old John Manyjohns.
  - klodolph 3y ago
    For those who haven’t seen Buckaroo Banzai—all the people working at Yoyodyne Propulsion are named John. It’s a plot point.
- cfj 3y ago
  Or Carmack.
- TechBro8615 3y ago
  It seems like Amazon has the same idea when promoting people named Andy or Jeff to executive roles.
mysterydip 3y ago
"Hi Sandy, hope you're doing well."
i_c_b 3y ago
You can read Carmack's .plan archive from 1996 here, if you're so inclined: https://github.com/ESWAT/john-carmack-plan-archive/blob/master/by_year/johnc_plan_1996.txt https://github.com/ESWAT/john-carmack-plan-archive/blob/mast... It's a _fascinating_ snapshot into Quake's development. I have no idea if his .plan is a record of what he, specifically, was doing, or if he was just capturing what the programming team was doing, but at the very least, it makes clear that he was aware of huge amounts of very highly specific game code issues as they were being worked on and was almost certainly deeply involved.
- baal80spam 3y ago
  Wow, this link is something else - you can track what problems he tackled and what he worked on DAILY.
  - Solvency 3y ago
    Guessing you're on the younger side? I used to read these voraciously as a 11 year old. Felt like a magic window into the game industry.
    - sillysaurusx 3y ago
      Hello fellow I-was-once-11-and-fascinated-by-.plan! I wasn't sure if I was the only one. St Louis in 2000 made it seem like there were only a handful of people interested in programming at all. Hmm... 11 would put me at 19999, so I must've been more like 12 or 13. I remember that's when I started taking gamedev seriously.

midasuni 3y ago

So the only requirement to work at iD back in the day was to be called John?

brookst 3y ago
That’s what my buddy said, yeah. Good old John Manyjohns.
- klodolph 3y ago
  For those who haven’t seen Buckaroo Banzai—all the people working at Yoyodyne Propulsion are named John. It’s a plot point.
cfj 3y ago
Or Carmack.
TechBro8615 3y ago
It seems like Amazon has the same idea when promoting people named Andy or Jeff to executive roles.

mysterydip 3y ago

"Hi Sandy, hope you're doing well."

i_c_b 3y ago

You can read Carmack's .plan archive from 1996 here, if you're so inclined: https://github.com/ESWAT/john-carmack-plan-archive/blob/master/by_year/johnc_plan_1996.txt https://github.com/ESWAT/john-carmack-plan-archive/blob/mast... It's a _fascinating_ snapshot into Quake's development. I have no idea if his .plan is a record of what he, specifically, was doing, or if he was just capturing what the programming team was doing, but at the very least, it makes clear that he was aware of huge amounts of very highly specific game code issues as they were being worked on and was almost certainly deeply involved.

baal80spam 3y ago
Wow, this link is something else - you can track what problems he tackled and what he worked on DAILY.
- Solvency 3y ago
  Guessing you're on the younger side? I used to read these voraciously as a 11 year old. Felt like a magic window into the game industry.
  - sillysaurusx 3y ago
    Hello fellow I-was-once-11-and-fascinated-by-.plan! I wasn't sure if I was the only one. St Louis in 2000 made it seem like there were only a handful of people interested in programming at all. Hmm... 11 would put me at 19999, so I must've been more like 12 or 13. I remember that's when I started taking gamedev seriously.