This typifies the trap I think a lot of us fall into sometimes, particularly programmers. We get so caught up in trying to find technical solutions to a perceived problem that we don't take a step back and ask if what we're trying to do makes sense at all.
Why do you want to listen to an audio book AND program at the same time? If both require your full attention then do them separately and so you can give it to them.
If you really are only interested in a small number of "important bits" in your audio book then maybe an audio books is not the right form for that information. Text is a lot easier to skim read, maybe you can even find a plot summary somewhere to speed things up. Or maybe you want a heavily abridged version of the audio book where it just tells you the important plot points, but that doesn't sound like very much fun.
Why do you want to listen to an audio book AND program at the same time? If both require your full attention then do them separately and so you can give it to them.
If you really are only interested in a small number of "important bits" in your audio book then maybe an audio books is not the right form for that information. Text is a lot easier to skim read, maybe you can even find a plot summary somewhere to speed things up. Or maybe you want a heavily abridged version of the audio book where it just tells you the important plot points, but that doesn't sound like very much fun.