jaXzin.com

Paperless

2012-02-05T16:08:00.000-05:00

I've been slowly going paperless over the past decade. The first step on my journey started in 2000 when I signed up to use a payment service, PayTrust, to receive my incoming bills, scan them, and put them online for me to pay. The next major step was probably when I got a digital camera to replace my traditional film cameras. It might not be considered a "paperless" use case, but it has lead to very little hardcopies over the years as monitors and HDTV with screensavers and AppleTVs have become so beautiful. Back to the paperless office, my next big step was eFileing my taxes but that didn't come until about 5 years later. Then suddenly about two years ago, I hit a real shift in my desire to go completely paperless when I got my iPad and installed Evernote.

digital notes...

If you aren't familiar with Evernote its an excellent app, available on all the major desktop and mobile OSes, that makes note-taking and organizing really simple. The killer feature is it keeps the notes in-sync across all instances, from my iPhone to my iPad to my multiple PCs.

So when I got my iPad and discovered Evernote around the same time, I realized how going paperless was finally a reality. The only problem is that I have a file cabinet full of paper! I tried to just keep up with the incoming paper in our lives using our all-in-one scanner, but sitting in my office just isn't my idea of a fun time, and so that project has stagnated and the paper continues to go into the file cabinet.

Then last week a friend on Facebook posted how he was going paperless and so I asked him his secret. He was nice enough to share that he was use a Doxie scanner. It was the first I had heard of it, but when I looked it up I knew it was exactly what I needed. After convincing my wife that it was perfectly valid use of my unspent Christmas gift money, I ordered a Doxie Go.

portable scanning to the cloud...

My Doxie Go came four days later, yesterday. Unboxing it, I knew it was what I have been waiting for. It is small, light and battery powered. I already had an Eye-Fi X2 Connect card so in about 5 minutes I had them set up to upload all scans directly to a new Evernote notebook I created and called Import.

The reason I created a new notebook was two-fold. First, the Eye-Fi doesn't let you set which notebook it should add new scans to, and just uses the Evernote concept of a "default" notebook. So instead of having to sort through an existing notebook for scans that need organizing, it will all go to a staging area for me to sort through. This decision also affects the "forward an email to Evernote" feature I often use, so having both sources go to the same place for me to sift through isn't a bad thing.

a family affair...

The second reason for a new notebook, is I can share it with my wife and we both have access to new scans. Seeing the size of the Doxie Go, we'll definitely be leaving it in the kitchen so my wife can scan all incoming mail. A shared Evernote notebook means she also gets instant access to the scans without a PC and without me in the way.

Speaking of keeping it in the kitchen, I'm really excited that we have our U-Socket installed there since the Doxie Go doesn't come with a wall charger. I'm sure an iPhone charger would work too, but having the USB socket right in the wall for the Doxie is pretty cool too.

lickable...

I can't speak highly enough of the user experience of the Doxie Go, from the first impression of the site, to ordering, to unboxing and installation; the experience is buttery and wonderful. They have definitely taken a page from Apple and made everything "lickable". About the only thing I could nit-pick about to this point was the order confirmation screen was the dull grey from some third-party payment service.

...the ugly...

So nothing is perfect right? And the Doxie Go is no exception. Where it falls down is trying to bulk import a lot of paper. I have that file cabinet right? So I had planned to sit for 3 hours a night while I'm watch TV or something, bulk scanning everything we had for the next few months. Sadly the Doxie battery gave up about 40 scans after its full charge. So I said, fine I'll just keep it plugged in and stand at my kitchen counter. No go. The Doxie Go only pulls juice from the internal battery and won't stay powered off just the USB power. So I was able to scan for about 10-15 minutes, and will have to wait 2 hours for it to charge again. This is clearly not the use case it was built for.

Another nit-pick, the marketing implies the Doxie Go has OCR built-in but its actually a software feature. So when you scan directly to Evernote you lose those additional features like auto-contrast and OCR. But its pretty moot for me, Evernote already has OCR that's pretty great.

final thoughts...

In the end, if all my incoming paper can be scanned and thrown away immediately, that's a huge improvement on what we have now. For the file cabinet, I'll have to break it up into batches of 25 pages or so and slowly scan them over the coming years.

Riddle: When isn't free space free?

2012-02-01T00:05:00.000-05:00

So tonight I discovered my hard drive was slowly being choked by some mysterious process writing gigs and gigs to it. So I moved 75GB of files to an external drive only to come back a few hours later and discover my free space was back down to 23 GB.

Where did 50 GB of files come from in just a few hours!?

Idea #1

Rogue process downloading large files...coughiTunescough

I had NetUse Traffic Monitor running and it clearly showed that there was definitely not 50 GB of downloads in that time period.

Idea #2

Rogue process writing lots of log files

In my investigation of what to move to the external drive I used GrandPerspective to get a visualization and catalog of what was on my drive. Thankfully I hadn't closed that window so I could rescan and compare what had changed. Here's the next head scratcher, it showed only a 4 GB total difference in used space between the two scans.

Idea #3

It was something on my wife's side which GrandPerspective couldn't see since it didn't have permissions to her files.

Nope, she only had 24 GB of files on her side.

Idea #4

Google for "mysterious hard drive full"

Surprisingly this got me some new ideas, like it was hidden files, or bad Time Machine backups to a non-existent external drive. Sadly they were not the problem. I even found someone with the same problem but no solution.

Idea #5

Run 'du' to show what GrandPerspective can't see

A this point I realized that GrandPerspective was reporting 104GB of "miscellaneous used space". So Googling for more info, one of the posts I stumbled on lead me to a page about Mac OSX Tiger Problems which introduced me to the BSD disk usage command 'du'. So it seemed like a lower-level command that would take some time, but would show me what GrandPerspective supposedly couldn't. Sadly it didn't and agreed with GrandPerspective that 804GB of my 931GB drive were being used while 'df -kh' agreed with the Finder that only 23GB were free. So four tools were giving me two different answers, that I had either 23GB free or 127GB free depending on which you asked.

