I see your point but I don't think when John says "Write Code Every Day" he means writing without thinking. Of course any decent programmer knows thinking about the architecture, pattern, design, data structure and algorithm while writing code is paramount.
What I see him saying is that practice the art of coding every day but you can't write code without thinking so it's kind of implied to me.
For me the interpretation is to not just write code everyday, but write QUALITY code everyday. Quality code that improves what you're working on, challenges you to learn new things, and contributes to the development of this skill.
Otherwise I could write hello world for 30 minutes a day.
What I see him saying is that practice the art of coding every day but you can't write code without thinking so it's kind of implied to me.