Well, Agile Manifesto is a strange thing a bit like an iceberg. Seeing it is one thing, but the understanding and imagination of what remains unseen is another.
I started coding in 90's. It was pascal I think. First time I got payed for coding in 2000 or 20001. Industry experience since 2003 or 2004.
Maybe, back then, it happened to be agile somewhere (but named differently). In my world, developers weren't so educated about project management and coding rules were foggy and unclear as well. Everything was slowly evolving and experience was gathered here and there. Agile Manifesto looked like this:
Individuals and interactions over processes and tools
Of course there was not so much knowledge about processes and not so much tools. In-home developers worked - back then and now as well - in small teams of friends where project management isn't so easy to implement and tools are usually too expensive. So it leaves you with individuals and interactions alone.
Working software over comprehensive documentation
I really do not know even single one developer who would like to work on documentation. Really. In-home developers do documentation only when sponsor asks them to do so. Quality of such documentation is the other thing as well as "working software" term. Today we know many indicators of quality and customer satisfaction and collaboration so "working software" means whole different thing than years before. TDD, user stories, code coverage is relatively new and even now I wouldn't bet in-home developers do all of that.
Customer collaboration over contract negotiation
Responding to change over following a plan
Few years ago it was almost impossible to sign an agreement where sponsor would not get: clearly described what product he will get, when it will be ready, how much will it cost and what milestones you should achieve to get paid at all. Collaboration meant that customer will change the requirements in the middle of the project (sponsor would name it being more descriptive) without changing the contract or a milestone plan.
I am not making it up. It was common mindset among the customers. It took years to change it but don't ask me who did it.
Only now I can imagine signing a contract where there will be rather description of some iterative developement process with two-side involvement than a nice looking, strict plan that nobody understand in the same way.