March, 2005

More about the damned Treo

Submitted by reeses on Thu, 2005-03-31 11:49. |

Yeah, I know.

I unboxed the Treo 650 when I got home tonight, synced the Treo 600 one last time, pulled out the SIM card and my SD, popped them in the 650, cabled it up to the Mac, synced the 650 (which took about ten minutes thanks to thousands of calendar events), and blam. Ready to go.

What's good:

  • The screen is the secks. Seriously. It's so much better than the 600 that it's just ludicrous that Palm actually released the pile of crap that is the 600. They should have called it an internal beta or a prototype.
  • The keyboard is drastically improved. I always envied the crackberry monkeys because they could actually type with their fingertips. Now I can too.
  • Bluetooth. Bluetooth is why I bought the Mac. Well, Salling Clicker is why I impulse-bought the Mac back when I had a T68i. ("Hmm, I need a laptop and this little app looks really cool!") Now I can sync via Bluetooth and run Clicker.
  • Removable battery. And it came half-charged, so none of that silly "leave it on the charger for at least three hours before playing with your new toy" nonsense.

What's not good:

Don't see this movie

Submitted by reeses on Tue, 2005-03-29 21:39. |

I was tempted to write something about how I've been a slacker with updates lately, but it occurred to me that that type of entry is so common there should be a flyweight reference. Like DTDs or Schemata, we'd have a common url like http://www.w3.org/TR/2005/REC-blog-20050330/ that people could refer to in their own blogs. Of course, the page rank for this URL would instantly make it the most popular page on the web.

Now, I've turned this into a blog entry about blogging, which could be found at http://www.w3.org/TR/2005/REC-metablog-20050330/, so let's wrap that up tout de suite.

What I really wanted to talk about, to avoid further http://www.w3.org/TR/2005/REC-blog-20050330/, was Napoleon Dynamite.

factorial.cpp

Submitted by reeses on Sat, 2005-03-26 22:02. |

This is a quick hack that was the result of a discussion on interview questions. A friend's coworker asked an interview candidate,"Can you write a recursive factorial function?" My friend and I joked about hazing an interviewer or an interviewee in the situation -- what language, what's the maximum value to expect, should we eliminate tail calls, etc. So, taking something that would be easy in lisp ((defun fact (x) (cond ((= x 0) 1) (t (* x (fact (1- x)))))), untested ), I wrote a quick and lazy char*-based solution in C. All I did was implement simplistic decrement, addition, and multiplication mechanisms for strings of numbers. It was interesting to see four lines of lisp turn into 140 lines of sloppy C.

You want to see fast

Submitted by reeses on Sat, 2005-03-12 21:22. | |

Kat's been working on one of her last papers for law school. A 35-page beastie about whether some random group should be considered a terrorist organisation. She's doing a lot of research, digging a lot of stuff up, and trying to wedge it all into an outline and paper that make sense.

Her struggle afforded my ever-prepared self an excellent opportunity:

"I think I just realised why I'm going so slowly on this paper. I'm not using the other monitor."

"Oh, well, you should take it. I'll go to the Apple Store and buy the 23 inch LCD for my laptop," I mumbled over my shoulder as I grabbed the car keys and ran out the door.

Lock up your sheep

Submitted by reeses on Tue, 2005-03-01 21:41. | |

I'll be flying into SF this Thursday evening (3 March) and I'll be around until stupid early Monday (7 March) morning.

If you want to grab food and/or cocktails, let me know. I'll either be on the top of Nob Hill or down by Union Square, but don't expect me to walk and don't expect me to leave the city.

My only schedule demands right now are some conf calls and a trip to Hermes some time Friday and a gay wedding Saturday afternoon/early evening.