What shape a experienced developer

You are just experienced, not superman Hi everyone. I am an experienced developer. A normal person that can tackle development problem in my experienced area just like you...

Hi everyone.

I am an 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 misunderstood 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 no need feel bad, here's some fact to cheer you up. (Let's skip about some meaningless complain such 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 an experienced people usually do better than the others. You know how to estimate the effort to do a thing right, how does it cost, and what's the bad side if the plan changed. Those are from your experience (the knowledge growth time by time through your career). You are not smarter, neither know the most, you are just know a better 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 stuff to you, are just some decoration of some simple fact.

You won't chase for anymore unique, fancy solution. It doesn't mean you won't appreciate them anymore. But when you look at the bright side, you also look into the dark side.

Nor the bad is bad, sometime good can also be bad. And sometime those bad from other people, maybe is they were doing it wrongly. To you, the fact is more important than what people said.

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, and scope it

A microscope awesome can'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 important, you realise that even those ideal solutions can and will definitely be broken when the time pass and scope 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 an easier 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 waiting for you. You need to continue your success through one to one point four point twenty.

You are not going to allow breaking a building by just a peronal prefrence of windows, though you still agree some beautiful wall painting that will delight the world.

You know what it will be built and will end-up with ten of the others. And what was there affact what will/can be there.

You also know a right tool is the key to bring success to the 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

It sounds like a HR, but in fact, an experience person in a team, somehow act really like an HR. You should but don't just 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 your life, your career and your company(or project maybe)

Those experience all together make you a unique, un replacable force in a company. Smart young people are good, but what you have, can always help them beeing much better.

The end

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.

BTW ping me, I always enjoy working with a peraon like you.