Pretty much covers it. If all you do is 'write code' then you have to be prepared to start 'write the same code in a new "paradigm" several times.' Once that starts you'll do one of two things, either get bitter and grouchy and become unemployable as a coder (trust me when I say that nobody likes working with someone constantly whining about how they already wrote this code 5, 10, 15 years ago), or you will change the areas you work in.
Some folks will try to be "architects" (used in quotes because there are lots of definitions about what that means), and some will go into management.
As a coder, your pay will definitely plateau. One of the interesting things about the current situation for 'rock star' coders is that their pay will plateau faster, this will be a problem for them later. If you can get a number of people on the same page to build something bigger than what a single person can build (not so much management as technical leadership) then you plateau will be a bit higher (roughly 20% if you believe salary surveys).
Some folks will try to be "architects" (used in quotes because there are lots of definitions about what that means), and some will go into management.
As a coder, your pay will definitely plateau. One of the interesting things about the current situation for 'rock star' coders is that their pay will plateau faster, this will be a problem for them later. If you can get a number of people on the same page to build something bigger than what a single person can build (not so much management as technical leadership) then you plateau will be a bit higher (roughly 20% if you believe salary surveys).
Keeping it fun is key though.