The fun part of my job is showing off my age to make the point that they need to build new things in new technologies. Typical interaction goes something like this.

Person: When we started X project, we were using the state of the art technologies. We can just use that again.
Me: And when was that?
P: About 2012
Me: I was a freshman in high school.

Probably need more context

Typically this discussion comes up when they try to say we can use jQuery or ASP.NET web forms for new projects that I'm brought in for. When I'm trying to push angular or newer .Net stuff.

You reminded me this funny guy.

@Master167

Two Words: "New Coke"

New and fancy tech isn't always the answer.

If the dev team are comfortable with something else, assuming it isn't insecure, then learning new stuff, while fun, can delay the project and lead to amateur-hour code because nobody knows it yet.

Also, as a 40 year old dev.. young'un.. you don't have the experience to be so cocky yet. Comments like 'I was in high school' will just point out immaturity and lack of experience, and nobody likes that.

Old age and treachery will always beat youth and exuberance.

I'll take good and reliable over new any day.

Well I'm pretty young and never used my age to prove anything, bcs it doesn't makes sense at all, dude. Some old languages, frameworks and IDEs may be more useful sometimes, mainly when the team are more used and have more knowledge about them

When I started I knew about many technologies, I was scared to talk about them because I thought everyone already knew about them. I think finally hit the balance where I know enough about new things to understand it but also know enough to know if it will become useful in our general work flow.

@cmarshall10450 very different to person posting though who has 'its old haha lulz' as the best argument they can come up with