[zdragnar]

From the perspective of someone who has been on the hiring side, I see this a bit differently.

Senior developer positions are more common now, in part from title inflation but also the rise of more complex online interactions and businesses. By cutting the senior bit out of your resume, you no longer look overqualified for the more numerous junior / "regular" developer positions.

While your work from the 90's is likely very interesting, for many companies the soft skills and lessons learned will be more applicable to whatever role they have available, best included as a summary.

I promise that most hiring managers aren't going to read a 10 page resume, or even a 4 page one. 9 times out of 10, they just want to answer a simple question: should the team take time to find out more about this candidate? If the first page of your resume doesn't answer that, it likely won't make the cut.

On a final note, "30 years experience" really isn't a great sign. I have indeed worked with the type of person who has basically had the same experience over and over for 30 years, not growing, learning new technical or leadership skills, etc. That is totally fine for many positions, but it is mark against them for many others.