The Caffeine Dilemma

This is not news to anyone, but the American food industry has a generally brazen disregard for people’s health, from over processed grains to trans-fats to things we don’t even know about yet. Unfortunately these ingredients and techniques are so commercially advantageous that it can be near-impossible to avoid them when having a meal outside of your house. An ingredient that falls into this category but doesn’t get as much chicken-little-press is caffeine.

Now caffeine is probably not as unhealthful as other things, but I’ve been trying to eliminate it from my diet except on an as-needed basis. Some people I know take pride in their level of caffeine consumption, but no doctor has ever told me I wasn’t getting enough of it, so I figure less is better.

Most non-fancy restaurants will have most of the following: coffee, decaf, hot/iced tea, tap water, bottled water, coke, Diet Coke, sprite, root beer, and a few other sodas, and often a juice or two. I eliminated sugary sodas a while back from my standard diet, so coke, sprite, root beer, and the other sodas are out, as are any available juices since they are mostly sugar too. Coffee is usually bad, decaf is usually horrible, and tap water is rarely any good, so they are out too. I’m left with hot/iced tea, bottled water, and Diet Coke. Bottled water usually costs a lot and you don’t get refills, and even before I was exercising regularly I consumed more beverage than your average person. I really can’t justify spending $5+ per meal for water. I’m not a big fan of hot tea without cream and sugar, and the quality of (caffeinated) iced tea is highly variable, so I typically order Diet Coke. Which, of course, has caffeine. It also has artificial sweeteners which I’d like to cut out at some point, but one thing at a time. There is of course, beer, wine, and liquor, but I drink far less than I go out (once or twice a month versus several times per week, respectively) and don’t see increasing intake as a healthy alternative.

So the logical plan would seem to be to order tap water, and if its not good, order a Diet Coke as a fall back. The problem is that if you’ve eliminated caffeine from your regular diet your tolerance for it drops quickly. So I’d be taking in a pretty powerful stimulant at 7 or 8pm and I’d likely be hopped up well into the night.

One thing I have stopped doing is buying soda for the house. I’ve been sticking to things like Gatorade, Fruit2O, Vitamin Water or Propel, and I feel better, despite most of them having sugar (though it’s about half of non-diet soda). I drink a half gallon of spring water a day, but I find that those sports drinks help with the sweet tooth.

If you think I’m working towards some conclusion here, I’m sorry to disappoint, as I’m still not sure what to do about the restaurant thing. If anyone has any ideas, I’d love to hear them.

Update: Credit to Dana for suggesting club soda w/lemon as a caffeine-free, free-refill alternative when the restaurant also has a bar. It might take a bit of getting used to, but I’ll give it a shot.

Vista: Day 1

So, after finally calling it quits in my battle against my MacBook Pro, I retreated to Microsoft. You basically can’t buy a Dell without Vista now, so I figured I’d give it a shot. There’s been a fair amount of hype by Microsoft in favor of it, and a tremendous amount of anti-hype against it by basically everyone else. After my first day, I’ll say that neither side has much to stand on.

The system is what I’d consider an average developer box these days. Grand total with tax was less than $1150.

  • Dell E521
  • Athlon Dual-core 5000+
  • 2GB RAM
  • 250GB hard drive (no raid)
  • ATI X1300 video card
  • 20″ Dell 4:3 LCD
  • Windows Vista Home Premium

I hooked it up to my pre-existing 24″ LCD as primary monitor. I had bought a Radeon 9250 so that I could run the second monitor on DVI, but ATI doesn’t have Vista drivers for that, so I hooked it up to the VGA port until I return that card for a newer one.

Here’s what I installed:

  • JDK6 – No problems
  • Eclipse 3.3M4 – No problems
  • Jetty 5 and 6 – No problems
  • JettyLauncher (eclipse plugin) – Only works with JDK 5, not sure if this is a Vista thing, so…
  • Subclipse (eclipse/subversion plugin) – No problems
  • JDK5 – No problems
  • MySQL 4 – No problems
  • Firefox 2 – No problems
  • Yahoo IM – Crashed once, but it does that on XP too often too.
  • AIM 6 – Crashed once after I first started it, ran fine through several conversations later on.
  • Windows Mail (pre-installed, I configured for POP and SMTP over SSL) – no problems.

