Archive for July, 2006

Climbing Mt Yale

Sunday, July 23rd, 2006

On Saturday me and JT climbed Mount Yale in the Sawatch range.  It was about 7 miles round trip and about 4300 vertical feet.  That means that it was pretty darn steep from the start of the trail more or less all the way to the summit.

It would have been a pretty easy hike if I weren’t in such miserable shape.  As it was, I was slow but had a blast.  This was my 5 14er.  So I have a place to find them, so far I have climbed:

Longs Peak, July 2002
Torrys, by the Kelso Ridge, 2005
Greys, same day as Torrys, 2005
Bierstedt, did the Sawtooth but didn’t summit Evans, 2005
Yale, 2006

First post from my Mac

Friday, July 14th, 2006

Okay.  I realize that I have only been using my mac for about an hour, but I would like to say that so far everything has just worked.

After installing OSX, wireless just worked.  After plugging in my new firewire drive, it showed up and was ready to use.  (Granted, I took the time to reformat it as native osx with journaling.)  Using the finder I was able to find my PC on the network and start copying my music to my new drive.

So far I am pretty happy.  It is gorgeous too.  The screen is bright and crisp, and the text anti-aliasing looks great.

We will see how I feel about a week from now.

gnubbs

(ps. I got off work early today and have been drunk the entire time I have been playing with this thing.  That could be influencing my opinion.)

Introducing Ruby

Friday, July 14th, 2006

At work I am a member of a Software Engineering Reading Group. It works pretty much like any other reading group, except the books of choice have titles like “More Effective C++” or “Pattern Oriented Software Architecture”. (Both those books suck by the way.)

We just finished up the C++ book mentioned, and in a two weeks we will be picking a new book. Since the vote on the new book will not take too much time, I have been asked to spend 30-45 minutes talking about Ruby and why I love it so.

To be honest, I am really in no way qualified to talk much about Ruby. I have been doing development in Rails for a couple of months now, but I still feel that I am an utter newbie to the whole thing. So, I am looking for some advice on the things that you would choose to focus on when selling ruby to C++ programmers.

To me, the key features that make me love ruby are:

1. Expressiveness. I don’t think I have seen another programming langauge that was so amazingly easy to read. I don’t think I have ever written programs in another language that so stated so clearly what they did. To steal an example from David Heinemeier Hansson’s “Pursuit of Beauty” presentation:


transaction(david, mary) do
david.withdraw(100)
mary.deposit(100)
end

2. Everything is an Object. This is what always killed me about PHP, Perl, and even C++. Objects always seem to just be hacked onto the top. There was always a disconnect between built in types and user defined types. They should really all work the same. Ruby nails this. Everything is an object:

“this is a string”.upcase -> “THIS IS A STRING”
5.next -> 6

3. Blocks. I am starting to really like blocks. They have not quite gotten to be second nature to me, but they are starting to get there. (I never got into Perl enough to really grok closures. Don’t hold it against me. And yes — in ruby you can use blocks as closures.)

[ "H", "A", "L" ].each { |letter| print letter } -> HAL
My main goal is a brief intro to what the language looks like, and in doing so highlight the key aspects that make it such a fun (aka. productive) language to program in. What am I missing?

Also, what are it’s major downfalls? With the how common multi-cored processors are becoming we are making a lot of moves in my company towards writing software that is more suited to those platforms. So, I feel I should definately point out Ruby Threads.
What do you love, and what do you hate about Ruby?

Time to Jump Ship

Wednesday, July 12th, 2006

I hate my desktop computer at home. I truely, truely hate it. It just doesn’t work. No matter what I want to do, I end up having to screw with it endlessly to get it working correctly. I blame this pretty much entirely on the fact that Windows XP sucks. It might be better than the rest of the windows family, but it still sucks. As I see more and more about Vista, I realize that this is only going to get worse.

So it is time to buy into the hype and switch. I could use ubuntu on my existing system, but it really needs a new monitor, keyboard, and mouse. That puts me out close to $400. On top of that, I screw with ubuntu enough on my laptop, I don’t want to have to do it with my desktop as well.

That only leaves one choice. So, I am buying a used Apple off a coworker. It is a 2-3 year old iMac G4 (the one that looks like a big pile of Mac poop with a monitor popping up out of the top) — 800 Mhz G4, 15″ flat screen, 256mb of ram (will be upgraded to 1gb as soon as I get it), and OSX Tiger. All for $400.

We will see how this goes. My requirements are pretty simple:

1. Listen to music in iTunes (can do this well enough on my PC)

2. Organize my photos with iPhoto (there is no photo management software for PCs that doesn’t suck! I have tried Picassa, Adobe Bridge, and the nikon stuff. They all suck when dealing with my Nikon D50 raw images)

3. Surf the web

That is honestly all that I do with the desktop at home. My laptop is where I spend most of my time, and do all of my development.

Hopefully all of those things will just work. That is what Apple claims, we will see if they can deliver.

gnubbs