No-one will start with a blank screen in the morning and start to write code, just because. You need to have an itch, something you want to solve. Writing code is the means, not the goal.
Think about your support job, and ask yourself what tool would really make your life easier. Then set out to write that tool. You have the target people sitting around you right now, solve your problem and solve theirs too. If you're lucky, the tool will be valuable enough for the company to take it to that next country, all while you keep supporting that code.
I did this many years ago, while working as tech support for a tape vendor (Exabyte). I found their customer tools rubbish, so I started writing something easier (Expert 7 for MS-DOS). I asked my wife to test it for me (she is not in IT), just to see what she struggled with and made it better. It took me a while, but in the long run the company made my tool the default for customer support. I have kept on supporting that tool and many others after that until the end of last year. For almost 20 years those tape tools have given me part of my income. Even today, I still have a few customers asking me to code for them. LTO-7 is coming, perhaps I'll be asked to integrate support by then.