I started with Basic, long-long time ago...
Then mid-nineties I became a professional content designer, so I learned HTML/JavaScript, later on CSS/XML/DHTML, tho I'm no expert on the latter whatsoever, and web content has changed a lot since then (PHP/MySQL, Flash etcet.).
I never used 'real' programming languages, though I studied C/C++ and Java.
AppleScript and AutoIt were my first favorites, then some three years ago - I guess - I discovered AutoHotkey, and am still using it. It does all I need.
Been working for a Fortune Top 100 company (a company y'all know and love/hate, but I'm not going to tell, and no, it's not Microsoft

) for the last four years, and have created a load of in-house tools with AHK, that really speed up the average work of the average Joe's and Jane's around here (and my own, ofcourse).
One of the biggest advantages of AutoHotkey is that any bugs/changes/requests can be fixed/implemented in only
a fraction of the time it would take to change something programmed in e.g. C/C++ or Java, so, especially the in-house tools, can be adapted to changing circumstances
easily and fast, which is perhaps the greatest strength of AHK. Try to do that with a 3rd party full-blown app.
It may take some time to convince management of the usefulness of AHK, especially the Open Source thing freaks many out for some reason, but frankly you just need to convince them to allow you to sit at someone's desk for half an hour, check on what he/she is doing, and write a small script that speeds up some of their actions. Present that to management, and it will not take long to convince them to take a shot at it... :wink:
And, don't forget to mention that it's free, and the compiled scripts need not be published. To convince the sheep up-the-ladder, I implemented a system that checks the userid/hardware id/ip and doublechecks against an app on a server. Moreover, the scripts are per-user compiled with private keys, double (once in-script, and once for the encrypted compile), and all user settings are saved encrypted. So,
no way an employee could take a script/app home and use it from there, or from anywhere else (one of the biggest fears of management if you build tools that access internal servers for example).
If you can demonstrate it's usefulness, I'm sure your boss will consider using AHK. (Just to let you know what you might face if you suggest using AHK at work, it took me quite some time to convince them, but that might be the company). :wink:
Now I will be changing to another company next month ( 8) ) and will be pushing hard to consider using AHK there too. :wink: