I kind of disagree. It’s not like people are printing out or even reading back that far. May as well include it, but certainly don’t expect people to read it.
I’m currently hiring and reading a lot of resumes. I rarely read past the first 2-3 pages, but sometime when I’m curious go back to learn more about career path. Has someone been programming for 30 years? Or started as a dba or a support tech?
I think it depends on the risk of including it. If you worked for an embarrassing employer or maybe don’t want people to guess your age, remove old stuff. But otherwise, I suggest just spending more effort on making the first page relevant.
One page! Put the most recent relevant stuff on one page and send that. I don't agree with the idea that it's OK to include more info because people don't have to read it. They do have to read it because it might contain a red flag.
Every word you type is making work for someone, and if it's not then why write it?
For my resume, I add on new items after each position or paper or new thing or whatever. So I’m just adding on new sections every few years. If I was starting fresh I probably wouldn’t write pages and pages.
I agree that the first page should contain all essential information. But as for the extra pages, people only read if they have some reason.
Someone who has been programming for 25 years, starting in the trenches is different from someone who changes careers in the 00s and learns programming.
And I prefer some context to know what someone means as if it was just a line for “FooCorp 1995-2000, Programmer” does that mean FORTRAN or excel macros?
The considerations I take about scalability, RTO vs RPO and my entire system design and process decisions change when I have unlimited capacity and the ability to scale to zero.
My experience programming in 65C02 assembly in the 80a doesn’t make me a better developer today.
I personally have been working professionally since the mid 90s. But I realize that no one cares about the fact that I did C on DEC VAX and Stratus VOS mainframes in the 90s, VB6 in the early 2000s along with C, C++/MFC/DCOM or C# for ruggedized Windows mobile devices in the late 200x. I’ve cut out everything on my resume before 2012.
Your resume is full of responsibilities. But not accomplishments. If I were to ask you why should I hire you over the dozens of other generic developers who run across my desk, what about your career sets you apart? I’m being completely hypothetical. I’m not in a hiring position and I’ve only been in one for a brief stint in my career. But put yourself in hiring manager’s shoes. Why would you hire you?
I’m not sitting on high judging you by any means. I’ve had a fairly unremarkable career myself until 2018 and nothing that really stood out.