Idea #6

Ask Google why 'du' and 'dk' can give different answers.

Sure enough, Google had an answer to why 'du' and 'dk' can differ. Turns out a process can hold onto a deleted file and the file will be unaccounted but the disk space will still be considered used. So at this point I gave in (sorry, never figured out who the offender was) and restarted my computer. Sure enough, after the Finder came back up...I had magically cleared up nearly 87 GB of hard drive space.

Moral of the story

Try restarting first, even for disk free space issues apparently. #facepalm

For that rant you read...

2012-01-18T08:15:00.001-05:00

Yesterday, I saw a stranger ranting about how my local town doesn't consistently use their call system to notify people of snow delays. He then went on to list at least four other alternative sources he could choose from and was finally "forced" to find out from the local TV station.

His rant was amusing because it reminded me of the comic Louis CK's bit about how everything is amazing, yet nobody's happy. It got me thinking that I wish someone had created a landing page that I could link a ranter like this guy to. Something in a similar tone to http://dearrecruiters.com and http://lmgtfy.com.

So that's what I did last night, I created http://yourenothappy.com

A year like no other

2011-10-10T13:50:00.000-04:00

Today is a significant marker in my life, the first anniversary of the passing of my mother-in-law. Her death was sudden and I was unprepared for it. While shocked and sad, after the week of mourning was over, I expected life to return to normal quickly. In many ways it did, but in retrospect I'm amazed at how much flux there was throughout the following year.

In hindsight, I now see how depressed I was for several months after her death. It feels silly to say that, since I'm generally a happy person. The idea of me being depressed for a day let alone a month feels very out of character. But I was and it affected the decisions I made and blurred my focus, both personally and professionally. I've been searching during most of the past twelve months and it took a while to find myself again, as my wife has so patiently endured.

My productivity at work took a nose dive for a while, partially because I became extremely disinterested in what I was working on. My disinterest led me to entertain notions of leaving ESPN. As the old cliche goes, I started thinking about what I wanted to do with the rest of my own life. I considered starting my own company and began working to that end. Around the same time I was contacted by Zynga, best known for the Farmville and Mafia Wars games on Facebook. I was flattered but the idea that I'd pickup my family and move seemed a bit crazy, so my thoughts turned to, "well if I'm really considering this, what is exciting in the network of people I already have and commutable?" This led to a string of interviews in the city at some great places like GetGlue and foursquare.

The interesting thing is that these interviews, while they didn't lead to job offers they led to other interviews. My interview at foursquare led to an interview at a stealth-mode startup. And that interview led to another interview where I got an job offer. In the end I didn't accept that offer but it's been a surreal ride to experience how the NYC tech startup scene works and how tightly-knit it is. The connections I've made have been pretty amazing, and I hope they will end up helping me someday when I start my own company. But that's for another year...let me continue.

While all this was going on, I got an interview request from Apple. That ride took me from a clandestine interview hidden away in a New York hotel, to a trip to the Cupertino mothership, all the way to a job offer that nearly turned my family's world upside-down. We were "this" close to uprooting my wife and kids to the Bay Area, a continent away from everything we had ever known. In the end, leaving everyone we had ever known was too great a hardship to accept, and that was one of the biggest lessons I learned this year. I took me quite a few extra months to learn it after I began reflecting on my own mortality, but for me, family and friends are too important to allow ambition to pull me away from them. I would have loved to have worked at Apple, lived in California, and have that notch on my resume, but I love seeing my kids playing with their grandparents more.

So though my path doesn't lead to One Infinite Loop, it doesn't mean my ambition has ended with that journey. I can take an East Coast path to get where I want to go. Amazingly, it looks like that path stays at ESPN. On the exact same day, actually in the same hour that I got my offer from Apple, I got news that ESPN wanted to create the role for me that I had been asking for for years, as a build engineer. I started that new role last week, and I haven't been this happy professionally in a while. It's exactly where I want to be right now, which brings me to my second cliched lesson, everything happens for a reason. If things had played out differently, I would not have been at ESPN to accept the new role.

With all that happened, Joanne hasn't been out of my thoughts for very long. I miss her, and I hope she is at peace. I know that right now, I am too.

Simplifying logging with Maven and SLF4J (Part 2)

2011-09-15T11:24:00.000-04:00

So in my previous post I explained how to simplify your logging with Maven and SLF4J. If you haven't read it yet, please do before reading more. Since then I've discovered an easier and cleaner way to remove the secondary frameworks from your Maven dependency tree.

Here's a revised overview of the steps:

Decided which logging framework will be your primary, aka who will actually write to your log file.
Define the dependency scope of all the secondary frameworks to be 'provided'.
Configure your project to depend on drop-in replacements of each secondary framework from SLF4J.

Define secondary frameworks as provided

Use the dependencyManagement section for this. Its used when you might have a dependency transitively.

Add dependency on SLF4J

Add the following to your pom.xml

Conclusion

So now in only 3 steps you can redirect all your logging to your primary logging framework without changing a line of code!

Newly open source

2011-08-11T22:03:00.004-04:00

Well its about 10 years too late for some of this stuff but I figured I'd open the source to my dead projects I have lying around. Some are pretty raw, like my flocking applet from a college course, while others are completely functional and dare I say beautiful code, like my X10 Java library.

FlockingApplet - a graphical applet that simulates the flocking behavior of birds.
handlecheck - a web app that searches the web to see if your favorite username is taken.
gwt-common-widgets - a collection of Google Web Toolkit widgets
x10-java - a Java library for home automation.

Parental Controls - The V-chip of 2011

2011-07-28T09:24:00.004-04:00

I've done something that I swore I'd never do, I've set ratings limits on my TV. As a kid/teen/young adult I swore I'd never use the V-chip on my kids. My thought was, how can you not be around to see what your kids are watching that you need to lock down your TV!? Now with the wisdom of 5 years as a parent, I can't watch my kids every second of the day, and for that 30 seconds I leave them to go to the bathroom, they somehow always turn on Wanted or 300 or Zombieland or _____(fill in the blank with a rated R movie I own). My 20 year old self would be very disappointed, but my 33 year old self says "You don't know what you're talking about." (P.S. He'd totally be geeking out our setup at my house though with our iMac-based home media server with 150 GB of movies played via a settop box (AppleTV) on an HDTV. 1998 Brian thinks that's AWESOME!)

