Developing Upwards

I've been putting a lot of though to my ongoing desire to write something in the way of a video game. This was my original foray into programming and I just didn't stick with it. Turns out I am such a geek that I actually found database design and protocols more interesting than first-person shooters. Go figure. Still, the old dream burns inside me. I've spoken with a few people here and there that could gain interest if I started something, and I'm thinking the time is arriving that I buckle down into the nights and see what I can do. I've been looking pygame versus pyglet and hoping to find a ready-to-use accelerated sprite library. Although I really want to write a straight Python, installable game, the lure of the web is strong. There are a lot of fun ideas I could try there, and probably a much larger audience I would reach. Of course, there are pros and cons to both. Web-Based Installable Pros Zero installation Higher number of users One target platform (for t

Brett Cannon is considering an import tutorial for PyCon '08, focusing on his new work in the area. I've caught word here and there about talks people are working on, and even had a suggestion to make a talk proposal myself, which is silly. I haven't a clue what I would be able to talk about. I sure would love to listen, and watch, and chat with everyone else. I'm really wondering how likely it is that I could make PyCon '08 the one I am finally able to attend. For Work This Means... I have a pretty flexable schedule at work and the boss is a great guy. (No, Van, I am not just saying that because I know you read my blog.) Still, I have no idea what prospects I would have for taking the time to attend PyCon, but I'll deal with that when I decide for sure that I want to try to go. Well, I know I want to go, but I have to make sure that I personally can go, before I figure out if I can professionally go. For Family This Means... Either Heather will want to come alo

Well we finally moved into the new office space. It doesn't feel very strange, of course, as I have only been in the old offices for a day over two weeks. Still, it is some feeling. We've got a nice, open space. I'm really loving the use of a long ledge along the one wall as a single, extremely long book shelf. The power and network running down poles at two points in the space allows us to encircle desks around for great collaboration. I'm a little worried about the lack of any personal space barriers, but I don't see it will be a great problem. I really wish I had gotten one of the two desks with their back to a corner, but Daniel grabbed it up pretty quick. He's been there as many months as I have been there in weeks, so I can't really complain about his getting first dibs. Now that we have the new space, I have my keys and I can leave a little early to avoid most of the traffic. The old leaser of the space was an embalming office. It makes the existence

My first full week at Social Serve ended yesterday with me jetting out early to try and avoid the rush hour traffic on top of race weekend conjestion going past Lowe's Motor Speedway. Turns out, everyone else had the same idea. Still, most days I seem to be able to make good time if I just get out before the real traffic clogs the roads. I've learned a few tricks, as well, like avoiding I-77 completely on the way home in favor of Brookshire all the way to the 85 junction. Avoiding the ramps between three interstates makes a huge difference. The work itself has been good. I still am learning my way around the existing code, and making my fair share of suggestions to improve things with all the stuff I see from the Python community. I'm looking forward to doing some fun stuff. I've joined the commit team on the GeoPy project to push some patches and further work I've done on it for Social Serve. Where things are is a surprisingly difficult problem to deal with.

Here are my instructions to anyone else who may want to work at SocialServe.com: Have a strong enough interest and passion for development to start a contracting business without any formal training. Support yourself for about a year and a half working for one client and the next. Move to an area populated enough to start a user group for your favorite development language, tool, or concept. (Mine was Python) Be suggested to send in a resume to the company of one of the first members. Sweat your way through the first real interview for the kind of job you've wanted your whole life. Cross your fingers not to screw it up. So, that's my story. I had my interview last Tuesday, called Thursday, and started Friday. I've enjoyed it a lot. Learning my way around the codebase has been going pretty well and I've already got my first couple of commits in, as well as two small projects. I like to think I'm moving along nicely. One of the things I need to get used to is that all