I am sure there must be many better or more efficient ways of learning fastai library, but somehow I find myself keep coming back to this hard and uncool approach. In case you are alike, what I have been doing may be a little help for you to march on the same path. But first, let me explain what do I mean by uncool and hard.
What does uncool mean?
- not apply fastai on interesting and fancy applications
- not even working on notebook demos
- but focusing on source code notebook tests (fast, short examples) only
What does hard mean?
- taking each func, class, method out of the source code notebook
- wrapping it up into a single .py file to experiment and ponder its meaning and usage
- it is hard, because you force yourself to walk through each life of source code
- keep revising every .py file like this PrePostInitMeta.py to keep enhance the understanding of its usage in itself and in the big picture in relation to other classes of the library.
Why I do this?
- mainly because I am a boring person (hate to admit), I don’t have any project which is interesting enough and feasible enough for me fully focus on
- also because I want to see progress, even just a little, everyday. a func per file, is doable!
- because If I manage to persist to the end, I expect fastai-v2 to enable me to be much much more …
If you are interested, here are those little .py files I have created and have been exploring everyday.
This is an on-going project, I have only just started, you are welcome to join and discuss the usage and understanding of fastai-v2 here with me (though Jeremy recommended to jump in when it is officially release, because currently v2 is adding and removing classes/funcs everyday). I will try to update my experience with this approach here.