No AHK at work??
Posted 19 March 2010 - 01:43 PM
I could write a program in C that could absolutely screw anything over, does that mean I shouldn't be able to write any C?
Has anyone else fought this battle at their workplace and if so, did you win / lose what were the arguments presented?
Posted 19 March 2010 - 01:58 PM
So the business had to start fighting against "why it makes sense to have security if you don't have any more customers" :lol:
TBH, beside that I agreed to the security group that AHK will be used for the current (billing) processing only, and if users want to get it as well they've to officially request/license it internaly --> and download it from an internal destination!! We're still in business 8)
Btw, please move that thread into GeneralChat (where it belongs to). Thx
Posted 19 March 2010 - 02:05 PM
Posted 19 March 2010 - 03:50 PM
I liked the comment about that temporary process, gotta love the word "temporary" in a business setting - you know that thing is going to be around for a long time . Good to hear the business went to bat for you, unfortunately the business is not directly utilizing any of the things I've used AHK for yet However, I am gaining a small following of developers with the last utility I wrote, so perhaps that can give me some benefit as well.
Posted 22 March 2010 - 08:38 AM
Explain to them how it will take you 3000 hours to write something in C or C++ (& how much they will be paying you for those hours). Then tell them how long it would take to write it in AutoHotkey.
Maybe even give them a real-time demo of creating a "Hello World" msgbox...AutoHotkey: 1-line of code / 3 secs...C/C++: maybe 15 lines of code, time to write it, compile it, link it, make sure you didn't miss a semi-colon, re-compile it / 3-5 min (unless I'm under-estimating)...
If you "lose", you get paid more (more hours). If you "win", you get AutoHotkey at work! If you get fired, well, then, find a company where you CAN use AutoHotkey...& laugh at the guy who got your job at the old company.
Posted 22 March 2010 - 02:45 PM
as far as seciroty concerns you can store approved scripts on a server and make it so it requires password or some other approved authentication to dl then make the first line delete the newly downloaded script remove the tray icon. this in essence prevents to those who arent especially trying to from viewing the code.
rename autohotkey and remove the helpfile to obbscure the tool your using from the unwitting user
finally, IT depts are coslty most work by setting billable hours against the company for each project. My brothers with real skills are hampered from being efficient programers by red tape. a lone ahker is not.
My justification for autohotkey was proven in the first year with over 2 million in efficiencies saved cost of inaccuracy enteirng the same data in different systems only to have to have someone go back and correct it due to the customer finding out. and actual man hour reductions.
last year initiatives i wrote produced over 6 million in loss reductions. I might add i work in banking. I am but one of a team of 8 and the above was just my solo contributions. if those kinds of savings arent realistic thats fine but at the very least you should really drive home the poiint you can write this app that will save x dollars a month/year etc
Posted 22 March 2010 - 07:46 PM
Posted 22 March 2010 - 08:19 PM
Which gives them hope that at some point we all make ourself redundant :wink: So I explained my colleagues that there's only one chance to survive: learn to script!
A potential savings of $60,000 was enough to persuade them.
We expect that these CEOs ...
... might need minimum one of us to do the maintenance if necessary.
Posted 23 March 2010 - 04:11 AM
Posted 23 March 2010 - 04:55 AM