An anonymous reader writes: I am a programmer at a large software company who is approaching my 5-year anniversary at the company. One of the challenges I have during my day-to-day is convincing the "older generation" — those in their late 40s and early 50s — that my design decisions are correct. I don't pretend to be an expert at these decisions, but I can hold my own. On a new LOB project I recently was told to redo my design publicly in a review meeting by two "senior" programmers. Afterward when I spoke with them to learn how I could improve my design, I realized these programmers were not familiar with the popular framework or language used throughout our product. Their objections were based on decisions made by the framework and "that's not how I did it in assembly!"
It's clear to me these two individuals did not keep up with their skills to hone 30 years of wisdom. How do you handle working with the older generation? How do you communicate to your manager that a colleague no longer can pass an entry level job interview? What should I do to prevent from becoming like them?