So the big complaint by the hordes has been performance. For a mid-range machine, with full Aero enabled on two monitors at 1920×1200 and 1600×1200, I see no lag at all. Aero is actually decent. It’s only major flourish is the new “flip-3d” where the windows stack up like something you would see on a Mac, but its really kind of useless, and I prefer alt-tab. The live previews when you over over the task bar are actually kind of nice, though not very useful. The transparency is fancy, but not overdone, the fade/shrink when you minimize is quick and nicely done. I haven’t disabled any of it yet after 7 hours of use, which is about 6.9 hours longer than the ridiculous XP theme lasted.

Programs launch and run faster, though it does seem like installers go slower and hang for a while. It also comes with a ton of nice fonts, I’m curious if we’ll start seeing those show up in CSS files. I set most of my stuff up for familiar 8pt Lucida Console, I’ll have to go through and see if they’ve added any other nice monospace fonts.

Microsoft seems to have adopted the unix idea of security when it comes to “sudo”. Whenever you do anything that affects the OS, it prompts you to allow it to proceed. If you want to do something like edit your hosts file, you’ll need to run your editor as an administrator, which is as easy as a right click. It’s all a bit annoying, but probably just because I was tweaking it alot. We’ll see how it plays out after a period of normal usage. The worst part is that when the box comes up, the whole screen flickers and takes on a lightbox type effect. Seems to be overkill and poorly implemented.

Other than that, I hate to break it to the Microsoft PR squad and the throngs of haters, but it’s really just good old Windows. The paths are a bit different, things are called slightly different names, but from my perspective, it’s all trivial stuff. Unless I come across something tragic or wonderful, I see no reason for people to upgrade, or to resist upgrading.

Roundup: January 2007

I don’t have the time or inclination to do a standard commentary-style blog, linking to the latest news item or wacky video, but on the other hand, there’s things worth sharing. I’m going to try wrapping these up in a monthly digest.

If you haven’t checked out The Chloe Chronicles, you should. Nicole has been writing a very personal, detailed, no-holds-barred account of the experience of having a daughter a bit on the early side. I can’t imagine how cool it will be for Chloe to read this when she’s older. I don’t think anyone in my family ever kept a diary, but it would be amazing to read something like this from them.

More important than the iPhone or the 108-inch HDTV, but lacking in fanfare, solid state disks (SSDs) are coming to the consumer market. These should be standard equipment in laptops in a few years, and will offer hardware designers a whole new set of opportunities.

My favorite fantasy series since Lord of the Rings, A Song of Ice and Fire by George R. R. Martin, is on its way to being an HBO show. It’s a complex, serial storyline with a ton of characters and no shortage of sex and violence, so it should fit in perfectly with HBO’s other great shows.

Went to see Children of Men. The first half was slow but seemed to be building up to something good. The second half looked like this:

Boston Fire Department at Loews Boston Common 19

I got a membership at BSC. The one in Wellesley is really nice, they even have individual TVs on each cardio machine. My current plan is to go in the mornings. Those who know me will probably affirm that the previous statement is probably one of the funniest I’ve ever made.

Rational Exuberance

I’m a fairweather football fan, and the last 5+ years have been good ones for New England area fans, fairweather or die-hard. I watched the two games yesterday, Seahawks @ Bears and Patriots @ Chargers, and was immediately reminded why I just can’t get into the sport in any serious manner.

