As a QA tester for a software suite, I find that I have to install/uninstall builds daily, change system configurations in batches, etc. I find I regularly create .bat's, .vbs's, and .exe's to script actions that I have to repeat regularly with my job. I have a folder of these on my desktop, and use them fairly frequently. I didn't bother with any sort of error handling into them because I didn't have "approval" to write them and wanted to minimize the dev time (most were written in less than 20 minutes), and never expected them to leave my desktop.
The problem is, coworkers have seen me using them, and they would like me to share. If I distribute these utilities, I know that I will suddenly have to support them and anything wrong will be blamed on me, possibly implicating me in damages, and damaging my reputation for something that is really outside of my job description anyway. I'm willing to take the risk of some edge case causing an error condition on my computer (I will probably be able to fix it with little effort), but I'm hesitant to allow that on coworkers computers that I have no control over.
I want to share the tools I developed but I don't have the time or budget to ensure that they're safe for use by colleagues that aren't aware of how they work or what could go wrong.
- Should I mention the risks and keep these tools to myself?
- If I want to share them, how do I ensure that they're used with caution and that any problems caused by their use don't reflect on me?
- Should I make the case for further development of these tools and, if so, how?