Big Buck Bunny (previously Project Peach), the world's second fully "open movie" (the first being Elephants Dream), has been released! Grab a torrent and go!

It's quite a good little short. Much more accessible, much less experimental, than Elephant's Dream. It's also totally gorgeous, and gained enough attention that its CGTalk thread got frontpaged. CGTalk's community, in the past, was somewhat notoriously snarky toward Blender for just being a hobbyist's software, but from the talk going on, it's clear that that attitude is changing.

Great news for Blender, great news for the free culture movement, and great news for blenderheads like me! The direct collaboration between the artists and developers means great new features making it into blender's codebase.

And if you like the movie? Like Blender? Like supporting free culture productions like this one? Well then, consider buying a DVD so you can support the Blender Foundation. It's good for you, good for the public at large, and you'll feel good about it at the end.

Now I'm looking forward to the next projects coming out of the Blender Institute, including Project Apricot, the Blender-based Big Buck Bunny game, Creature Factory, a blender training DVD made by the well known Blender artist Andy Goralczyk, and lastly the whatever-successor-to-peach movie they're coming out with next (I hear it involves robots). Lots to look forward to, but in the meantime my Big Buck Bunny DVD is on its way, as is the ManCandy FAQ, a Blender character animation training DVD.

Mmmm. Mancandy.

Wow.

I've Been thinking about the way I currently organize my home directory, and I'm not sure it's quite the best. It's actually a lot more messy than this in reality, but here goes:

Directory Contents

~/bin/ What you'd expect... local scripts & executables.

~/backgrounds/ Backgrounds for my desktop

~/college/ College notes, essays, etc. Has subfolders of individual classes.

~/docs/ Writings and documentation, not by me.

~/devel/ Code-related projects I've created or have been involved with. I also have a ~/code directory that I'm planning on deprecating.

~/elisp/ Code I use to extend emacs. Some of it my own creation (and symlinked to ~/devel). Mostly stuff I've downloaded

~/gfx/ Graphics of my own creation, or that I've been involved with.

~/mail/ My local mail spools...

~/music/ Third party music. I don't make music, so this is all other peoples' creations.

~/Plans/ "Muse" files from Planner Mode. Personal notes and documentation, todo lists, etc.

~/programs/ Programs I've downloaded (and usually compiled from source) that I don't do any development for.

~/proj/ Some projects that are too wide encompassing to fit in a specific folder.

~/python-local/ Common python libraries I use. Normal setuptools-y directory. I'm planning on moving this into ~/programs/ soon.

~/records/ Stuff I need to remember, like how much my rent bill is and what my landlord's address is. Some of this is encrypted with GPG.

~/svn/ Some svn repositories I've set up. It's not one big repository in here, but several... one for ~/college, one for ~/devel, one for ~/gfx... you get the idea.

~/tmp/ What you'd expect... files I'm just downloading temporarily. I clear this out now and then.

~/vids/ Videos... pretty much all made by others, except for a few blender animations I hacked together.

~/words/ Writings, by me.

Well, that's the way it is ideally, at least. Now, this probably looks reasonably clean, but of course, looks can be deceiving. There's a fundamental problem with this design.

I'd like to have a distinction with projects I'm involved with and projects totally made by others. This isn't an issue of "fear of influence" or whatever. I think it would be pretty hard to be part of the free software/open source/free culture movements and such and be afraid to be influenced by or collaborate with others. Its just really convenient to separate the things I'm working on from the rest.

So anyway, how to reorganize things? The easy way would be to either have an all encompassing ~/projects directory that could have separate subdirectories for ~/code ~/words ~/gfx & etc. Or maybe I should do the reverse and keep all of my personal projects at toplevel of my home directory, and keep a ~/media directory for all files that aren't mine?

How do other people organize their home directories?

I'm working to reclaim myself. That might sound silly, but..

During the two years I was working at Google, I was going to both work and school full-time. I had no time to do anything I liked during those two years. I also spent most nights either trying to finish schoolwork or work on projects for work (I would stay up all night working on projects I was totally unpaid for, just because I wanted to learn, to prove myself, and to do good for the company). Overall, I learned a lot, and of course both my experience at Google and my graduation are both invaluable. But there have been other problems.

I gained an unbelievably large amount of weight, to the point that people who knew me several years ago often can't recognize or believe that it's me today at first, or people who know me today can't recognize pictures of me several years ago. I have a picture on my desk of myself and my siblings taken three or four years ago. One woman at my work came up to my desk, pointed at me, and said, "Who's that?" I explained, that's me before I worked at Google. She kept coming back and staring at the picture saying "No way..." One of my other coworkers I showed the picture to said, "Wow, Google can do that to you?"