For those that don’t know, last weekend was the second round of the NFL’s 4-round playoff season. One of the reasons I think football is so popular is that it’s so easy to follow. There’s no grueling 162-game marathon, very few weeknight games, and a season ticket is only 8 regular-season games. I watched 50% of the entire league’s playoff games for this round in the space of a few hours, something that would require taking a sabbatical for a sport like basketball. Add a TiVo to the mix to skip past all the downtime and you’ve got some good action. Seeing guys get tossed like ragdolls and exciting plays like interceptions, as well as freaks of nature like Shaun Alexander, who makes the rest of the field look like it’s in slow-motion, is good entertainment. Yes, entertainment.

So first up was the Seattle Seahawks playing the favored Chicago Bears. They battle it out for a while, the Bears benefiting from Seattle’s quarterback Hasselbeck making a few big mistakes, and the game is tied going into overtime. I really didn’t care who won, I don’t follow either team and it’s two of my favorite cities, but it was an immediate letdown. Why? Because overtime in football is probably the thirdmost anti-climactic thing in professional sports. (The second is also in football, where they run down the clock, and the first is pretty much anything that happens in soccer).

Football is a game modeled on the same principles as warfare of the 18th century. Everyone lines up, everyone has a job, and you go at it. The two sides are rarely evenly matched, but there’s the sense that if everyone does their job and the plan is sound, you have a chance. Overtime takes that and flips it on its head, because it’s sudden death. Whoever scores first, wins. The really disappointing part is that it usually ends on a field goal, and the team that gets the ball first is decided by a coin toss. The Seahawks won the toss, but didn’t score. The Bears moved the ball a bit, and kicked the winning field goal.

Football is no stranger to rule changes, so I’d like to see two more. First, both teams are guaranteed at least one possession. If there’s a turnover, at least the other team had a chance. Second, and much more importantly, no field goals. Sorry kickers, I’d rather see the whole team have to win, not just you.

After that game, the Patriots played the favored Chargers. Both teams played a sloppy, but enjoyable game. The Patriots came back in the 4th quarter to tie it, and took the lead on a field goal. The Chargers got the ball, made a field goal attempt, and missed it, game over. The big story of the game, however, is that the Patriots overcelebrated their victory, “showing up” the Chargers on their own turf. So now the darlings of the NFL media, the reigning dynasty in the league, were made to look like a bunch of hooligans with “no respect for the game”.

There seemed to be two major offenses. The first was that they were jumping on the Chargers logo in midfield. The solution to this is a simple one. If you or your fans are too sensitive about your corporate logo being tarnished, don’t paint it on the field. The second was that the Patriots appropriated the taunting dance of the Charger’s defensive superstar Shawne Merriman. Never mind that Merriman did it after every sack, or that Merriman had shown his personal respect for the game by failing a drug test. The league MVP Tomlinson was so incensed he charged at the group and had to be restrained, and kept his anger boiling through the post-game press conference.

To borrow Rob Corddry’s attempted catch-phrase, “coooome ooon!” Sports are first and foremost entertainment. Fans pay hundreds of dollars to watch guys play a game most of us gave up in adolescence, after which they retire to their mansions and spend the rest of the life getting updates on the charitable tax deductions their assistants run for them. I’d argue they deserve the money they get, not because they are psuedo-heroes or guardians of contrived traditions, but as entertainers. I want to see the winners be happy and the losers be sad. I want to see grown men doing silly dances because they carried a warped ball over a line of paint. The next day, I want to read about the ridiculous comments from a guy who had to cheat to get a 700 on his SAT.

If the Yankees beat the Red Sox and a pinstriped marching band ran out onto the Fenway infield and Derek Jeter stuck the game winning ball in his pants while A-Rod did the funky chicken on homeplate, I’d be laughing out loud. When they silently tap gloves and retreat to the locker room, I feel deprived not only of my team’s victory, but the sense that it actually meant something to the team who took it from them.

So let’s forget about respecting the hallowed traditions of a child’s game played by rich men of often questionable character, managed by billionaires who hold lifetime fans hostage and demand taxes to pay for expensive stadiums with horrible parking. I just want to see people show up, play as hard as possible, and put on a good show. If you win or lose, show me that you’re playing this game for something more than the huge paychecks, and that you’re as excited or disappointed as the crazy fat guys that painted themselves blue to try and give you an edge in the contest.