Tonight's project: Motor shield, assembled! Sadly no motors yet, but it makes the servo easier to use!

2011-04-30T21:59:00.002-04:00

Taken at The Jacksons'

Tonight's project: Color LCD shield, assembled!

2011-04-27T22:22:00.002-04:00

Taken at The Jacksons'

My first Arduino shield, assembled! The Protoshield

2011-04-21T21:42:00.002-04:00

Taken at The Jacksons'

Buffalo Pretzel Chips, the greatest snack ever and they sell them at the Cafe. Dangerous...

2011-04-07T12:00:00.002-04:00

Taken at ESPN Building 4

Go-Kart Racing in Mt Kisco!

2011-02-25T14:48:00.002-05:00

Self-explanatory....

Best Practices with Maven: Versioning your Artifacts

2011-02-02T11:59:00.008-05:00

I realized today that I had made this nice flowchart about two years ago of how I decide when to add qualifiers and increment version numbers, but I never shared it anywhere very useful.

This is heavily based on the version numbering scheme that Maven inherently understands. You should also checkout the excellent versions plugin for Maven that include some great utilities for upgrading your plugins and dependencies.

TeamCity build triggering by GitHub

2011-02-01T20:03:00.007-05:00

So I started using GitHub for a side project and discovered their very cool feature of service hooks. A service hook allows a repository administrator to setup a callback to another service when a commit is made to the repository. For example it can send an email, or chat a message via Jabber.

Now continuous integration servers, like TeamCity, can poll source control systems every few minutes to see if any changes have been committed. But wouldn't it be more efficient to use a service hook to trigger a build?

Looking at GitHub's service hooks, there wasn't one already available to callback a TeamCity server, but right on that same page was a link to the open source repository for GitHub Service Hooks. They "eat their own dogfood" so to speak and make it very easy to contribute new service hooks back to them. So I took an evening, did my first Ruby coding in a while which included more time getting Ruby setup and working on my Macbook than actually coding. In a few hours I had committed a TeamCity service hook to my fork of the project and requested them to pull the changes from my fork.

After just a few hours the pull was completed and the changes were in production, wow! Turned out I had a few bugs and it took some back and forth to get it all ironed out, but its now available as a working service hook at GitHub!

How to use the TeamCity service hook

Begin by creating a new account on your TeamCity host. Since this account will be used to kick-off the builds, its best to name it something like "GitHub Service Hook" so your developers will understand the build history when they see "Triggered by GitHub Service Hook". Note the username and password you create as it will be used later.

Next, navigate to your GitHub repository and look for the Admin button and click it.

Select "Service Hooks" from the left sidebar.

Select "TeamCity" from the submenu.

In the form that appears, enter

the url to your TeamCity server (which can contain a path in the url if you run it on a shared host).
the build type ID which you can find in the address bar when you are on TeamCity and looking at the build you want to trigger (ex. "...?buildTypeId=bt123&...", in this example the ID is "bt123").
the username of the GitHub Service Hook user you created.
the password of the GitHub Service Hook user you created.

Once you press "Update Settings", the page will refresh and you should see the "TeamCity" sub menu item change to have a green dot.

If you select "TeamCity" again, the form will reappear with a new "Test Hook" button. Press this and it will manually trigger the build with the information you entered.

The next time you push new commits to your GitHub repository, GitHub will trigger your TeamCity build!

25 Years, A Moment in Time

2011-01-28T22:09:00.002-05:00

"Daddy, what happened?"
"It blew up, honey."

My sister was five and she was the first speak. I was seven and knew I was going to be an astronaut. We were in Florida on vacation and the shuttle was supposed to launch while we were there. My awesome parents drove us from our condo in North Palm Beach to the Cape, not once, not twice but three days in a row as the launch continued to get scrubbed due to cold weather.

I remember the instant the shuttle blew up, watching it from the side of a nearby roadway, and I knew exactly what happened. I remember the crowd gasp. And I remember my sister pulling at my father's arm and being the first in the crowd to say anything. I remember being annoyed, as most typical seven-year old brothers tend to get, when she asked a question I knew the answer to. I remember the look on my parents' face. I remember feeling sad. But most importantly, I remember how proud I felt and how much more I wanted to be an astronaut that day.

Today, I reflected on how did being there affect my life. Most obviously it kept my passion for space alive and two years later, in July of 1988, I went to SpaceCamp. Later, as I neared the time to begin planning what I would do after high school, my parents spent countless hours researching the path to NASA including how to become an Air Force pilot and how they could get me the most prestigious recommendation they could to earn me entry into the Air Force Academy. In the end I didn't choose that path and instead chose a path into computer science, thanks mainly to the effect of Jurassic Park.

Reflecting on the "what-if" of becoming an astronaut, as a now parent of two, I'm blown away by what my parents tried to accomplish for me. What an amazing thing, to have someone on this Earth who would go to any lengths possible to get you the right foundation to make your dreams come true instead of to laugh and scoff and say "sure Brian, an astronaut". And I'm blessed to have two, and now for the past decade I've had a third person too.

The other thing I've realized is the coincidence that this year is the 25th anniversary of that day, and also the year the space shuttle program will end. As my wife and parents know, for the past few months I've made it clear that I will be taking Penelope down to Florida to see the next and penultimate space shuttle launch. If Wally was older and able to appreciate it I'd bring him too because I want my kids to experience, at least once, the wonder of watching a manned spacecraft launch to the heavens and the imagination it sparks with that tangible discovery that anything really is possible. The symmetry that mine and Penelope's first launch will be 25 years apart had escaped me until today and the thought is bittersweet because who knows when, or if, she and Wally might see another launch of a manned mission to space.

Trends of Vulger Phrases

