I guess in terms of concrete advice:
1. Put time on a calendar to work with this person; don't just slack back and forth about some specific issue for a bit.
2. If you're looking to become a better programmer, actually pair with them - take turns driving and writing code. If she's doing the driving, it would help to hear out her rationale for what she's doing - probably even before she starts writing. If you're driving, try to do the same.
3. Ask for code reviews on as many of your pull requests as she can provide; this is going to be pretty workplace specific, and is going to depend on how much code you end up putting up for review and how much time she has. It's a good way to get async feedback.
And yeah, it takes time and practice.
You can also find others on your team whose work you admire and ask them similar questions. Lots of people are happy to talk about their work when asked.
The `only` time I speak with my mentor is when I get stuck with a bug and need help getting started. I have asked frequently on how to do better code reviews or how did she get so good at programming - she always said it takes time. To get better with the code base - it takes time.