Professional Advice: Speakerphones

Speakerphones seem to be increasing in popularity in the workplace, and in case it’s not obvious, this is a bad thing. For the sake of sanity, let’s review the narrow set of conditions under which speakerphones are allowed. Note that both conditions must be met.

  • You are in a fully-enclosed office or conference room.
  • Two or more people need to speak on your end.

There are some rogue conditions floating around that are invalid. These include.

  • I’m typing. – Stop and listen, or hang up.
  • I’m very busy and/or important. – No, you’re not.

Simple huh? There is a small set of exceptions. (This list is exhaustive)

  • You are juggling and on the verge of breaking a personal/world record.
  • You are performing surgery.
  • Your handset is broken and you are ordering a new one.
  • Your ears are under some sort of medical duress and you are calling the doctor.

Baseball HOF 2007

This years Baseball Hall of Fame election results have been announced. Here’s what would have been my votes. Those who were elected are in bold.

Harold Baines – No
Albert Belle – Almost
Dante Bichette – No
Bert Blyleven – Almost
Bobby Bonilla – No
Scott Brosius – No
Jay Buhner – No
Ken Caminiti – No
Jose Canseco – Almost
Dave Concepcion – No
Eric Davis – No
Andre Dawson – No
Tony Fernandez – No
Steve Garvey – Almost
Rich Gossage – Almost
Tony Gwynn – Yes
Orel Hershiser – No
Tommy John – No
Wally Joyner – No
Don Mattingly – No
Mark McGwire – Yes
Jack Morris – No
Dale Murphy – No
Paul O’Neill – No
Dave Parker – No
Jim Rice – Yes
Cal Ripken Jr.- Yes
Bret Saberhagen – No
Lee Smith – Almost
Alan Trammell – No
Devon White – No
Bobby Witt – No

Notes:

HOF votes should not be secret. Why? Because we need to see who didn’t vote for players like Gwynn and Ripken and fire them. The supposed logic here is that since nobody was ever elected unanimously, nobody ever should be, but that’s bunk. The point of the HOF is so we can take our kids there someday and show them the revolutionary players like Ripken (which outweighs the fairly inconsequential Streak), and players like Gwynn who make something so hard look so easy. If you want to impose your own twisted house rules, go vote somewhere else.

I’m not really surprised that McGwire didn’t get in, but I am surprised how few votes he got (23.5%). The topic of steroids in baseball is annoying, and the consequences are inconsistent. Steroids have been around for over 50 years, and clearly players have used them in all sports. To say that McGwire is the one of the first to abuse them is simply false, especially when people hold up the hitters of the 60s and 70s as examples of people who didn’t. We have no idea if Hank Aaron or Jim Rice or Tom Seaver used drugs or supplements, and even to suggest the possibility as I’m doing here is blasphemy. Despite longstanding media hype to the contrary, there isn’t even any credible evidence that steroids have adverse effects on grown men. McGwire is 6’5″, Canseco is 6’4″, both are well over 200lbs and took advantage of modern nutrition and training. Mantle was 5’11”, Aaron is 6′, and both were relatively lean. They also grew up in an era where people didn’t even know what effects basic vitamins really had. To say that modern sluggers were “obviously” using steroids and other hormone supplements is silly, and even if they were, can someone prove that they shouldn’t? We’ve proven the dangers of weight training as well as alcohol and red meat and sodium and pretty much everything else athletes put into their bodies, why aren’t they banned as well?

Jim Rice isn’t a legend like Ruth or Cobb, but he was a dominant force for a long time. There are many opinions why he can’t seem to get enough votes, from his mediocre fielding to his frosty relationship with the press and fans, but he should be in.

Albert Belle got 3.5% of the votes, not even enough to stay on the ballot. He was a troubled personality whose career ended on a very sour note, but the voters apparently forgot that he was a terrifying hitter who competed for MVP status, had 9 consecutive seasons of 100 RBIs, and a career .295 average. Perhaps not HOF numbers, but clearly a brighter talent than some who finished ahead of him.

