Skip to main content

My Top Ten Goals for 2010

Call them New Year's Resolutions or whatever else you want, but we all should have some goals and we should lay them down. Of course, I'm not sure if its better or worse to make these goals public. I'm just doing what feels natural.

  1. I'm going to move this blog away from Blogger and Blogspot and self host. I've spent the last couple days building a new server, for personal and future business use. I really like the setup I've built to launch and manage a bunch of domains easily. It should be a piece of cake to set up, but migration I'll have to look into the details on.

  2. I will launch up to ten websites in 2010. Some of them will be very small and nifty. Some of them will be undertakings and hopefully profitable.

  3. I'll put more focus to my "Personal Brand" and to my business as an actual business, rather than a dude who does stuff for cash. I won't let that business face become cold, however.

  4. I will read 50 books. This one is tougher, because I know I keep loosing track of my goals when I try to read more often. If I set page-a-day goals, I can get books into my regular cycle of media consumption again. I'm restarting and completing the Wheel of Time series, first.

  5. I will write at least one book. This includes the editing, so I hope to finish more rough drafts, as well. I used to write constantly, and I never do it anymore. This blog is evidence of that, but I don't only mean technical writing. I miss writing fiction as much as I miss writing it.

  6. I will paint at least one painting. I haven't painted anything for a decade.

  7. I will relearn how my guitar can relax me. I'll probably submit some recordings to Sound Bush.

  8. I will do science with my son. We will get shirts that say so.

  9. I will write a JetPack extension.

  10. I will finish and submit the patches to the dozen or so projects I've made internal modifications to in 2009 without time to clean up.
You can see a list of my other and upcoming 2010 predictions.

Comments

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

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful

How To Teach Software Development

How To Teach Software Development Introduction Developers Quality Control Motivation Execution Businesses Students Schools Education is broken. Education about software development is even more broken. It is a sad observation of the industry from my eyes. I come to see good developers from what should be great educations as survivors, more than anything. Do they get a headstart from their education or do they overcome it? This is the first part in a series on software education. I want to open a discussion here. Please comment if you have thoughts. Blog about it, yourself. Write about how you disagree with me. Write more if you don't. We have a troubled industry. We care enough to do something about it. We hark on the bad developers the way people used to point at freak shows, but we only hurt ourselves but not improving the situation. We have to deal with their bad code. We are the twenty percent and we can't talk to the eighty percent, by definition, so we need to impro