My current rule of thumb is: if I know how to write it correctly, then I write it correctly. If I don't feel confident, I write the dumbest / most direct version that works to get the feel of the "lay of the land", and then refactor it later based on the new experience.

I like this rule (don't remember who said it): "Write code that is easy to remove, not easy to extend".