Macintosh Gripes: Poor Usability

I’ve had many computers over the years, and many of those have been Apple Macintoshes. I’ve had an SE, PowerMac 7200/75, iBook, Mini, and currently a MacBook Pro. Up through about 1997 I considered myself to primarily be a Mac user, but I switched because I was using and developing for the web more and more, and Mac web browsers were slow and poor, to put it kindly. I was also developing on Microsoft Access quite a bit, and there was no Mac version (and there still isn’t). When I started at StyleFeeder I had a choice and opted for Mac because that’s what the other developers were using, and I have to admit I regret that decision.

Macintosh OSes, especially OS X, is often praised for it’s quality and usability. Back in the old days, I’d agree. System 7 was hands-down better than Windows 3.1 in pretty much every way I can think of. These days, I’d say the tables have turned and can’t think of any way that OS X is better than Windows XP. They both crash infrequently, but I’d give a slight advantage to XP as it only crashes for me once or twice per year, while the Mac has done so at least twice since August. The Mac came with some decent software for dealing with movies and making music, but I don’t do much of that stuff and if I did, I’m sure I could find similar Windows software.

My main cause for regret is the overall usability of the OS. There are three main issues here. The lack of keyboard access to commands, the antiquated menu bar and the MDI.

As a full-time developer, I’m in the power user caste. I am constantly trying to find the shortest and easiest way to get things done. Nobody with half-a-clue about usability would argue that the mouse is an efficient command tool. It’s obviously the ideal way to select things and navigate spatially, but once you’ve gotten where you need to go, you are ready to start issuing commands. On Windows, every command is accessible via the keyboard. Common operations have simple key-combinations, more obscure ones will have more complex combinations. Control-P prints, Control-S saves, and so on. For tasks that are more specialized or used rarely you will likely have to use things like Alt-F-W-F (makes a new folder in explorer) or Shift-Control-F (formats code in Eclipse). These don’t need to be easy, but they are there and every user will find themselves learning a few of them depending on what they do often.

On a mac, no such luck. Some things like printing and saving are common, but after that it’s seemingly random and left to the application developer to implement commands, and most don’t. So I have to stop what I’m doing and reach for the mouse all the time. In usability terms, this is a fairly significant hurdle and has a high cost which I find unacceptable. Apple reluctantly introduced “universal keyboard access”, but it’s really bad and clearly a begrudged afterthought that makes you use the arrow keys to navigate menus.

The second gripe is the way OS X sticks the menu/command bar at the top of the screen. The logic here is that it’s easier to target something thats at the top of the screen because the mouse won’t go past it, and also that it’s always in the same place. That makes sense in theory, but fails in practice. As mentioned above, the mouse is a last resort for issuing commands, so by the time you’ve reached for it you’ve already incurred significant expense. Spending the extra 50ms target it is a minor addition to this.

Where the fixed menu bar really fails is when you use more than one monitor, because it sticks it to the top of the primary monitor. If you’re working in the second monitor you now need to grab the mouse, and drag it all the way to the second screen, then drag it back.

Also, when working in more than one program, which most people do, you can’t select commands from an inactive program. You need to find a safe place to click to activate it, which is expensive and varies widely, then you can access the menu bar. In windows you can click on an inactive menu bar and it will open with that same click.

Thirdly, almost all Mac programs use what is called an MDI, or Multiple Document Interface. This means that all the windows for a program are linked together as opposed to a Single Document Interface (SDI). Microsoft realized that MDI was a poor design in many cases, and fixed this in XP. MDI makes sense for some things, such as dialog boxes and the many windows that Photoshop uses to show things like layers and pallettes. This does not make sense for things email and word processing. Just because I have two documents open in the same word processor doesn’t mean there is any relation between the two. I should be able to alt-tab to a specific document and keep the other one minimized. A minor annoyance related to this is that you can have programs running with no windows at all, which ties up resources and is just plain confusing.

