Skip to main content

How To Have Too Much To Do

I've got a lot of things I'd like to tackle and I just wanted to layout some of the things on my mind lately. Many of them are small, so maybe I'll even complete a few before 2008.
  • Launch a small, free service that uses a del.icio.us account to take social bookmarks and forward them to Twitter or Jaiku or Onaswarm automatically.
  • Learn how to write a Firefox sidebar application and replace the crappy TwitBin. I want to only see the most recent status from each user and to remember my preferences better.
  • Develop a small desktop tool to grab my bugs from FogBugz and let me track time offline. This will come in handy when I travel around the holidays.
  • Get reacquainted with Nevow and Athena for a few small games, like TicTacToe and Squares.
  • And, as I write this, I want something that will take highlighted text and replace it with a link to a Google search for the text. Easier than looking up the links to everything I just mentioned!
It really seems like an OK plate, now that I have it written out.

Comments

Jeremy Cantrell said…
Not sure how you feel about GTK, but I wrote a couple of apps using pygtk and glade over the thanksgiving holiday. it was my first venture into pygtk+glade, and the separation of presentation and logic was nice.

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

The Range of Content on Planet Python

I've gotten a number of requests lately to contribute only Python related material to the Planet Python feeds and to be honest these requests have both surprised and insulted me, but they've continued. I am pretty sure they've come from a very small number of people, but they have become consistent. This is probably because of my current habit of writing about NaNoWriMo every day and those who aren't interested not looking forward to having the rest of the month reading about my novel. Planet Python will be getting a feed of only relevant posts in the future, but I'm going to be honest: I am kind of upset about it. I don't care if anyone thinks it is unreasonable of me to be upset about it, because the truth is Planet Python means something to me. It was probably the first thing I did that I considered "being part of the community" when I submitted my meager RSS feed to be added some seven years ago. My blog and my name on the list of authors at Plan

Pythonic Defined

Introduction Losing is Good Strings Dictionaries Conclusion Introduction Veterans and novices alike of Python will hear the term "pythonic" thrown around, and even a number of the veterans don't know what it means. There are times I do not know what it means, but that doesn't mean I can define a pretty good idea of what "pythonic" really means. Now, it has been defined at times as being whatever the BDFL decides, but we'll pull that out of the picture. I want to talk about what the word means for us today, and how it applied to what we do in the real world. Languages have their strengths and their idioms (ways of doing things), and when you exploit those you embrace the heart of that language. You can often tell when a programmer writing in one language is actually more comfortable with another, because the code they right is telltale of the other language. Java developers are notorious for writing Java in every language they get their hands on. Ho