My best advice is to acknowledge that workarounds will be necessary, and the application of that acknowledgement is that you need to establish what *doesn't* work, then post on these boards what you are trying to do, what seems to cause a crash, and then hopefully work it all out, with help from us if necessary.
Keen troubleshooting skills will get you far with this software. It should get better with time, and avoiding crashes will become closer and closer to second nature. You've probably learned how to avoid crashes with whatever software you'd worked on before. Now, since you're using different software, the workarounds are different. Ready-composed documentation would do wonders. Lacking that, I encourage you to start composing your own, gather from the Internet, complete with links so that you can reference stuff later on down the road.
Yes, it's not ideal. I'll be the first to agree. Look at my posting history as of early 2015 if you doubt my early phobia. If your experience becomes something similar to my own, you'll be able to get around decently after a while.
For what it's worth, reading your post elicited a sad, sympathetic laugh.