> This is like telling programmers they don't need to know data structures before writing a program.
Serious question: What did you refer to with "This"? You might argue against something I didn't say here.
I did not say people should not read these books — I actually said the opposite: read as many books as you can find, even the formulaic ones. What I did say however is that writing entails more than is said in these books.
To go with your analogy: Yes, beginner programmers should be aware that just understanding the data structures alone doesn't make you a master programmer and that there is more to the craft.
And taking your analogy to the next step, what does that make that blog article? That would be like an article on data structures pretending you can do everything with Arrays and not mentioning anything else exist.
Don't get me wrong, story structure is crucial, but doing as if there is only one doesn't help beginners and communicating why this one is common and what advantages it has over other choices would be much better.
Serious question: What did you refer to with "This"? You might argue against something I didn't say here.
I did not say people should not read these books — I actually said the opposite: read as many books as you can find, even the formulaic ones. What I did say however is that writing entails more than is said in these books.
To go with your analogy: Yes, beginner programmers should be aware that just understanding the data structures alone doesn't make you a master programmer and that there is more to the craft.
And taking your analogy to the next step, what does that make that blog article? That would be like an article on data structures pretending you can do everything with Arrays and not mentioning anything else exist.
Don't get me wrong, story structure is crucial, but doing as if there is only one doesn't help beginners and communicating why this one is common and what advantages it has over other choices would be much better.