This is great when you're re-implementing Wolfenstein.
Not so much when you're doing exploratory computer science, or blue-sky prototyping. To build upon his analogy, scaffolding is most helpful when you have a reasonable knowledge of the shape of the building.
"It depends on the context" isn't exactly a shocking discovery however.
I love Carmack, love his presentation style, and when he talks from experience, I listen.
> Not so much when you're doing exploratory computer science
I'm not sure. The following experiment is outdated (I'd love to see it redone more rigorously and with modern languages) and has several methodology flaws, but "An Experiment In Software Prototyping Productivity" (1994, Paul Hudak et al) shows that Haskell and static types are actually great for rapid prototyping and exploratory programming, even in the face of vague or incomplete requirements. This runs contrary to common sense, which is why the experiment was fascinating.
Not so much when you're doing exploratory computer science, or blue-sky prototyping. To build upon his analogy, scaffolding is most helpful when you have a reasonable knowledge of the shape of the building.
"It depends on the context" isn't exactly a shocking discovery however.
I love Carmack, love his presentation style, and when he talks from experience, I listen.