I'm confused why that troubles you. Does every article concerning Buddha have to mention his birthplace? Or to generalize, does every article about any significant historical figure have to mention their birthplace?
Well written articles will provide only relevant details. Exhaustive details can be found in encyclopaedias.
The team is mostly settled, we have database programmer who pretty much handles everything, programmers who work directly under business analysts taking tasks from them. I find myself not adding any value to the team. In other words, apart from day to day admin tasks and some occasional instances I am hardly needed. So I'm thinking what next?
Not looking to be a full time developer,my health condition doesn't allow for it anymore.
If the team is as optimized as it can be, then it may be time to move on from this team to another where you can add value. This sounds like an obvious statement, but without knowing much about your organization this may or may not be a viable option.
But again to my original, what do you want to do? How do you want to grow? What impact do you want to have? If you have the organization structure such that you can make a case to join a new team and help them grow and/or help with strategy for the organization as a whole (which will touch multiple teams), then there is that path as well.
If you want to transition organizations altogether then the above still holds.. in the sense that you need to define your own goals and then find an organization where you can develop them and have an impact.
I'm currently going through the transition. One I've learned one fact - People, People, People. It's all about people skills. People with emotions, people with attitude, people with ego and some great people as well. And you'd learn, you have to rely on things that aren't in your control. Age doesn't matter. What matters is how mature you are. Depends on whether you can smile and move ahead even when you know its not what you think is right.
Old age is not something to be managed. People are old, not by choice, but by natural processes that no one can control. You will be old one day and hopefully no one will see that as something that has to be managed, but if we feed into this negative trend then it is likely you will be seen in that same light. In the meantime, make a positive move away from ageism and remove that attribute from your mental profile of employees who requirement more management than others.
Your question implicitly suggests that you wouldn’t have problems managing young, unmotivated, change resisting programmers.
If so, do you think there is an innate difference between old unmotivated, change resisting programmers and young unmotivated, change resisting ones, or could your attitude towards the two groups be different?
Young people generally don't resist change because change benefits them. People who have invested 5 years into an obsolete skillset are most resistant to change.
SEEKING WORK -
I'm a melbourne based freelancer looking for work. Most of my experience is in .NET platform but can work on others as well.
Looking for either development or project management work.
Buddha was born in Nepal. Omission of these facts in mainstream articles like these has robbed Nepal of its history.