[Bar_Code]

You're in tech, so an experience you have that is over 5 years is largely useless. What you need to leverage is your wisdom gained from the 15 years of experience. Wisdom is what separates you from someone with "only" 5 years of experience, but who can code almost as good as you and work for less. So no, there is no respect for experience beyond a number of years.

I've been in tech for over 25 years and I am more engaged than ever in what I am doing. I've been a programmer (front and back end), sysadmin, dba, network engineer, project manager, and product manager. Looking back, through all of that learning, I was becoming a better leader. About 3 years ago I stopped coding and became a full time leader in tech. I now optimize people and teams, not code and systems.

I'm still very much involved in architecting systems, which is where wisdom comes in. If I can't guide them in how to build something, chances are I can provide equal value in telling them how NOT to build something.

I would advise pursuing a role where you can impart your wisdom and leverage your many years of experience to help others and make an impact that way.

[kzisme]

Should there ever be a fear of being stuck with one technology, or language while at a job (or in a career?)

Currently I write .NET but I don't know if that would be the most interesting career to ~only~ write .NET (I'm a recent grad)

[Bar_Code]

I think you should be afraid of only knowing one technology/language. You should strive to at least play with one new technology/language per year. "language" can be flexible, like CSS, SQL, HTML. It doesn't have to be things like Go, Erlang, or Haskel. It would be nice to be at a company that encourages that. Even if you just know why people like certain languages, that would be helpful.