[yebyen]

This exactly. Pay grade and composite sets of professional skills acquired are not protected classes. You can't prove it was age discrimination if you are paid higher and don't have skills that newer employees have (because both of those things also made you a target.)

That being said, I am probably younger than all y'all and I've been trained to remain in constant motion on the skills treadmill. I don't know if that's a good thing for either employers or employees. (I certainly feel under-utilized.)

[scarface74]

Whether it is “good” or not isn’t relevant. It’s necessary.

[yebyen]

With respect, this has to be demonstrated. Are the new skills better than the old skills?

(I am on the treadmill, so clearly I believe they are.)

[scarface74]

It doesn’t matter if they are better. It just matters if they are more marketable.

[yebyen]

More marketable to who, employers? Are they more marketable because people with those skills are younger and earlier in their careers, so can be paid less? That sounds potentially circular and I would need to hear more to come to agreement.

You're also not giving me much to go on here. I've had to infer 90% of what I think you meant. I think there's a solid argument that older skills are battle-hardened and therefore better for productivity and maintainability. I'm not going to try to make it though, because I'm on the treadmill focused on acquiring newer skills, and therefore would be arguing against my own self-interest. (Eg. why do we need to know capistrano if we have kubernetes?)

But maybe those older skills are not so much maintainable, if all the newer employees on the block are discouraged from acquiring those skills based on the treadmill. You see why I'm not so sure about this treadmill business? I already learned a bunch of skills that I'm afraid we won't use, because they are already asking for newer ones (serverless!) Maybe my employer would be better served by asking me to spend some time to learn Capistrano, if they're not going to let me use Kubernetes skills I went off and acquired on my own. (Let's make this real, I'm using a real example from my own life. I don't have to be convinced that Kubernetes is more valuable, but I do have yet to prove it in the context of my real job, where our deployments all still run on Capistrano not K8s.)

My situation is likely a bit unique and I don't think my employer engages in age discrimination in any way but we have to capitalize on these newer skills to give them value. An abstract sense of "having skills with high marketability" does not deliver any value to the employer (or employee) unless they are capitalized somehow.

In any case, we're arguing about nothing, because

> get a $35/month PluralSight subscription and watch the job boards to see what you need to be studying?

we don't have any numbers on how many of these canned IBM employees actually did this and got canned anyway. Its relevance as a factor is questionable, if the employees with advanced age are simply more well compensated like you said that has also made them a bigger target. They may have kept their skills current and been terminated anyway. This is a 100% speculative argument.

[scarface74]

Two parts. I guess as a mid 40s developer I could share what you shouldn’t do and should do based on my experience. I’m also nowhere near Silicon Valley startup or FAANG culture. I have lived in a major metropolitan area for 20 years where there has always been a vibrant job market for developers.

I spent 9 years at a company in the 200x’s that stayed stuck in 2002 - C++, VB6, Perl hosted on IIS, classic ASP, etc. I didn’t know anything about modern development practices. Can you imagine what would have happened if I stayed another 10 years like another developer did? Last I heard they were transitioning to VB.Net and were still using Perl. So yeah, I know first hand what it looks like to let your skills stagnate and find yourself barely marketable.

When I finally left, I took a job as what for all intents and purposes was a junior .Net developer instead of a higher paying position as a C++ developer because I knew the market was moving away from C++ (at least the local market).

I spent the next decade watching the job boards, talking to recruiters and making sure my resume was matching the skills in demands and changing jobs about every two years as I learned all I could from one company and always for nice bump in salary.

I didn’t mean to jump on the “newest” technology just to keep up with industry trends. As much as I love Hashicorp’s Nomad and so used it since it worked with more than just Docker, I would never suggest anyone learn it if they already know kubernetes. That’s where the market is.

So yeah, it is about being able to find a job quickly and being more marketable to employers.

My own m.o. is to be a true “full stack developer/architect”. By full stack knowing a marketable technology on each layer -

- web

- server

- database (RDMS/NoSQL)

- cloud hosting and knowing netops/devops/ and development using their cloud native features.

- continuous integration/deployment best practices.

- and just general best practices.

You don’t have to jump on the new and shiny, the further you go down the stack, the more stable it. Sure things are always being added at each level but you don’t see the rapid changes like you do in JS land.

As far as learning things that pay less, I’m not a strong front end developer. Companies pay me because I can go very deep in the stack and can guide development and architecture from the back end. Web developers are a dime a dozen and pay seems to be stagnating for them. But I still want to learn the latest web frameworks to be more marketable in a pinch even though they are getting paid less than what I make now.

we don't have any numbers on how many of these canned IBM employees actually did this and got canned anyway. Its relevance as a factor is questionable

I wasn’t thinking about keeping thier skills up so they could keep their job at IBM, jobs are disposable and interchangeable if you stay marketable. Someone in technology with marketable skills can have a job before thier next mortgage payment is due if they are either in the right part of the country or are willing to move.