August 27th, 2004

Telling computers what to do

Lately, at my main day job, there has been a frenetic pace of programming. We have a lot going on. Three major projects are all going live at about the same time. I'm not sure anyone understands just how frenetic it is, except for the other guy I work with, who is similarly busy.

In one respect, I like it. I'm churning through obstacles like butter, writing code and just running for implementation at full tilt. I feel myself functioning at a very high level. I'm not sure how much anyone at work appreciates that, but I certainly appreciate it myself.

Really, I'd like to test the code a bit more. But there's not much time. My own hours are officially limited to 35 hours a week, so it's all about knowing what's actually essential and getting that done and slapping it into place for go-live.

Just-in-time programming you might call it.

If we get the essentials in, there will be time afterward to clean it up and tweak it.

Rhyme of the day:

Figure out what you really need,
Then code at full speed.

Into the Secret History

I've started (about 50 pages or so) into Donna Tartt's novel, The Secret History. I was persuaded to give it a look by Shannon Ringvelski's eloquent lecture on contemporary fiction this summer at the Objectivist Center. I'm liking it so far. It's giving me a very ominous feeling. It somehow reminds me of Dostoyevsky, although the prose is quite different.

Not the rhyme of the day:

I don't have an addiction
To contemporary fiction.
But I quite enjoy start
Of this "Secret" book by Tartt.