For the vast majority of engineers, even writing high impact code means repeating the same request/db query/response dance, code pasting or ebuggin activity, and to be actually good and efficient at any of these means having done them plenty of times.

Even understanding novel problem domains requires a certain structured approach to research, talking with users, writing out thoughts, etc. All this certainly matches the analogy laid forward.