Perhaps the worst part of these problems is that they could be built into the OS and be optional behaviors, but they aren’t. Apple’s stance has always been that they know best, and that options are confusing. Unfortunately they compound this defect with the fact that they are extremely slow to change things even when they are clearly wrong. For proof of this you need only to see that they still put one-button trackpads on their frighteningly hot, overpriced laptops.

Cracked Foundation: Trac

We’ve been using Trac on a project lately, and it’s a good example of an otherwise decent product being rendered almost completely useless by a simple problem. To be clear, we’re using Trac for defect/issue tracking, so if you aren’t using that part of it, this wouldn’t affect you. The rest of the system seems OK, though I’m not sure why integrating SVN commits into tickets requires some hack via Perl script (that won’t work for us). However, that’s just a lack of convenience, the real problem is the way it handles the chain of custody for tickets. Here is Trac’s state diagram for tickets:

Track Ticket State Chart

I’ve worked with many different issue tracking systems, and if you have too, you’ve probably already noticed what’s missing. I call it the “full circle” concept for lack of a better term. The crux of the idea is that the person who opened the bug should be the only one to close it in most cases. Trac does not have this. The reporter can reopen the ticket, but a closed ticket basically falls off everyone’s radar, so no validation or verification would take place. Here is the state chart with the step I’m referring to:

Minimal Defect Tracking State Chart

Even on a small team, without this step we’re running into people with clogged-up queues because it’s pretty common for developers (ticket resolvers) to also create tickets from time to time and assign to another developer. We’ve take the safe route of reassigning to the reporter rather than closing, so things should be validated before closure, but this makes the ticket queues much larger and more difficult to manage, and sometimes tickets don’t get closed until after the fix has been published.

Voting Obsecurity

December 26, 2006

The Honorable George W. Bush
President of the United States
The White House
1600 Pennsylvania Avenue NW
Washington, DC 20500

Dear Mr. President,

I hope the holidays find you well, and wish you happy and productive new year.

I am not an expert on the topic of voting, nor am I a professional security expert, but I do try and follow the news with regards to the intersection of the two. I watched the HBO documentary “Hacking Democracy” this weekend while wrapping presents, and was flat-out disgusted. It was not especially well-made, made no attempt at being objective, nor was most of its information news to me, but I was moved when I watched a mock election be rigged using actual voting systems and saw a real, respected election official be speechless and dumbfounded that his job was completely undermined.

There is no simple solution to secure voting, nor is it remotely probable that any election will ever be 100.0% honest, but there are some monumentally obvious flaws in the way we currently count votes. The largest is the issue of the lack of openness of the software, systems, and processes that are involved.

I am a software developer and most non-programmers I’ve talked to have a difficult time understanding the idea that public access to the “secret codes” of software, AKA the source code, is more secure than private or closed source code. The general opinion is that if you can see the inner workings of something, it’s easier to break it, which is valid and true. The next step in this thought process, however, is more critical and is one that most people don’t take. That is that if you cannot see the inner workings of something that is broken, it’s more difficult to fix it.

The idea of “security by obscurity”, sometimes referred to as “obsecurity”, is valid and necessary when it comes to information such as private financial data, personal information like medical histories, and intelligence gathered by our military and other government agencies. However, regarding mechanisms and processes, such as software, obscurity lessens security. This is doubly true when those mechanisms are designed to collect and analyze public data, such as votes.

Here’s a dirty secret of the programming craft: 99.9999% of software is broken. By broken I mean there is some bug somewhere in it. In new or rarely used software these bugs can be serious and misleading. In most mature software, it’s nothing serious; something doesn’t display right, some obscure error condition is handled poorly, etc. This applies to video games, email programs, ATM software, Windows, Linux, etc. as well as voting software.

