News for hackers. Stuff that matters.
Re:Ask HN: Percent of time spent developing internal tools? by btilly on Saturday November 10, 2012 @12:01PM (#4767057)
You miss the most common issue:

4 The task requires interacting with a system that was not designed with automation in mind.

For instance you have a third party GUI which you don't have source to that you have to push a button on based on what it is showing you. So you wind up having to research this, work around it, etc. Often you can use a GUI test kit to solve it temporarily, but that is going to be fragile - on the next upgrade it will likely break.

In this case automation may not be worthwhile. What you're learning is not connected with what you do. The automated solution is more fragile than the human one. The time saved is not that important.

Re:Ask HN: Percent of time spent developing internal tools? by rhizome on Saturday November 10, 2012 @12:53PM (#4767183)
The solution to that is to reimplement the functionality outside of the GUI. Write the GUI out of your life.
Re:Ask HN: Percent of time spent developing internal tools? by btilly on Saturday November 10, 2012 @02:06PM (#4767408)
Great if you implemented the thing with the GUI that you have to interact with. Not so great if it comes from a third party.

Even if your people did implement it, depending, getting rid of the GUI might be easier said than done. I remember an Access app that I had to automate stuff around. In the end the best solution to all of the different popups that were buried in their app was to make the machine it was on remotely accessible, and have a watching process page someone if it took too long. A human would then look at the screen, and press the appropriate button.

Re:Ask HN: Percent of time spent developing internal tools? by rhizome on Saturday November 10, 2012 @02:48PM (#4767536)
Yeah, I worked with something like that about 10 years ago. We had an ETL process that involved like 20 Access macros manually triggered in sequence (click, wait, click, wait...over several days per cycle). I converted this entire process to a Perl script that would be pointed at the raw data directories, clean and process the data and throw it into the DB. Access was taken completely out of the equation. It took a few months, but I was an IT guy who had never programmed before and had to learn Perl at the same time.