Movember is complete and I got to shave off my Mo today. And let me tell you, it feels great to have that caterpillar off my upper lip.
But the best part is that I was able to raise $393.55 for a good cause. Final standings: #2 in Kansas, #554 in the US, and #6940 internationally.
Update: The wonderful Appelgate family just donated $20 to push me to $413.55! I am now #593 in the US and #7373 internationally. I guess processing paper checks takes a little bit longer than online donations!
So I owe everyone who donated a huge thank you for supporting me and my Mo. I am looking forward to hitting everyone up next year. So if you are a friend and have the ability to grow a Mo, I will be bugging you next October. And if you have a wallet or purse, I will be begging for more donations. That is assuming Kari lets me do it again!
Prostate Cancer can be diagnosed using with a DRE (digital rectal exam) and a PSA (prostate-specific antigen) test followed by a biopsy if necessary. The biopsy consists of a procedure where needles are inserted into the prostate (ouch!). The good news is that it is likely an out-patient procedure (no nights in the hospital). The American Cancer Society recommends the PSA and DRE on a regular basis for men over 50. Or those with a higher risk (African American or those with a family history) the tests should be performed on a regular basis starting at 45.
Once diagnosed, Prostate Cancer has many treatment options and depends upon many factors. For details on each one please consult a physician (I am no doctor but I play one on my blog). Here are just a few methods of treatment:
Yippee! Donations are over $200 dollars after the the generosity of my lovely wife, my mother, and a great guy named Clay!
And just for Jeremy, here are some pictures from this evening. Enjoy!
And now for something completely different – the serious part. For the most part I avoid serious topics on my blog but this seems like a great opportunity to help educate the men (and women) around me. So here is a quick list of symptoms.
Frequent urination; especially at night
Difficulty starting or stopping urination
Weak or painful urination
Blood in urine
Those are just a few of the symptoms. If you have any of these you should see a doctor – the earlier that it is caught the more likely you will beat it.
My biggest role model is my dad (Virg Wallentine). For the first 16 years of my life he had a Mo. And it turns out that my father-in-law, my brother-in-law, my uncles-in-law (Bob and Millard), and even Kari’s god-father had a Mo at some point in their life. Unfortunately, I found very few pictures of my family (uncles, cousins, grandparents) – I wish I had pictures of my cousins (TJ and Justin for sure).
So enjoy the fantastic Mos that my role models had. And don’t forget to donate!
Day 13 and I am starting to feel the pain. My Mo is getting itchy and the skin is tighter than normal. But that isn’t the toughest part – I had two job interviews over the last 7 days. Luckily, one of the guys at the company had read my blog about it so I didn’t have to find some way to bring it up.
Anyway, the Mo is coming in and I hope to be getting more donations soon. Hear that family and friends – SOON!
And thanks to my good friends and neighbors (Scott and Angie Wallace) for a generous donation. FYI, I am currently sitting at $113.55 which puts me in 850th place in the US and 15256th place internationally.
Developing software is a very tough business. But days like this make me believe that the world would be better off without software! For two days I have fought a very simple but elusive issue in Eclipse. Basically, when I installed Eclipse it wasn’t picking up any execution environments so no project would compile nor run. A screenshot of the empty Execution Environments screen is below.
Empty Execution Environment
I first thought this would be an easy problem to fix so I used the world brain. When that failed, I had to actually use my brain. It turns out, Eclipse gathers information about JREs available and stores that information in a configuration file (libraryInfos.xml in the .metadata/.plugins/org.eclipse.jdt.launching/ directory inside the newly created workspace). And I think this auto-generation is where the bug lies. Specifically, when Eclipse grabs the version information from a newly added JRE/JDK it can get corrupted. When it works correctly the Execution Environments screen looks like the following. FYI, in this case I used the Sun JDK 1.6 to run Eclipse.
Available Execution Environment
Here is a snippet of the libraryInfos.xml file when the bug is visible: <libraryInfo home="/opt/sun-jdk-1.6.0.07" version="CompilerOracle: exclude org/eclipse/core/internal/dtree/DataTreeNode.forwardDeltaWith 1.6.0_07">
and here is a similar snippet when the bug is not visible: <libraryInfo home="/opt/sun-jdk-1.6.0.07" version="1.6.0_07">
Notice that the version information is pretty funny looking?
And it looks like it is connected to the .hotspot_compiler file that I am using. The contents of it are: exclude org/eclipse/core/internal/dtree/DataTreeNode forwardDeltaWith
which causes the following to be printed on the command line when Eclipse starts: CompilerOracle: exclude org/eclipse/core/internal/dtree/DataTreeNode.forwardDeltaWith
So I assume this is a bug since it would be a crazy feature. My work-around is to move (or rename) the .hotspot_compiler file the first time I run the new Eclipse. I then add the Java JREs, close down Eclipse, move the .hotspot_compiler file back, and then restart Eclipse. Once the JREs are added the issue no longer persists (unless new JREs are added).