Sounds like agile methodologies; doesn't sound like agile manifesto. Which is kinda the point. The manifesto is a few salient points and heuristics that devs at the time found effective for delivering working software (and which, I would contend, still hold). The methodologies that have arisen are overly prescriptive, adopted without any eye to the culture, and frequently lead to outcomes no better than what they're intended to replace.
at least with how "agile" is set up at work (with SCRUM and SAFE (scale agile framework)), yes
I started programming professionally in 1989, and I delivered a LOT of software for a few different companies before the Agile obsession hit. I had a quite a lot of freedom to modify the process depending on what the project called for. There were fewer corporate overlords worrying about whether I stuck to this or that process. There were certainly no Agile Coaches making sure I followed all the ceremonies of the "Agile Process" (that's a quote) or making sure I used story points instead of calendar time in my estimates.
Making software is a lot less fun these days than in the "bad old days" of the alleged waterfall process.
For the historical cruft we’re getting there, I’m sure there’s teams mandating to stand during stand-up even during remote sessions.
Even if we loose time with lots of stupid things we are required to do the same work as if we had the whole period free. So, the code quality has to suffer and tech debt is accumulating.