2010-12-17T12:53:00.001-05:00

Of course my mind first goes to typing vulgar phrases into Google's new N-gram Viewer but the results were pretty neat.

Simplifying logging with Maven and SLF4J

2010-09-14T17:35:00.012-04:00

UPDATE:Ceki commented below which prompted me to rewrite the third paragraph.

UPDATE 2:I have a better way of configuring Maven and SLF4J now.

The mismatch between logging frameworks always seems to come up in projects I've developed over the years. Little-by-little I've learned and relearned how to navigate the nest of runtime logging that occurs in non-trivial applications. With my latest project I think I finally converged on a solution that I'll carry forward to future projects.

So what am I really talking about? Have you ever been stumped, even for a short time, about where a certain log message is going and why it might not appear in your log? Often this happens when you are trying to debug an issue with a third-party library that's using a different logging implementation them your application. If you are nodding from familiarity, skip the next paragraph.

Let's start from the beginning. There are several logging implementations available for Java, the best known being Log4J and the java.util.logging (JUL) API that was added in JDK 1.4. You may also encounter Apache commons-logging which is a logging facade for library developers to abstract their logging so library users are free to choose their own implementation such as Log4J. But commons-logging has well-documented issues so that's where slf4j comes in as my logging facade of choice. I actually code all my new applications to use the slf4j API directly because it adds functionality over the logging implementations like parameterized log messages that are only evaluated if the associated logging level is enabled. But that's tangent to this post.

So how have you solved the usage of multiple logging implementations? In the past I've tried different techniques:

Configure each framework separately and have them write to their own log files.

Pro: Is there one?
Con: You need to monitor multiple files
Con: You need to understand the usage and configuration of each framework.
Con: If you are in a J2EE container you lose the log adminstration it provides.

Redirect everyone to standard out and redirect standard out to a file.

Pro: Its all going one place.
Con: Its all in standard out, even errors which can make adminstration tools fail to filter messages properly.
Con: You still need to configure each secondary framework including message formatting so all log lines follow the same pattern.

Write and connect bridges for each secondary framework so that they will log to one framework that is responsible for writing to the file, which I'll call the primary framework.

Pro: Its all going one place and category names, and levels are preserved through to the primary framework.
Pro: If the primary framework supports programmatic changes to log levels, it works for all frameworks.
Pro: If you are in a J2EE container that support live updating of log levels, it works for everything.
Con: You need to know what you are doing to develop the bridges, configure the bridge in each secondary framework and connect it all together properly.

So what's the magic solution I found? Well its a variation of #3 but it doesn't require any coding or any real knowledge of how to configure secondary frameworks. And I'll show you how to accomplish it using Maven and a logging facade API called SLF4J.

Here is the overview of the steps:

Decide what the primary framework will be.
Ban all secondary logging framework in your projects.
Update your dependencies to exclude the banned dependencies.
Configure your project to depend on drop-in replacements of each secondary logging framework from SLF4J and to use SLF4J to send everything to your primary framework.

Decide what the primary framework will be.

For my latest project, I'll be deploying to Glassfish which use JUL internally and has support in its admin console for live updating log levels without restarting the server, so it was easy to pick JUL as my primary framework.

Ban all secondary logging frameworks

Add the following plugin to your pom.xml

Add exclusions

This is where mvn dependency:tree -Dincludes=log4j:log4j is really helpful. If you try to build now, your build fail on the enforcer rule. Run this command to find which dependency is including log4j and add the necessary <exclusion>. Repeat until you find no more dependencies on log4j. Repeat for each of the banned dependencies.

Add dependency on SLF4J

Add the following to your pom.xml

Conclusion

So in 4 steps you can redirect all your logging to your primary logging framework without changing a line of code!

Best Practices with Maven: OSS forks

2010-03-21T12:05:00.001-04:00

Recently I came across a company that is forking several open source Java projects. I saw they were making a mistake that I also made a few years ago and have since learned from.

In Maven's distributed repository architecture project artifacts, like JAR files, are uniquely identified by a coordinate system composed of a group identifier, an artifact identifier, a version number, optionally a classifier, and a packaging type. For instance, the most recent version of the Apache Commons Lang project has a Maven coordinate (i.e.groupId:artifactId:version:classifier:type) of commons-lang:commons-lang:2.5::jar.

A few years ago, if I wanted to make custom changes to this project I would get the source, make my changes and then deploy the result to our private Nexus repository under a new groupId such as com.jaxzin.oss:commons-lang:2.5::jar. That might seem reasonable. Then a year later or so I tried something different and changed the artifactId like this commons-lang:commons-lang-jaxzin:2.5::jar.

Unfortunately there is a serious problem with both of these approaches. Maven supports transitive dependencies which means, if you include a dependency you get its dependencies 'for free'. But what happens when you depend on com.jaxzin.oss:commons-lang and indirectly include commons-lang:commons-lang? With either approach, Maven has lost all knowledge that these two artifacts are actually related. And when I say 'related' I mean they include different versions of the same classes. When Maven loses this relationship, it can't perform version conflict resolution and will include both versions in the output. It will compile against both in the classpath. If you are building a WAR file, it will include both in the WEB-INF/lib directory. If you are assembling or shading an "uber"jar, it will include the classes from both in your giant jar with all its dependencies. And unfortunately, the one that 'wins' is nearly indeterministic.

So what's the solution? How do you properly fork an open-source project privately?

The trick is to change the version, and leave the groupId and artifactId alone. That way, Maven still can detect the relationship and can perform version conflict resolution. So to complete the example I would fork Commons Lang 2.5 to a new coordinate commons-lang:commons-lang:2.5-jaxzin-1::jar.

Now I do have one further suggestion, but it's of questionable practice and I'm not sure how well it works. You might consider forking version 2.5 to version 2.6-jaxzin. This way, if Maven attempt to resolve version conflicts, it will know that your fork is 'newer/better' than 2.5. Maven sees version with qualifiers as being older than the unqualified version. I think the assumption is that if you are qualifying a version its a pre-release version like 1.0-alpha-1, 1.0-beta-1, or 1.0-rc-1. You can read more about how Maven version conflict resolution works and I know they have a major overhaul of this logic available in Maven 3.0 with the Mercury project.

