who loves a challenge
This has been a tough few days. The cause seems to be that a) I love a challenge, and b) I love to code, and c) I love having lots of open projects so they can all connect to each other and become better. In other words, I can get overextended, overcomplicate matters, and never really come to closure on things. In other words, I've become one of those cats that are difficult to herd. In other words, a programmer.
The cure, is to continue to work hard and with the highest amount of integrity possible. The way to increase integrity with my work (perhaps yours too) is a) care more about the work itself than what other people might think of you, and b) care more about the work itself than keeping your job. The other way of thinking about this is, if you're concerned about your paycheck, and the popularity contest, and the implicit connection between the two, you will operate from one of the lowest and self-serving spheres of integrity possible. (Obviously I've learned this by falling for this one myself, so don't think I'm holier than thou).
I'm reading QuickSilver, speaking of a challenge. It's due back at the library the end of the month. I have, um, 500 pages to go. I should probably just return it unfinished, but I was on the waiting list for a year to get the reservation.