So how do you weed out these bugs? You test, over and over and over again. When you find a bug, you test again, even things that you didn’t fix (AKA regression testing). Eventually, you’ve fixed all or most of the bugs that were found, satisfied your unit tests and requirements, and you ship it. Then your customer does something you never planned on, maybe because they are being silly or stupid, or you aren’t the programming god you thought you were, or your QA staff is overworked, or it just wasn’t possible for you to test in the lab. This is why you get Windows updates every week, and why there are dozens of bug fixes for every Linux kernel, patches for every video game, it’s simply unavoidable. The more something is used, the more bugs are found, and the better it becomes.

Voting software isn’t used very much. Most machines are used one day every year or two. Excel has been used by millions of people every day for nearly 20 years, and there are still bugs in it. If I’m making an inventory of my baseball cards and have a problem with Excel I can report it to Microsoft and hopefully a ticket will be opened and hopefully they will fix it. The difference between a spreadsheet package and a voting system is that my grandfathers didn’t risk their lives overseas to make sure “=SUM(D3:D13)” was accurate, they did it so that I would grow up in a better world than they did, and just as importantly, have the power to make it better for my grandkids.

It is absolutely imperative that we apply the highest possible standards of scrutiny, security, and integrity to the systems that facilitate our most sacred public right. Voting software, hardware, and system should not only be open, they should be the zenith of openness. The public should be able to download complete specifications for every piece of hardware on every type of voting machine out there, from the device I vote on to the system that tabulates it to the printers that make the reports. We should have access to every line of code used in the entire process. I should be able to test it myself and find flaws or solicit advice from those I trust. The public should have as much access to the hardware as is feasible. Regular citizens, universities and vendors should be encouraged with bounties to find and report flaws they find. Defect reports on voting systems should be legal documents, also open to review by all. There should be digitally signed video publicly viewable via live broadcast or within hours of all access to every machine with the sole exception of the person casting a ballot. There is room for only ONE secret in this entire process, and that is who an individual voted for.

I would be exceptionally pleased if you would propose or support legislation to help protect our votes by virtue of an open and honest process. It would not only validate the sacrifices millions of Americans have already made, but it would set an example that other democracies and future generations will aspire to.

Sincerely,

Eric F. Savage


Also sent to my Senators Kennedy and Kerry, Representative Frank, Governor-Elect Patrick, State Senators Brown and Creem and Secretary of the Commonwealth Galvin. If you feel similarly I encourage you do write to your officials and feel free to borrow or copy from my letter.

For more, better information on this topic I recommend checking out Ben Adida’s Blog and Black Box Voting. A web search for ‘secure voting’ or similar topics will also turn up piles of other opinions and (often scary) facts.

Glossary: Kilby Shortcut

Every group of friends develops a very localized parlance, usually drawn from movies they’ve all enjoyed or memorable events. My group of college friends was lucky enough to include someone who had inherited a dominant curator gene, Keith Tyler. This is well-evidenced by his contributions to Wikipedia, but also by his entering into the historical record a fairly exhaustive list of rubbonics, complete with phonetics, that would be useful in deciphering our conversations of the day.

This way's faster!Sometimes, a term or phrase has the potential to break out of the group and escape to the community and beyond, and I’m going to nominate one to do just that, or at least get it into Google. This term was apparently born after the rubbonics were codified, and I can’t remember the date, but I do remember the circumstances.

We went to the Cheri Theater (now the site of the Summer Shack and King’s bowling), one chilly Boston night. On the way back, Kilby proclaimed “this way’s faster” and promptly crossed the street. We declined to follow and proceed on our way as Kilby marched down the other side of the street. At the next intersection, he crossed back to our side of the street, but was there before us. “How?,” you ask. The answer is simple, he walked faster. This was not the first time he had performed such a feat, but it was then that the phrase “Kilby shortcut” was coined.

Kil·by short·cut

noun (kÄ­l’bÄ“ shôrt’kÅ­t’)

A path between two points which is longer than other obvious choices, but the extended length is mitigated by travelling faster.

An ironic footnote is that Kilby doesn’t drive, and never has, yet somehow is the best navigator I’ve seen when it comes to exploring cities or unfamiliary territory. Except, of course, when he says “this way’s faster”…