Of course, it wasn't as much Google that did it to me (though the daily lunches we had seemed to increase the weight of almost everyone on our team over time) as much as the late nights drinking energy drinks, eating snacks, etc, just to survive the crazy schedule I was working through. (Also, I actually had started gaining weight just the year before they closed Barat... during that year they closed our cafeteria but maintained that all residents on campus had to invest a mandatory 1000 dollars every 3 months into a meal plan that we could only use at the coffee shop, where they served greasy muffins, chicken nuggets, etc. But the weight didn't really pile on until I joined Google.) As I said in a previous post, I also had stopped biking entirely once I got my car and moved into the city. This certainly didn't help either, as I pretty much was stripped of all forms of exercise, other than the daily busywork of the datacenter.

The sad thing about all this is that, due to image issues I have with myself that date back to my teenage years, I have a very hard time looking at myself in the mirror. I gained most of the weight in just a few very short months, and hadn't really realized it until I stepped onto a scale. After that point, numberwise it appears that my weight gain was not quite as quick and drastic, but until I got out of the work and school cycle, I kept putting on weight.

It's been nearly a year since I graduated from school and started working at Imaginary Landscape. During that period I haven't gained any weight, but I really haven't lost any either.

That is, until recently. I've begun biking constantly (I have a new schedule where I bike a little more than ten miles every morning before work... today it was raining, I am totally soaked), and I feel much healthier and have less desire to snack so much. I'm counting calories and eating a lot of spinach salads. And I'm seeing the effects: the weight is peeling off. I lost a lot of weight very quickly the first week and a half, and it's been slower since, but its going down. I am slowly adding more exercises to my schedule. I can feel the effects of this. Surprisingly, I'm even enjoying it.

It's going to take at best a year for me to get back to my pre-Google weight, and hopefully I'll succeed in that as I'll then be in shape for our wedding.

And so begins part one of reclaiming myself: reclaiming my body. I'm now also trying to figure out how to handle part two, reclaiming my mind.

So on my second day of biking in Chicago, I was doored for the first (and hopefully last) time. It wasn't that bad in my case... I saw the door opening, yelled "Hey!", and both braked and swerved out of the way. The driver was very apologetic, and I told him not to worry too much as at least nothing bad happened, but that he should be more careful. Recovering from his shock and embarrassment he said, "Man! I thought that stuff only happened in the movies!" I found his comment funny, but the whole situation could have been very tragic; I got away with nothing but a few bruises on the knuckles (which bounced against the edge of the door), but there was a bus about ten feet behind me. If it were closer when I swerved, things could have been much worse.

But perhaps this situation is all for the best as it has served as somewhat of a wake up call. Since then I've done a lot of research both on how to avoid being doored and on bike safety in general, with a lot of help from some bike-savvy friends. I now know that you should always keep yourself at least three feet away from all car doors to avoid being hit (four is better, five is ideal). I've also found a nice essay on the subject (including some examples of people who have died or been seriously injured by being doored) as well as advice from the City of Chicago. These are good reads, but nothing compares to Bicycle Safe: How to Not Get Hit by Cars. Seriously, it's a must read for any urban biker.

Anyway, I'm glad that I'm biking a bit better informed. But I'm definitely going to keep my alertness level at its highest and stick to neighborhood roads. My sister just told me about how she was a passenger in a car when the driver parked and doored a bicyclist, knocking out the guy's full set of teeth. To be honest, I don't take the best care of my teeth, but I sure would hate to lose them all at once.

Before I got my job at Google, I was reasonably fit. I also didn't have a car, and traveled everywhere via biking and public transportation. About three years later I'm quite overweight and haven't even owned a bike for some time. There's probably a correlation there.

Besides weight gain there's also just the feel of biking that I've missed. Well, since now's the best season for it, I decided to go out and get one. I went to a place called Working Bikes in Chicago; they recycle old bikes to create new working ones. I had no idea how furious the selling of bikes is as soon as the location opens. Well, I got one, but the decision was somewhat rushed. Its cheap, it works, but its pretty small and my butt sure does hurt sitting on it.

I figured I'd just bike it home. That was a huge mistake, as it actually took me several hours as working bikes is about thirteen miles from my apartment, and I'm totally out of shape. (In my biking prime that would have taken me no more than an hour and a half.) To top it off, I had no phone on me, I forgot that you can take bikes on public transportation here, and I was only wearing a t-shirt and it started raining (at least closer to the lake on the bike path).

But in a way I've been thrown fully into the world of biking again and I've forgotten that while the experience isn't fully unusual, the full experience of biking takes a bit to get readjusted to again.

Interestingly enough, I've begun learning lisp again, partly due to some frustrations I've had with Emacs and the realization that I just don't know how to debug and extend it well enough. I was never super great at lisp, but I wasn't bad either. Even for the parts I knew well though, I'm finding that you never totally forget how to bike or code lisp, but there's always a bit of relearning to do.

It's nice to return to these things again.

I've been writing a lot on the go lately. Thus, I have a whole backlog of posts to put up here, including some stuff from Flourish. I'm going to be posting them a bit sporadically as I clean them up, so just be aware the dates I'm posting them on aren't necessarily when I wrote them, in case that becomes confusing.

In the future I'll try to be more timely about posting just after writing.

A bunch of people have sent me links to an article about a programmer who proposed to his girlfriend through a video game, and have noted the similarity to my own proposal using PyStage.

