Devs Can't Optimize: Specs for a LEGO GAME
(media.kotakuinaction2.win)
You're viewing a single comment thread. View all comments, or full comment thread.
Comments (37)
sorted by:
Yeah. "Premature optimization is the root of all evil" is the root of all computing evil.
Meh, there's some truth to the sentiment, but it's more at the level of "not all projects need to be optimized", but when you're building something like this you go in knowing from the word "go" that you're going to need to optimize for performance. It should be getting baked into the preliminary design choices that "whatever we build, it needs to be extremely performant, so structure everything accordingly." Building and designing for that though? That requires genuine skill and intelligence, something which you're not allowed to select for anymore because you'd just get a room full of John Carmacks and that's simply too White and too male.
Yeah, look at anything Carmack talks about and the entire mindset starts with optimized code. His natural output is optimized.
It's white guys and old guys that can even do it anymore. The rest are Indians who don't know anything, and young ones who have never dealt with resources being the limiting factor. Not even as a coder, I remember having to optimize stupid ass drivers in DOS and pick through what I really needed so I could have enough RAM free to run Doom on a PC it totally shouldn't have run on. Adding more wasn't an option and getting a new PC was cost-prohibitive for a kid.
If I was going to design a learning-track for a good programmer, one of the things I'd make them do is a functional Gameboy game with a list of things they have to make it do. In assembly. Give them an understanding of how everything moves around in a rather easy to build and debug system. Learn to make things work in 8K of RAM.