Regardless, kudos to her--this is a great way to learn.
I can't see anyone benefiting from less than a couple of hours of coding
That being said, when I'm not under extreme time constraints, I'm using other approaches. For example, for a whole week I'm reading and gathering bits of information I will need to build something. I have a large file, where I paste links, paragraphs of text from articles and write tiny little snippets of code, either mine or borrowed from somewhere. All this takes an hour or a little more each day (but it's nice that it can be divided into pieces). Then over the weekend I try to make this amorphous mass of data into understanding, in one or a few coding sessions.
There are other ways to make the best use of what little time we get, too. They'd better be, because otherwise we'd be royally screwed as working programmers :)
Here's another example of the "daily practice" approach from a different domain. A self-taught designer callled Mike Winkelmann has been posting his "everydays" on his website. From his site's description:
"Originally I started out drawing and did that everyday for a year. Then I decided I'd like to learn a 3D animation package so I did a render using Cinema 4D every day for two years. Then I did some photography and also Adobe Illustrator for a bit..."
http://www.beeple-crap.com/everydays.php
Edit: Just to add, another great post on the idea of practicing everyday from a motion graphics designer. I think it's applicable to any field:
http://greyscalegorilla.com/blog/2013/01/one-a-day/