But, in practice, when I've run into version conflicts like this I will add an exclusion clause where I depend on an artifact that is including the conflict transitively.

Not for Adoption

2010-03-18T15:20:00.002-04:00

Last night was my first session as a volunteer at the Danbury Animal Welfare Society (DAWS). I had attended an orientation a few weeks back and that's when I saw the facility for the first time, learned about the standard operating procedures and policies, and got to meet some of the cats I'll be working with. Now I'm not a person that enjoys change or meeting new people, but other than my immediate family I don't think many people are aware because I try very hard to hide my discomfort. Who knows, I could be wrong so feel free to call me out in the comments!

So far, this entire experience is quite out of my normal comfort zone, but I'm forcing myself to do this for several reasons. I learned about DAWS after attending their Puppy Love Ball, a fund-raiser they held in February, in support of a friend of mine who was honored as their Person of the Year. They premiered this mission video at the event and it had me hooked. To learn that DAWS is a shelter that doesn't euthanize animals for non-medical reasons was a real inspiration to me. I didn't even know this idea of a 'no-kill' shelter even existed. Another reason, I have wanted to volunteer somewhere simply to give back to a community. I'm not sure where my misunderstanding came from, but I've always imagined volunteering to be an unpleasant activity, like cleaning or manual labor. So when I found out that I could volunteer to be a 'cat socializer', it sounded like a perfect fit. Since my wife is very allergic to animal hair and dander, this would also be my chance to interact with cats on a regular basis without owning one.

This next statement may come off as brutally honest, another reason I was outside my comfort zone is the facility. Inside, its a clean, spacious and wonderful facility for the animals, but when I first arrived its exterior isn't exactly what I had expected especially since my introduction to DAWS was the grandeur of the Ball held at the Ethan Allen. The building looks like a large residential home and could easily be overlooked as a place of business. After visiting the DAWS location in Bethel I understood the importance of the sign and landscaping that my friend Paul created. Hearing about their goal to fundraise for a brand-new state-of-the-art facility by 2019, it made me even more impressed and connected with DAWS. I'd love to be a small part of them reaching that goal.

I arrived last night a few minutes early, uncertain what to do. Seeing others waiting outside for the door to open, I introduced myself and found out they were waiting to become adopters. I was starting to get a little nervous since none were other volunteers. Was I late? Was there a different entrance? Did I not read an email fully? After a few minutes I discovered I hadn't made a mistake when other volunteers arrived.

After a few minutes we were let in and I introduced myself and was introduce to the other cat program volunteers that were there. Unfortunately I'm joining the volunteer program at a time when everyone needs to be more hands-off with the cats because of a skin infection that is making the rounds in the shelter. They have done an amazing job handling the situation. I hope in a few weeks the issue will behind DAWS.

From what I gathered from the my first session, a two-hour evening consists of feeding the cats, playing with them, cleaning litter boxes and then finishing the night by getting everyone back in their cages. This is the kind of volunteering I can handle!

The thing I really took away from last night though was my experience with a cat named Daphne. She's a beautiful black & white cat and very reminiscent of the family cat I grew up with for 14 years named Purrina. She has some trouble with her hind legs, and she seems a bit of a special-needs case because of it. On her cage is a sign that reads "Not for Adoption" and those three words seemed to say so much about DAWS. Here is a cat that in many cases would be euthanized because no one goes to a shelter looking for a special-needs pet. But instead DAWS, with their no-kill policy, chose to give this cat a chance to be adopted and she's so close to going home.

Daphne cemented why I want to give two hours of my week to DAWS, in a time when I feel like I don't have 5 extra minutes to spare. If you are located in the greater Bethel/Danbury area, I encourage you to donate your time or donate your money.

First Impressions from NoSQL Live

2010-03-12T00:40:00.003-05:00

Today I drove up to Boston for the day to attend NoSQL Live. My experience so far within the NoSQL community has been limited to what we've built in-house at Disney and ESPN over the past decade to solve our scaling issues, more recently has been ESPN's use of Websphere eXtreme Scale, and the very latest has been my own experimentation with HBase which hasn't gotten much further than setting up a four node cluster. I've read a little about Cassandra, memcached, Tokyo Cabinet and that's about it. So before the sandman wipes away most of my first impressions of the technologies discussed today, I wanted to record my thoughts for posterity or, at the very least, tomorrow.

Cassandra
Cassandra seems to be the hottest NoSQL solution this month with press about both Twitter and Digg running implementations. My impression, I'm wary of "eventual consistency". I don't feel I understand the risk and ramifications well enough to design a system properly. When Jonathan Ellis of Rackspace Cloud mentioned that Digg needed to implement Zookeeper-based locking on top of Cassandra so that diggs get recorded correctly, I realized how poorly I understand eventual consistency and how risky it could be. But my impression of Cassandra isn't all negative, it definitely seems to have less baggage than HBase by not being built on top of HDFS. I'll get into what that means a little later.

Memcached
Unfortunately the speaker that 'represented' memcached gave off a vibe that really turned me off to the product. I know that's incredibly shallow, but this is first impressions after all and not perfectly-evaluated impressions. Mark Atwood sat on the first panel of the day "Scaling with NoSQL" and his whole attitude seemed to say "memcached is all you'll ever need and these guys next to me are just overdesigning hacks". His answers were short and his tone was quite condescending even when addressing audience questions. Not a very good first impression of him. But luckily today wasn't my first impression of memcached as I was pointed in its direction just last week by a Disney colleague. My research before today has me intrigued about using it as a replacement for ehcache as a second-level cache provider to Hibernate which we use as an ORM in one system at ESPN right now.

