The core of what I do is solve problems, whether that's in graphic engine flow or rockets. I like working on things that are going to have an impact one way or the other.
John CarmackRead
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. ... The trick is to pick the features that don't fight each other.
Interpretation
Adding new features has hidden costs that can hinder future development.
In software development, each new feature taken on can complicate code structure and vision, affecting future enhancements. John Carmack emphasizes the importance of selecting features that will harmonize with one another, rather than create barriers, ensuring a robust and flexible software architecture.
In practice
In a team meeting discussing the new software project, one might say, 'As John Carmack pointed out, we need to consider the cost of adding features carefully.'
The core of what I do is solve problems, whether that's in graphic engine flow or rockets. I like working on things that are going to have an impact one way or the other.
Sharing the code just seems like The Right Thing to Do. It costs us rather little, but it benefits a lot of people in sometimes very significant ways. There are many university research projects, proof of concept publisher demos, and new platform test beds that have leveraged the code. Free software that people value adds wealth to the world.
Low-level programming is good for the programmer's soul.
Because of the nature of Moore's law, anything that an extremely clever graphics programmer can do at one point can be replicated by a merely competent programmer some number of years later.
Programming is not a zero-sum game. Teaching something to a fellow programmer doesn't take it away from you. I'm happy to share what I can, because I'm in it for the love of programming.
In California, we have some of the strongest consumer protection laws in the country. While it is easy to conceive of innovation and regulation as mutually exclusive, California is proof that we can do both. We can innovate responsibly.
I think a lot of the time there isn't such a black-and-white difference between what's a platform and what's an app. It's really just like the most important apps become platforms.
The future is green energy, sustainability, renewable energy.
The fundamental truth for developers is they will build if there are users.
We want to build systems that can generalize to a new task. Being able to do things with much less data and with much less computation is going to be interesting and important.
If you go back back a few hundred years, what we take for granted today would seem like magic - being able to talk to people over long distances, to transmit images, flying, accessing vast amounts of data like an oracle. These are all things that would have been considered magic a few hundred years ago.
Subscribe for the occasional hand-picked quote. No noise.