Joe Rogan Experience #1342 - John Carmack

I'm an idiot. I wrote John Cusack when I wanted to write John Carmack. I don't know how I could even confuse the two names. Here's the Carmack podcast where he talks about it. Fantastic listen for anyone honestly. Carmack is a fascinating guy. [VIDEO]

Interesting perspective on work-life balance, certainly contrary to the usual discussion online on these issues [VIDEO]

On open sourcing Wolfenstein, Doom, Quake: [VIDEO] Neuralink: [VIDEO] Artificial General Intelligence: [VIDEO] Quantum Computing: [VIDEO] “Engineering is figuring out how to do what you want with what you’ve actually got”: [VIDEO] End of Moore’s Law / On CPU architecture: [VIDEO] 5G and streaming (games & video): [VIDEO] edit: like already mentioned there are a lot of topics covered, some even for just a few sentences, the conversation flows, worth watching the whole thing

He talks about AGI at [VIDEO] I wonder if all the really smart people who think AGI is around the corner know something I don't. Well, clearly they know a lot of things that I don't, but I wonder if there's some decisive piece of information I'm missing. I'm a "strict materialist" too, but that doesn't mean I think we can build a brain or a sun or a planet or etc within X years, it just means that I think it's technically possible to build those things. I don't see how we get from "neural net that's really good at identifying objects" to "general intelligence". The emphasis on computational power also makes no sense to me. If we had infinite compute today , what steps would you take to build AGI? Does anyone have any good ideas about that? Sometimes I wonder if AGI (and the concept of a "technological singularity") isn't just "intelligent design for people with north of 140 IQ". Maybe really smart people tend to develop a blindspot for really hard problems (because they've solved so many of them so effectively).

John Carmack is practically a machine. He's openly talked about his work ethic in a bunch of places. He's the type of guy who after a life time of coding calculated he's 100% efficient up until 13 hour work days and then he drops off[0]. Although he did mention working those long hours is often best working on multiple things instead of 1 topic but maybe with AGI there's a bunch of different avenues to explore. [0]: [VIDEO]

They have a very good thing going. Perhaps there is no great reason to bite off so much at one time. They can take their time and do that later if it makes enough sense. I would expect it would require a very substantial effort to rebuild their platform in a different language. If you're 75/100 of where you want to be on performance, it can be easy to lose immense amounts of time chasing a 95/100 type ideal performance outcome when you can maybe far more easily get to 90/100 by making eg straight-forward caching improvements to what you already have and not have to rewrite all of your code. Good enough is almost always underrated in tech. People destroy opportunity, time, money, and entire businesses chasing what supposedly lies beyond good enough. John Carmack has a good example of this in his Joe Rogan interview [1], in how id Software burned six years on Rage, making incorrect (in hindsight) choices that involved trying to do too much. He regrets his old standard line and approach that it'll be done when it's done. He wishes they had made compromises instead and shipped Rage several years earlier. That's a pretty classic storyline in all of tech, taking on far too much when 85% good enough would have worked just as well most likely. [1] [VIDEO]