Document Oriented Databases (Riak, CouchDB, MongoDB)
Wow, this is a subgroup of NoSQL technology that I had heard of in passing but was really unaware of what problem they were trying to solve. Riak had the best answers for scaling and operational-ease. With homogeneous nodes and consistent hashing, Riak promises that adding and removing nodes are seemless. CouchDB and MongoDB sounded like a 'me too' answer so I'm interested to find out what that really means for each, or better yet what it doesn't mean. But the concepts of document-oriented databases really meshes well with ESPN's current fantasy user database. Our fantasy user profiles are stored in a traditional RDBMS as serialized maps of maps, one row for each user. Since its serialized to a BLOB column its completely opaque to reporting and analytics. To keep that model but have vendor support for divining information and having transparency into it sounds exciting. I really need to look into these. Riak definitely won this round of first impressions.

Tokyo Cabinet
This was a technology I was referred to by a colleague and read through their site last week. I was far from impressed then since it seems much too low-level for my taste, similar to my impressions of Carbonado which we use at ESPN. The lightning talk by Flinn Mueller got me a little more interested. He seems to be doing interesting things but from an analytics and reporting perspective. He was vague on how loads the data from his primary store and what the scale of the data is, so my first impression: its a toy. I'm sure that's an unfair characterization but I'm not trying to be fair tonight. But honestly, Tokyo Cabinet makes no bones that it punts on horizontal scaling which is the deal breaker for me.

Hypertable
I looked at Hypertable (as in read their website) about 18 months ago on the suggestion of a colleague when discussing HBase around the same time. This conference didn't change my opinion, which is "It's HBase but written in C". It doesn't seem to bring anything else to the table which to me is a blocker. JVM implementations are available for all the operating systems I use and so I don't like the idea of needing to find the right binary to download for a given box. When it comes to Java vs. C, I choose Java but I'm also extremely biased as I've been a Java developer nearly my entire career.

Full-stack JavaScript
This was my favorite of the lightning talks, and possibly my favorite of the conference. It felt a little tangential to the NoSQL topic, mainly because Jim Wilson covered more than just data storage. The idea, what if you could use JavaScript on your server, in your client and use JSON for talking between the layers and as the storage format? Crazy, right? I say brilliant. His few slides were mildly embarrassing that dissected each of the popular stacks of today by how many languages you need to learn (Java, XML, etc) as well and the various impedance mismatches between layers (ORM, Object marshaling to JSON or XML, etc). "ORM is an antipattern" was an enlightening take on something I've accepted as necessary. Full-stack JavaScript is something I'll be lusting after for a long time, especially since he made it sounds so attainable with node.js, rhino and MongoDB. As soon as his slides are online I'll be linking to them as well as passing them around the office.

HBase
Well I saved HBase for last. It's the one I've had the most experience with, though that experience can still be measured in hours. As I hinted at earlier, this conference gave me the first impression that HDFS is a weight around the neck of HBase. I was surprised to get that feeling from the room, since my impression has been purely positive so far. It is also getting a lot of flack from the 'single point of failure' problem associated with the current HDFS architecture's Name Node. Apparently performance is a dog since it was "only" designed to be highly distributed with no promise of when you'll get your data. This burden seems to carry over to HBase. But after talking to Ryan Rawson one-on-one at the end of the HBase lab, it's clear he is of the strong opinion that its getting a bad wrap. He also makes very convincing arguments about the scale of what HBase is currently doing in real production environments vs. competitors like Cassandra. It's very pursuasive and you can read more of the details in a very active thread I kicked off on the HBase user group earlier this week.

Conclusion
HBase is still the front-runner of my personal candidates for a NoSQL option for ESPN as it has been for a long time. Cassandra's design choice of eventual consistency is a little scary to me because I don't know yet how to design for it, not because it is inherently bad choice. Documented-oriented databases just made a big blip on my radar. Memcached is interesting if I want to stick with a traditional ORM-based architecture. Tokyo Cabinet and Hypertable are all but off my radar. And the lusty vixen of them all is a full-stack JavaScript architecture.

Disclaimer: Though I mention my employer ESPN in this post, these are my own personal opinions and don't represent the opinions of the company. The final decision on this stuff is "above my pay-grade" as they say.

Java Puzzler

2010-02-24T13:10:00.013-05:00

I bought the book Java Puzzlers by Josh Bloch and Neal Gafter a few years ago and enjoyed it. If you aren't familiar with it, it covers rare, odd and usually counter-intuitive edge cases of Java in a brain-teaser style of presentation. For both a Java user and an analytical mind its a fascinating book.

Well today I stumbled onto a puzzler of my own and thought I'd share. Can you tell me what the main method of this class will output?

1 : public class Parser {
2 :
3 :  private static <T> T parse(String s, Class<T> type) {
4 :    // Simple implementation only supports long primitive
5 :    if(type == long.class) {
6 :       return (T) Long.parseLong(s);
7 :    }
8 :    throw new UnsupportedOperationException(
9 :                   "parse() only supports long right now!");
10:  }
11:
12:  public static void main(String[] args) {
13:    System.out.println(parse("1234", long.class).equals(1234));
14:  }
15: }

So what gets written to standard output? If you said 'true', then you'd be wrong. If you said 'false', then you'd also be wrong! The code above won't even compile! There are a few features of Java that are colliding here to give odd results, including generics, type erasure, primitive types and autoboxing.

So what happens exactly? You'll get a compile error like this:

Error:line (6) inconvertible types
found   : long
required: T

The error is on the return statement line of the parse() method. Long.parseLong() returns a primitive long, but since a parameter type can only represent an Object type, you can't cast a primitive to an parameter type. Also, it appear auto-boxing doesn't work in this case, so it fails with a compiler error.

But wait, doesn't the code explicitly use the Class object that represents the long primitive, long.class? But see 'long.class' is syntactic sugar for the constant field Long.TYPE which is of the parameterized type Class<Long> since type variables only support using Objects.

So realizing this, we can change the return statement to use a Long instead of a long:

    return (T) Long.valueOf(s);

Now the code will compile, but something is still wrong because it prints out 'false'.

