How to Write End-to-End Tests for Legacy Code

The approach is not something that I invented. There's a really good book about this called working effectively with Legacy Code by Michael Feathers. So what do you do? Is it all about trying to create as many tests as possible as quickly as possible? That kind of seems like, you know, really hard, tough going as something to begin with. Yeah. But if I approach an existing system that was written in TDD, then no one needs me there. If someone called me in, it's because they are unable to change their software and they need help to make their software changeable. And so where would we start? We start by writing an end-to-end test