The Angry Old Technologist (AOT) has been around forever. They built the system that you are trying to change. They’ve forgotten more than you’ll ever know about programming, hot shot. In short, you’re trying to change things, they’re yelling at you to get off their lawn.
Now, that’s not to say anyone with more then a few years of experience is a senior citizen. Nor that all criticism from people that share characteristics with this group.
Unlike last week’s character, the Angry Young Technologist (AYT), I don’t have experience being the AOT. At least I think I don’t. I’m fairly sure I’ve never been the one saying we absolutely shouldn’t change something. I may have argued against a particular change, or implementation, but not generalized change. Therefore, my thoughts here are more conjecture and inference than actual experience. Anyone who sees themselves in this description is welcome to set the record straight on anything I get wrong.
I was once at a conference where there was a Q&A with representatives from Microsoft, Yahoo, Google, and, of course Adobe. Someone got up and started talking about the current pace of change, and how every year all of us were coming out with more tools and technology. And he got angrier and angrier as he spoke, until he blurted out:
Why do you guys keep forcing me to learn new stuff?
And therein lies the key problem of the Angry Old Technologist: progress forces change; change forces them to learn; and they don’t want to.
Now, back when I was an AYT I never understood this. How can you hate to learn more things? As I get older, while I don’t resent learning new things, I can understand why you might.
I’m lucky, part of my job is to keep learning new things. Not all jobs build into them the need to learn new things. Most don’t. When you’re younger and have less responsibility, it’s not a huge deal, you can just spend your free time learning new things. As you get older, other concerns come in, like family, kids, housing, health care, retirement funds, school districts, PTAs ARRRRGGGGGGGHHHHHHHH.
All that stuff, some of which people refer to as your real life, destroys your free time. When you’re young, and passionate about technology, that free time is where you spend long hours focusing and mastering new things. When you get older and attached, you don’t have that time. Learning goes from something you love to do and you can easily do because you have copious free time, to something you have to make time to do.
And that’s if you’re passionate about what you do. If not, you start as a young person having to spend time to play catchup. By the time your free time is gone, the idea of learning new things terrifies you because you don’t know when you’re going to do it, and you never know the worth as all technology has an expiration date.
Where does the anger come from? What do you get when you combine no time, with years of responsibility, the pressure to constantly learn new things, some of which may be “dead” before you even implement them, and fear of what happens when you fail? You get rage, pure and simple.
There is bad news here for the guy from the conference, and for all of the other AOTs: There is no stopping the change. We technology companies might impact, alter, or nudge the waves of changes. But ultimately we don’t control them; they are caused by too many disparate sources to be controlled, even if we wanted to.
So what do you do when you’re face to face with an AOT?
- Well they’re irrational, so you should ignore them. Didn’t you read my book?
- Learn from their knowledge of the current environment.
- Engage them and try to bring them onboard without patronizing them.
So what do you do when you’re face to face with an AOT… in the mirror?
- Accept that the future cannot be stopped.
- Accept that it’s okay you can’t grasp every new piece of technology.
- Be part of the change, which will eventually replace what exists now, instead of opposing it.
- But mostly stop being so angry.
So what do you do when you’re face to face with an AOT and they’re your employee?
- Build-in continuing education and skunkworks into employee goals.
This is a tough group, and they are some of the most resistant to change. They’re also tough because a lot of them end up in management. So avoid, if you can, defer if you can’t, and give them opportunities to save face along the way.
4 thoughts on “Angry Old Technologist”
“And therein lies the key problem of the Angry Old Technologist: progress forces change; change forces them to learn, and they don’t want to.” – This is insulting at best.
I am an older tech, older than you. At times I’ve opposed “change” for many reasons. NEVER due to having to learn new tech. The biggest problem I have with some changes is that some AYT just jumped on the technology flavor of the month and keeps insisting we should rewrite everything to use that. Other reasons include may include the call to adopt something new that just isn’t enterprise proven. There are valid reasons to oppose a change. And as an Old Tech, I’ve also been the one pushing for new tech while younger techs that have no skills oppose it. I think this description of a AOT is a overly broad stroke designed to discredit people with valid reasons to oppose some “change”. Same went fot eh AYT description as well, but I held my tongue until you post the other held of the comparison.
Okay, my last sentence went all screwy.
It should read – Same went for the AYT description as well, but I held my tongue until you posted the other half of the comparison.
Will, these posts are intended to be additional info around my book, so they do lose some context.
I’m not saying when a older person angrily resists change, they are an AOT/AYT. I’m saying that when a person is identified by you as Irrational as per the definition in the book and they are angry and older or younger, these might be the people you are dealing with.
What makes them irrational?
In short they don’t have a rational objection to the change. “It’s wrong for this environment” might be a rational objection. It might not be. But if you look at the behavior and determine that they are blocking change for no good reason, then this is one of the possibilities of what’s going on.
I think I have not the power to be insulting as you have power to be insulted.
We have this problem at work, however the AOT is the manager. He is not a programmer as far as I have ever seen, but he has managed the project from the start…10-12 years. We are finally upgrading the site, and many of the underlying problems we are not allowed to fix…one reason given was because I said so, or because we have always done it this way. It is frustrating because many of not all of the team see many of the changes that need made, but since he is the only one allowed to make decisions, most of these changes will not be made. If we made those changes, then he would not know the system backwards and forwards…it would make the system better for the client,but not for him. This is a real hard situation to deal with since he is not a developer, he is a manager.
I do realize there are many old developers that like change, however, I seem to be matched up in jobs with many that don’t want to embrace change…it is a very touch situation to be in…