Knowing that the return type of parse("1234", long.class) is Long, take another look at the puzzle. Can you see the problem? This one is subtle. The numeric literal '1234' that is inside the call to equals() needs to be auto-boxed and since it is a literal int, it is boxed into a Integer. But an Integer object isn't considered equal to a Long object because they are different types, so equals() returns false.

So it a few interesting features combine for some strange behavior. Hope you enjoyed this puzzle!

UFOs, Ghosts and Bigfoot

2010-01-25T23:29:00.006-05:00

So I hope you don't think I'm a complete loon, but I've always been interested in the paranormal, cryptozoology and lights in the sky. I think it is driven by my need to try to answer all those unanswered questions in life.

Lately I've been watching various 'reality' shows on these topics like MonsterQuest, Paranormal State and Ghosthunters. Don't get me wrong, I'm not gullible enough to believe these shows are finding evidence of anything, its just some good ol' fashioned mind-numbing popcorn TV for me to fall asleep to.

Watching them has reminded me of a few unexplained incidents I've had in my life and I wonder if you've experienced anything similar? I've got three that all happened to me over a decade ago but were so unnerving that I remember them vividly. So here are my campfire ghost stories, feel free to share yours!

Incident #1: The Mysterious Flash
I don't remember the exact date or even the season of this first incident, but my best guess is it happened during the summer of 1993. It was the summer before my sophomore year of high school. I had a goal to read 50 books that summer. I know what you're thinking "wow, was he really that cool?" My motivation was a challenge from my freshman English teacher that I couldn't do it, and I ended up proving him wrong. The reason I'm telling you all this is to set the scene that I was in my bedroom reading a book around 10 o'clock at night.

My Dad is awesome and years earlier had installed overhead track lighting in my room attached to a touch-sensitive dimmer switch. The track lights hung from the ceiling and I had most of them pointed outward to face the walls so I wouldn't be blinded. However the one light that hung near the head of my bed I faced inward to act as a reading light. For whatever reason, I was laying in bed with the lights dimmed as low as I could and still be able to read. I can't explain the inner workings of my 15 year old self but I liked the lighting that way.

As I'm laying there in bed with my back propped against the wall my entire room is flooded with brilliantly blinding light! I stare at my book and realize the light isn't coming from above me it's from behind me as I can see my shadow and the shadow of the book I'm holding cast against the far wall of my room like someone is holding a spotlight a few feet behind my shoulder. And before I can react it's gone! The whole flash takes about half a second. Then as I turn to see where the light came from I come to the realization that I'm laying on the wall, it couldn't have possibly come from behind me and cast the shadows I saw. Now being rational, my first thought is that I imagined the shadows and it was a simple power surge so I go downstairs and ask my parents if they saw anything, but they hadn't.

Incident #2: The 727 at 500'
For this next incident I wasn't alone. I was still in high school and my Mom and I were in the car together coming home from an after-school activity, probably band practice or musical rehearsal. It was twilight and as we drove home I see a plane on the horizon. As I watch it I realize it is not near the horizon because its far away, it's because it is close but flying low to the ground. I pointed out the plane to my Mom and wondered out loud if something is wrong with it. She was surprised and decided to pull over to watch it. As the plane drew closer we both realized that it was a commercial airliner, not a small prop plane out of Danbury as I was expecting. Now mind you, I grew up in the hills of New Milford where the closest airport that can land an airliner is 40 miles away. It continued to approach us and at this point I realized it was traveling extremely slow for a jet of its size. Finally as it passed directly overhead I realized it was the size of a 727, no more than 500 feet from the ground, and going maybe a 100 miles an hour which is very close to, if not less than, the stall speed for an jet like that. But if that all wasn't strange enough, here's the part that haunts my mother and I to this day...it was dead silent. I mean so silent that the crickets stopped chirping. The jet passed and disappeared past the treeline and we never heard a thing. In that pre-internet age, my only recourse was to check the newspaper every day for at least a week. Nothing.

Incident #3: Close Encounters of the Orange Kind
My last weird event is probably the clearest of the three in my mind. It was September of 1995 near the beginning of my senior year of high school. My Dad and I were flying to Florida for the weekend so I could tour the Ringling School of Art and Design and see if it was where I wanted to spend the next four years of my life studying computer graphics. In the end, I went to Trinity College in Hartford but that's another story.

On this trip we flew down on a Friday night. It was one of the first night-time flights I'd ever been on so I was pretty excited. We were seated on the left side of the plane that faced the Atlantic Ocean for most of the trip. Even without much to see but the blackness of the ocean I still sat watching out the window almost the entire trip. Midway through the trip I got to see thunderhead clouds out on the horizon. It was a lot of fun watching a lightning storm from 200 miles away. But as I watching I realize that one of the clouds has begun to light up with a constant orange light. The cloud wasn't lit in a diffuse way, it was very clear it was emanating from a point within the cloud. If you've seen the movie Close Encounters of the Third Kind in the scene where the UFOs arrive you can only see points of lights within the clouds, it looked exactly like that but for only one light source. I'm not saying I think this was a UFO, only that the special effects in this movie are a good approximation of what I saw. So I immediately got my Dad to lean over and take a look to see if he had any idea what it was. As we sat there and watched, it became extremely bright. It was so bright that you could see the light cast through the windows onto the right wall similar to what happens when the setting sun is off the left wing. We watched it brighten for about 30 seconds, stay at full brightness for a minute or two and then fade to nothing in about the same amount of time it took to arrive. To this day I have no idea what I saw.

My thoughts on Google's Chrome OS

2009-11-24T15:22:00.001-05:00

Unless you've been living under a rock, you have heard that last week Google demonstrated their Chrome OS for the first time in public. They also open-sourced what they have so far as the Chromium OS project. You can watch an overview video here:

I followed the event, watched the YouTube videos and even played with a copy of Chromium OS via gdgt.

So here are my thoughts on my limited experience so far. It seems like a perfect fit for the netbook market. "Living in the cloud" seems like a great idea for the ability to access your data anywhere. A verified boot system will be a godsend to anyone who has ever had reinstall an OS because it just got 'crufty'.

