Well, okay, but rote memorization is neither necessary nor sufficient to internalize concepts.
One of the reasons people make fun of the author's approach to creativity is that systematic memorization fundamentally can't teach taste—so the systematic approach reeks of awkward, try-hard, low-brow, tasteless art.
More broadly, memorization doesn't help much with any sort of tacit knowledge, not just taste. I just figure taste is especially important in creative endeavors. That's definitely the case for programming! Memorization in programming gives us architecture astronauts and design-pattern soup rather than elegant code.
For what it's worth, I do think that it is useful and important to have a good mental model of what expertise is and how you can develop it. Memorization might be a component of this, but it's going to be a small component at most. I expect that realistic practice with fast feedback and expert mentorship matters far more. (If you're curious, I found the book Sources of Power by Gary Klein gave me a good way to think about how expertise works.)
At the same time, memorization has a real cost: it takes time and it's frightfully dull. For me, at least, trying to memorize something without context is not just ineffective but also totally kills any intrinsic motivation I have for whatever I'm learning. Sometimes a bit of memorization is unavoidable, but I've found that to be relatively rare. Otherwise, my time is generally better spent on some sort of practice in context.