I’ve been doing kernel code in C for nearly 30 years. Same tech stack.. emacs, c compiler, kgdb. Lots of things have come along to make things better (dtrace, eBPF). The kernels have changed (out with Solaris, DEC OSF/1, AIX, etc, in with FreeBSD and Linux), but it’s all pretty similar in the end. And experience REALLY helps and is rewarded. Especially when you were there 25 years ago and you remember why something is the way it is
It has gotten harder to remember what I've worked on lately. For the past 15 years, I've been keeping notes in text files to remind me of what I work on each day. It's far easier to do a recursive grep on my top level notes directory than it is to find something in Outlook. I also make heavy use of Confluence to document everything I work on. I think I've created more Confluence pages than the rest of my group combined.
I've kept in touch with a number of people I've enjoyed working over the years with which has made it much easier to find jobs when I need to make a change. For the past 20 years, I've maintained a mailing list to organize weekly happy hours with some of them. I got hit by a RIF 5 years ago (first time in 47 years, believe it or not) and managed to line up a new job in 2 months thanks to a hardware engineer I had enjoyed working with 32 years ago. I also had a few whiteboard interviews during that time which helped remind me why I hate the traditional way of finding jobs.
I certainly didn't write it 20 years ago, but I was there and around and can understand the motivations which is helpful.
Right around then, most open source kernels started doing a lot of performance work on sockets. Some of which has stood up until recently, but some things look silly with today's eyes. You could set the port number hash length to more than 16-bits, which doesn't make sense... But they added it to get 2 or 4 bits of hashing in 2000, and it worked enough that nobody changed it. Things like that.
Extensive experience (beyond say 5-10 years) isn't valued for ICs. There's so much churn in tech stacks, frameworks, etc that anything anyone was doing 15 or 20 years ago is now totally irrelevant.
This leads to burnout from lack of progression, and either people go into management or they drop out into something else.