But I don't understand why they have, so far, omitted the concept of a desktop. One of the coolest features of Chrome is its ability to turn a web app into a 'desktop' app, which prompted me to to find Fluid for the Mac. Why force new users of Chrome OS to live in a browser when they could have still kept the concepts of a desktop with 'desktop' applications? There is also a nearly direct analogy in Chrome OS between its tabs and the Windows task bar or Mac Dock. So why make it feel so different instead of trying to fit into the conventions every other GUI-based OS already established?

I know it is fun to "rock the boat" and "shake the tree", but I'm just not finding the benefits to tying so closely to existing browser paradigms instead of reusing some of the desktop conventions for this new 'web' OS.

Maven and Legacy Projects

2009-11-16T16:40:00.005-05:00

Recently I've been helping a colleague introduce a dependency on a legacy project that hasn't been "Maven-ized". Often the "easy way" to add a legacy dependency is to throw the JAR into our Nexus repository and be done with it. But this legacy project was a little trickier and is my new poster child for why taking the easy way can lead to headaches and frustration.

Your legacy project might have compile-time dependencies you need.
Maybe your legacy project implements an external API, or maybe it uses a library and exposes that usage in its API. "So what", you say? "I'll find it at compile-time for my project and I'll add the dependency." Well, now every project that wants to use your legacy project is going to go through the same discovery and embed the dependency in their POM. The right way is to define this dependency in the pom.xml for your legacy project so all dependent projects retrieve it transitively.

Your legacy project might have run-time dependencies you need.
Similar to the last example, your legacy project might use a library but not expose it's use directly. You won't discover the missing dependency until you try and run your project. Here's where the power of the 'runtime' scope of a transitive dependency becomes obvious.

Your legacy project might include library classes within its JAR.
Now here's a real yuck factor when it comes to dealing with other people's code. Our example legacy project bundled a small subset of its dependencies right in its JAR. It wasn't until after we threw it into Nexus that we discovered this rather severe violation of Maven standards. The best solution, get access to the project's source, mavenize the project properly and release a 'pure' artifact. If you don't have access to the legacy project's source you'll need to strip the extra classes from the artifact and construct a pom that includes the right dependency.

Summary
So here's a really quick summary of why not to half-ass adding legacy projects into your Maven infrastructure:

Any transitive dependencies will be missing.
With legacy jars that embed the classes they depend on you risk class file collisions

Medicine is so Young

2009-11-10T21:50:00.000-05:00

I think its undeniable that one of the hottest topic of this year is health care. While I've been casually following the political discourse, its far from my inspiration for today's post. My one year old son, Wally, had a reaction to penicillin this week and I question why current medicine is still so reactive rather than proactive. Since allergies are something that can change and fluctuate, that led me to also wonder why we don't have more frequent testing too.

Standardized testing
I'm looking forward to the day when there is a standard battery of tests for allergies and conditions. It's beginning with the prenatal screenings available during both of my wife's pregnancies, but why, for instance, is there no standard allergy testing post-birth? From the perspective of a patient, current medicine waits for a reaction to an allergen which seems so dangerous to me.

Continuous diagnostics
When can I get my little implant that continuously monitors my blood-work and vitals? I've been dealing with the medical 'miscellaneous bucket' that is IBS for 6 years now and don't feel like I'll ever get an answer about what is really afflicting me. I see my doctor once a year, and she doesn't really seem to have an answer. I know, I know, demand answers, fight for myself, blah blah, that's not my point. It's currently not 'bad enough' to force me to demand anything yet. I bring up my current state during my annual checkup, and that's about all I feel I'm empowered to do right now. I strongly believe if there were a way to easily and continuously monitor medical data points (blood, hormone, etc) within my body and let me correlate that with the ebb and flow of symptoms there would be a much higher chance of being able to find the problem.

Online records
I've been 'using' Google Health since it was released last year. But my doctor's office has no tie to my account so I'm forced to update it by hand. Not to mention all my historical data is no where to be found. For the providers that Google Health does currently support linking, I have a 50% success rate getting them to work. I was able to link my CVS prescriptions but failed to link my Quest test results. When I followed Quest's instructions, the receptionist at the testing facility looked at me like I had three heads when I asked to get my results online. She had no idea what I was talking about.

jaXzin.com

Paperless

digital notes...

portable scanning to the cloud...

a family affair...

lickable...

...the ugly...

final thoughts...

Riddle: When isn't free space free?

Idea #1

Rogue process downloading large files...*cough*iTunes*cough*

Idea #2

Rogue process writing lots of log files

Idea #3

It was something on my wife's side which GrandPerspective couldn't see since it didn't have permissions to her files.

Idea #4

Google for "mysterious hard drive full"

Idea #5

Run 'du' to show what GrandPerspective can't see

Idea #6

Ask Google why 'du' and 'dk' can give different answers.

Moral of the story

For that rant you read...

A year like no other

Simplifying logging with Maven and SLF4J (Part 2)

Define secondary frameworks as provided

Add dependency on SLF4J

Conclusion

Newly open source

Parental Controls - The V-chip of 2011

Tonight's project: Motor shield, assembled! Sadly no motors yet, but it makes the servo easier to use!

Tonight's project: Color LCD shield, assembled!

My first Arduino shield, assembled! The Protoshield

Buffalo Pretzel Chips, the greatest snack ever and they sell them at the Cafe. Dangerous...

Go-Kart Racing in Mt Kisco!

Best Practices with Maven: Versioning your Artifacts

TeamCity build triggering by GitHub

25 Years, A Moment in Time

Trends of Vulger Phrases

Simplifying logging with Maven and SLF4J

Decide what the primary framework will be.

Ban all secondary logging frameworks

Add exclusions

Add dependency on SLF4J

Conclusion

Best Practices with Maven: OSS forks

Not for Adoption

First Impressions from NoSQL Live

Java Puzzler

UFOs, Ghosts and Bigfoot

My thoughts on Google's Chrome OS

Maven and Legacy Projects

Medicine is so Young

Rogue process downloading large files...coughiTunescough