> I think specifically I would second guess myself for the syntax of the cards I was creating - and if there was another better way to do it.
This kind of perfectionism has also been bothering me. ("I need to write the card perfectly, or else it's not even worth doing or even actively harmful.") But there's a couple of points worth remembering to change this belief:
1) If a card is bad, you will notice it when reviewing. It will be difficult to remember (i.e. you will fail the card often compared to other cards); it will be annoying to review (there's a general sense of "ugh" and/or confusion when you see the card); it will be unexpectedly time consuming to review, etc.
2) Bad cards can always be refactored. You can suspend the card (where the card is still in the database, but removed from the learning queue); reword; or split into multiple cards.
Michael Nielsen [0] gives an example of a card which asked for the syntax for creating a symbolic link in Linux. He always messed up the order of the filname/linkname, so he created an additional card that explicitly asked for the order of the filname/linkename in the ln-command.
3) The only way of learning how to make good cards is by just starting making cards, and then noticing which ones don't work.
When a card doesn't stick, it's useful to ask yourself what doesn't work and why. Is the back side surprising when you reveal it? If so, maybe rewrite the card to add more context to the front to make it clearer what you're asking for. Do you always miss one or two pieces of the answer? If so, maybe split the card into multiple cards, each of which asks for one part of the answer. (Or add an additional card to direct your attention specifically towards what you struggle with, ala Nielsen.) Etc.
4) There's diminishing returns on card improvement. Time spent on perfecting an already OK card is time taken away from creating new cards to remember new information. If your goal is to remember as much as possible in a given time, spending time on perfecting already existing cards is trade-off not always worth making. (The quote: "a poem's never finished, only abandoned" comes to mind to highlight this.)
[0] http://augmentingcognition.com/ltm.html