I am a experienced developer. A normal person that can tackle development problem in my experienced area just like you.
And just like you, a lot of people misunderstand our experienced in a very common way, they just think we can do all the thing those junior people (maybe) cannot.
But the truth is, we are not like that. You should admit, pretty much what you can do, is not from your 'experience', which also means, a junior may just be better than you. But don't feel regret, here's some fact to cheer you up. (Let's skip about some meaningless complain such as we still need to eat and sleep)
You plan solution along with time and resources
Experienced people, you give them time and resources, they come up with solution.
Superman, they just did it no matter what.
Right? I think this is a experienced people usaully better than the others. You know how to estimate the effort to do a thing right, what does it cost, and what's the bad side if the plan changed. Those are from you experienced (also the knowledge growth time by time). You are not smarter, neither know the most, you are just know the right way to break down a problem, and sort those thing out. All those pyshical fact are still there, you just know the most efficience way to deal with them.
You know what is good and what is bad
You are not tech hippies anymore, all those trendy fancy thing to you, are just some decoration of some simple fact.
You won't chase for some unique, fancy solution anymore. I don't mean you won't appreciate them anymore. But when you looking at the bright side, you also look into the bad side.
Nor the bad is bad, some time the good can also be bad. And sometime those bad from other people, maybe is they are doing bad with it. The fact is more important than what people say.
And that's what make you so different. You ask
why more than
how, you learn more about the
reason than a
solution. And belive me or not, it's easier to think than you actually are. You can only learn it when you facing just enough
awesomeness and just way too much of them. This process take time, and those time, luckily you've already been through.
You think problem with scoping
awesomecan't help you to ensure a macro scope success (vise versa).
You understand all thing has it's scope, and that scope is usually changing time by time. You know how to think the most ideal way just within that scope, more importantly, you realise that, even those ideal solutions can and will be broken when the scope is changed.
You understand changing is always necessary, and by this scope, this is the best you can do. But you also consider when scope is changed, how you can adopt that changes in a more easy way.
You realise Software Engineering is an Engineering problem
Although you still think building a software is somewhat like painting on a wall, you admire it, the wildness and art sense really help you to build a zero to one thing. But if you are not doing zero to one, there are a lot of daily routine to be done from one to one point four point twenty.
You are not going to allow breaking a building by just a peronal prefrence of windows, and you will agree on some beautiful wall painting that will delight the world.
You know what it will be built will end up with ten of the others. And what is there affact what will be there.
You also know a right tool is the key to bring success development team. You value right tools as well as right person. There is nothing called personal preference, personal preference only resisted in personal preference setting page. You don't want the overall failure come from a single im-professional tool choice.
You care about people
This one sounds like a HR, but in fact, a experience person in a team, something really act like a HR. But you only share the frustration with your teamate, find a better way to work together. Motivate the team. Because your experience is not only about programming, it also about life, career and company(or project maybe)
Those experience together make you a unique, un replacable force in a company. Smart young people are good, but what you have, is always help them beeing better.
Don't be afraid when you grow old, don't be afraid of being a developer with ages and experience. If some company doesn't value your experience, or they do but in a wrong way, don't feel bad. You should still revaluete yourself, but if you are really that experience, it only prove that those company are not valuable for you to stay.