Use whatever labels you want, apply charitable reading and I'm sure even you could understand what I mean here. Clearly there are at least two sorts of tasks (or used to anyways) in "software engineering" as a whole, one more mechanical and one more about thinking.
What exactly shows that? That I think thinking about code/design and typing code are two different activities? Maybe you disagree, around myself and my peers that'd be a minority perspective, but it's not speculative, based on real experience.
Coding is literally writing code, instructions in plain text that control the behavior of computer. That implies knowing which instructions to write.
But creating software is much more than that. Just like writing an essay involves more than just typing words. Other activities include: Architecture, Requirements analysis, Debugging, Testing, Integration,…