As always, it depends.
It depends on whether you're planning to work all by yourself, in a small team, in a large team or even in a big comapny (like EA).
If you're planning to do everything by yourself you'll have to learn everything: persistence (databases, xml files, binary files, text files), visual side of the game (flash, open gl, direct 3d, or even something else), writing logic of the game (any programming language will do) and stitching everything together (build systems, shipping, copyrights).
If you're planning to work in a bigger team your set of responsibilities will shrink. For example you'll be responsible for creating models, or physics, or game logic, or game scenario.
If you're really good at designing games (what the game is about, its scenario, goals and playability) maybe you'll find a position where you only write scenarios, draw models (on paper) and explain the ideas to developers.
Long story short: many people involved in gamedev are not developers/testers/graphics designers, so you still can do what you feel you're good at (designing games) without programming skills (developing games).