Ask HN: How do you manage local development with a microservice architecture?

I work at a fast-growing company, and we've moved to a microservice architecture over the last couple years. I'm beginning to observe a lot of waste with our engineers trying to get 3, 4, 5, or even more microservices to work locally on features unrelated to those services. I understand that the 'right' answer is to build software with few dependencies, but we didn't know we were heading here initially, so it's probably too late to rearchitect major pieces of the platform.

What are practical strategies you have used to reduce the type of waste I've described above? Thanks!