Another small tip: measure then optimize. As long as you understand how to use state properly (which isn't hard once you get it), Compose is pretty smart about optimizing your code, and will usually perform perfectly fine even if you don't do things optimally.
Only start looking into the deeper trenches of "argument stability" and other areas when you actually notice performance issues. Premature optimization is just a waste of time.
And yeah, feel free to ask about anything you don't understand or struggle with in this channel!