Hi, I agree with @runjaj and understand @ahp378 point of view. I would add:
have in mind a practical problem to solve with Pythonista (a program to calculate something, or a graphical app with keys and text fields, or a game, ...)
divide the practical problem in little problems (if possible)
learn to solve the little problems (before independently that is easier and then by linking them together to recreate the main big problem of point 1) by:
a. searching for an existing piece of code that solves the little problem 'x' (a big database of Pythonista scripts is this
). if the piece of code solves your problem ok, if not try to modify it by changing numerical values or easy parts (with an empirical approach, and if the piece of code is well commented, it is easier).
b. if you can't find existing pieces of code, starting to read documentation having in mind that it could be not updated or incomplete (but it is very big).
The best documentation could be in my opinion a big with easy to find/search feature database of common recipes/pieces of code for all Pythonista features (objc, scene, sound, location, console, etc...). The big database (the one by tdamdouni is an example) would be created and maintained by people with different curiosities and interests, in this way community could help itself about common pieces of code and without bothering the only person who maintains the Pythonista software and its big documentation (@omz).