things that we don't like, and later do like

Fri, 31 Mar 2006 21:49:00 GMT

For me, perl started out as this programming language that I didn't like because schallee liked it. I had a boss in my summer-job days who liked perl though, so I was forced to use it long enough to realize its power, and now I sometimes joke that English is a second language to my first language: perl (yes, I am a computer dork).

TWiki was introduced to me as this web application that I had to get working ASAP on doublethink, because they fired the only person in The Company who knew how to keep it running. At first I didn't want to use it any more than required to in order to get the job done. Now it is an integral part of the way that I plan and keep track of tasks, and bits of information which needs to be taken care of. I can't imagine living without it, frankly.

(incidentally, TWiki is written in perl, so these things that we don't like at first but come to like tend to build on each other)

There are a lot of things like this, but now that I am looking for work I am actually thankful that I got stuck with TWiki in my last year or so at The Company, because it gives me something concrete to talk about when people ask me certain kind of IT related questions now that I am looking for a job. It really was a good experience, though it didn't seem like it at the time.

Now I am seeing other things that I'm supposed to know that I am sure I will be extremely resistant to adding to my tool set, mainly because they will be some amount of work to learn and (ironically) they aren't perl or TWiki or one of the many other technologies that I already know. Which ones will I later be glad that I know?

I put Photoshop, along with dark room experience and studio lighting on my resumé in part because I had some of that kind of experience, but mostly just for fun, because I couldn't imagine possibly ever using that in my job (which is a pity). Today I actually gave my resumé to someone and he was like "oh, they would actually like someone who knows a little photoshop in addition to all this computer stuff."

doublethink

Fri, 07 Jan 2005 17:55:00 GMT

Doublethink means the power of holding two contradictory beliefs in one's mind simultaneously, and accepting both of them...To tell deliberate lies while genuinely believing them, to forget any facts which become inconvenient.

George Orwell 1984

Abuse of words has been the great instrument of sophistry and chicanery, of party, faction and division of society.

John Adams

Doublethink is also the name I chose for my web server at work. It is named for the application it runs, which collates information collected by BigBrother (a component of our tool software which tracks usage) and presents it in a readable way. At some point I inherited a Twiki which is also hosted on doublethink (the machine).

Last year when complaints about the web servers performance were made, I said that the machine needed to be put on a faster network. There is no technical reason why this cannot be done. When I'm at home and I need a new fast Ethernet port, I go to Best Buy and purchase one... here is one for $39.99 [broken link]. The reason this cannot be done at work is that there is security on the port at work so that the IT department can charge us per computer instead by bandwidth. Charging by bandwidth would make sense, since that is the service they are providing, not use of the computer. That is neither hear nor there.

So, as mentioned earlier, there was an "experiemnt" on Wednesday to see if the web server would run faster, as I said it would, on the faster network. The LAN team's position is that the performance problems have nothing to do with bandwidth, but the speed of the machine. Put succinctly, this is rubbish. I knew this, but I ran the test anyway, and sure enough twiki and doublethink (the application) ran much faster on the faster network than it had on the slower network.

I felt vindicated by this result and assumed that we could now push to get port security turned off in my office. I know this has happened for other high priority projects, and now that the managers are using twiki, this has become a high priority.

The guy who is spearheading this little adventure just came by my office to tell me that they are getting me a new computer to replace doublethink (the server). Normally this would fill me with rage because they are obviously not listening to me, but because of recent events I view the entire affair with a rather comforting sense of detachment. Why should I complain, after all, if they give me a new computer? Even if I didn't ask for it.

Still the original doublethink - still humming underneath my desk for now - and I have been through a lot and it will be sad to see her go.

The Twilight Report

things that we don't like, and later do like

doublethink