It's really interesting to see the perspective of an older peer when it comes to development. I've been writing code since I was 10 (19 years ago) and have bee

It's really interesting to see the perspective of an older peer when it comes to development. I've been writing code since I was 10 (19 years ago) and have been doing it professionally for about eight years. To look back sometimes and see the differences in myself as a coder and wonder about what it will look like going forward is a favorite wandering for my brain. I think the one thing that I find most common in my career has been coworkers, within 10 years of retirement, that have just given up and no longer put in what's needed to be a coder. I enjoy the company of someone who has had more experience (it's part of how you learn) and love to hear about the battles that the people before me had to fight. I start my day by asking myself some questions. Where is the technology at right now? Where is it going? How does it relate to my job? How does it relate to my interests? How does it relate to what I've done in the past? Where am I at as a developer? The problem is that people stop asking themselves all of these questions and start weighting towards a few in particular.