Personal review:
A good recap of his previous writings and talks on the subject for the first third, but a bit long. Having paid attention to them for the past year or two, my attention started drifting a few times. I ended up being more impressed with how much he's managed to condense explaining "enshittification" from 45+ minutes down to around 15.
As soon as he starts building off of that to work towards the core of his message for this talk, I was more-or-less glued to the screen. At first because it's not exactly clear where he's going, and there are (what felt like) many specific court rulings to keep up with. Thankfully, once he has laid enough groundwork he gets straight his point. I don't want to spoil or otherwise lessen the performance he gives, so I won't directly comment on what his point is in the body of this post - I think the comments are better suited for that anyways.
I found the rest to be pretty compelling. He rides the fine line between directionless discontent and overenthusiastic activist-with-a-plan as he doubles down on his narrative by calling back to the various bits of groundwork he laid before - now that we're "in" on the idea, what felt like stumbling around in the dark turns into an illuminating path through some of the specifics of the last twenty to forty years of the dynamics of power between tech bosses and their employees. The rousing call to action was also great way to end and wrap it all up.
I've become very biased towards Cory Doctorow's ideas, in part because they line up with a lot of the impressions I have from my few years working as a dev in a big-ish multinational tech company. This talk has done nothing to diminish that bias - on the contrary.
Math underlies programming in a similar fashion to how physics underlies automobile driving. You don't ever need to know about newton's laws of motion to pass your driver's license and never get a ticket until you die. At the same time, I will readily claim that any driver that doesn't improve after learning about newton's laws of motion had already internalized those laws through experience.
Math will help your intuition with how to tackle problems in programming. From finding a solution to anticipating how different constraints (notably time and memory) will affect which solutions are available to you, experience working on math problems - especially across different domains in math - will grease the wheels of your programmer mind.
Math on its own will probably not be enough (many great mathematicians are quite unskilled at programming). Just as driving a car is about much more than just the physics involved, there is a lot more to programming than just the math.