It's not quite the same thing. The system I wrote was an animation system I wrote from scratch, and not a game. This other programmer hacked a pre-existing game. Both are interesting feats in their own ways. (Interestingly enough, the original plan was for me to propose with a full game, but then I realized that the cutscene was complex enough.)

Still, there are certainly similarities in the nerdiness of the proposals, but they're not really surprising. Good programmers take pride in the nerdiness and cleverness of programming, and what better way to propose than to make full use of your craft?

A while ago I gave a summary of the huge number of projects I have going on. I've been struggling to figure out what my primary focus should be.

Well, over the last several days I've been going on a lot of walks. Walking is one of my favorite activities, and this weather is the most perfect time of the year for me to take a stroll. I find that I do my best thinking on walks, and over the last few days I've been walking until I accumulate enough thoughts, then I sit down, pull out my laptop and type them all up.

Well, one of the things on my list of projects in progress was my old comic Lingo, which never really got that far in the first place, but which I've always felt very attached to anyway. But I really couldn't continue developing the comic. First of all, I want to take the comic in a different direction than I was originally planning. Second, I really regretted attaching myself and my friend Jay to the two main characters; it felt both egotistical and limiting. I recently had a nice talk about this with one of my friends, and she gave me her assessment that it's alright for the characters to be based off of real life people but to develop in their own directions.

Well with that in mind I went on another walk today; this time the focus of my thoughts was how to bring Lingo back to life. I sat down on a bench and typed up an outline of the story, and I think what I wrote should keep me going for at least another thirty comics. Afterwards I sketched out some new character designs for some of the forthcoming characters and drew out some layout drafts.

I'm glad to say that not only do I now know where I want to bring the comic, I wrote the script in a way that allows me to continue where I left off (even though I didn't get too far) without having to start from scratch. This is a huge relief, and the decision of what to do here was one of the major roadblocks I was facing.

So, I've decided that for off-work hours projects, Lingo will take number one priority. I'm going to try to turn this into a weekly comic.

By next Friday there will be a new comic up. I hope you look forward to it as much as I do.

This will be my final post regarding the Eee PC for some time to come, I promise. I got Ubuntu installed on the Eee, and I thought I'd give my impressions about that.

First of all, the results from a number of Google queries on how to do the installation pointed me to some interesting and well written articles, but I was having a lot of trouble until I actually visited the Ubuntu wiki. The steps you want to take are definitely these:

• Make a bootable Ubuntu Live/Install USB key. This is worth doing even if you aren't using the Eee, especially if you follow the instructions on how to create a persistent USB installation. However, its critical for the Eee, since the Eee lacks any sort of optical drive.
• Then follow the instructions for actually installing Ubuntu on the Eee . I found the install to be pretty normal, but its definitely worth following the instructions on this page to optimize the life of your flash disk, for installing the wireless drivers, etc.

But yeah, it was all very, very easy once I found the right resources. And now I've got a real operating system on here! It's way, way better than running the default Xandros install.

The only problem I'm having is how apparent it is that many applications just aren't developed to run at a resolution less than 800x600, and since the model of the Eee that I have has a maximum resolution of 800x480, I sometimes have to to hold down alt to drag windows around.

Here's a list of applications I've tested which work really nicely on the small resolution:

• Firefox
• Blender
• zsnes
• Emacs
• GNOME Terminal
• GIMP (had to modify the docks a bit, but once I did so all fit very nicely)
• Pidgin
• OpenOffice
• Aisleriot Solitaire
• Mines (minesweeper clone)
• Chess
• Ekiga

Applications that were unusable:

• Gnome Blackjack: Required an unnecessarily large window
• Wesnoth: While I could start this up in windowed mode (fullscreen would not work) it was totally unusable as I could not access the buttons from the main menu. Constantly moving around the window to play this game is just far too obnoxious of an idea to even seriously contemplate.

Other than that, a number of applications had preferences menus or graphical wizards which required a lot of manual positioning to navigate, but nothing too frustrating, and since these are things that one needs to access very rarely, I don't really find myself bothered at all. Now, the next generation of the Eee is both more expensive and more powerful: for 400 bucks (50 dollars more than what I paid) you can get a savvy 1024×600 resolution screen. My suspicion is that this will be good enough for most people, though I think the current system I have is still Good Enough For Me (tm).

Conclusions: Asus has definitely done the right thing here. Sure, they could have shipped with a better distribution, but the fact that this machine actually ships with and was designed for Linux means that I knew I could buy it already knowing all the hardware would work with my operating system and distribution of choice. Since the resolution is good enough and not too unusual, and since it ships with a keyboard and a touchpad, this means that finally Linux users have access to an ultraportable device that isn't trying to reinvent the browser, email clients and feed readers because of limitations or peculiarity of the screen or input. For the most part, you know you can run the distribution and applications that you already know and love. And not reinventing the wheel is a great thing. And despite how great these devices have done for the proliferation of free and open source software, this just can't be said for the Nokia handhelds, the Zaurus, or even a project I'm still a huge fan of, the OpenMoko phone.