This is something that really helped me learn the Octatrack.
I would say this is also good advice. Create a “sandbox” or “playground” project and don’t worry about “breaking” stuff in there. Just practice, try different things out, don’t worry about the results. Removing the frustration of “mistakes” will allow you to concentrate more on the workflow and getting that right.
The biggest thing for me, though, since you mentioned the model:cycles is to get familiar with difference between how sounds are managed on the Octatrack. On the M:C, sounds are stored in each pattern. On the Octatrack, each pattern will use the same sounds (samples) unless you change parts. That’s a high-level, quick overview of the main difference, but it’s critical to know. You’re going to create a pattern in the OT, then change a sample in a new pattern and wonder why your original pattern is all messed up. It’s OK - we’ve all done it!
Check out elektronauts (tons of information there), or come back here with questions.