After a few months of school, I got a job writing tools for site monitoring at a .com. There, I got into the idea of making things that made life easier. If you have to do A-B-C over and over, sooner or later there are going to be mistakes. But if you can make a tool that will do A-B-C, all you have to do is check the results, and you can spend your time on D.
At work, this means writing tools to automate test procedures. The current project is a script which will auto-install daily builds on test servers, then trigger acceptance tests. It's a real challenge because it has to work on three different operating systems.
At home, I user perl for processing mp3s. I have a huge collection that grows all the time. It's an easy task to edit the ID3 tag on one file, but after 100, it gets really old. Using perl, I'm able to automate a lot of the work.
I honestly don't know if it's coding that I like or if I like having the ability to do cool things with code. I guess it's the debate between process and result: did you enjoy the building of the house or the satisfaction of having built the house? Either way, I make hard/boring jobs easy, and get paid for it. Having worked as a DJ, a pizza delivery guy, a barrista, and a programmer, I can say that programming has treated me the best. What I'd say that if spinning records paid the same as churning out code is a different story.
"What do I want? I'm an American. I want more."
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>