I am struggling a bit with ths topic: “Ramping up.”
Wednesday, I forgot my phone, glasses, and external hard drive.
Thursday, I forgot my phone and wallet.
Today, I remembered everything but I found an issue in the latest release in the Infragistics WPF controls so I’m wallowing a bit trying to decide if I should work around the issue for the moment or plow straight through.
So I am having a bit of trouble ramping up as it were. Read more…
Microsoft has yet another new initiative. Ramp Up This site is geared toward giving developers fast-track learning. If you need to learn about mobile development, you can find a module to help. Learning ASP.Net, covered. Blah, blah, blah. It might be useful. It might be more marketing garbage. I don’t know enough to comment on that issue at the moment.
Then there’s always the .Net University. I learned about this one today as well. Again, I don’t know enough to comment on its usefulness.
Today the vacation ends and the trip home begins. We need to catch the 11:00 ferry back to the mainland then link up with our shuttle to take us back to the Cancun airport. The 2 hour wait at the airport should be entertaining. We fly out at 4:20. It’s a short 2.5 hour hop to Dallas. There is a 3+ hour layover in Dallas. The flight back to Portland is about 3.5 hours. Hopefully, we’ll be home around midnight. That’s a 16 hour travel day when you included the timezone changes. Tomorrow, I’ll pick up Aenya, register for classes and get ready to dive back into work.
PS: I still hate flying.
What can I say? The water is warm. The days have been relaxing.
We arrived on the island two days ago. We met up with the rest of the group on Wednesday then loaded into a van for the drive down to Playa Del Carman. The ferry crossing was easy enough. After a little confusion we found the house. I watched another stingray working its way across the ocean floor.
Yesterday, I had an ear plug malfunction. I tried a new pair of ear plugs and they immediately leaked. With the tubes in my ears the water flowed straight down the back of my throat. Needless to say, it was time for me to get out of the water. I’m carrying everything I need to handle problems like this. That sidelined me for the rest of the day. I finished reading Daemon.
This morning, I was feeling fine and I joined the others on a snorkeling charter. Pizza over cards, naps all around and here we are…
Tomorrow, we have reservations to go parasailing. I wonder how that will turn out…
We made it to Dallas without any trouble. My new Timbuk2 bag rolled right through the TSA scanner without any extra drama. Netbook, external DVD drive, external harddrive, power adaptor, extention cord, half a dozen USB cables, blah, blah, blah. What can I say? I’m a geek. Read more…
Good Enough
Hi. My name is <withheld> and I have a coding problem. I’m an obsessive/compulsive programmer. For every feature request, I can think of 5, No 10! (so-called) improvements.
You say you need a knife to cut a tomato. I think Swiss Army knife with a saw, scissors, tweezers, multiple screwdrivers, leather reamer (yes I’ve actually used it for its intended purpose), can/bottle openers (including wine) and oh yeah a couple blade that could cut up your boring tomato.
Am I thinking ahead?
Am I simply showing off?
Am I getting my nerd on?
Am I ignoring the needs of my users so I can mentally masturbate?
Is there any real difference in any of these questions?
Let the war in my head begin…
Yes. I mean, No! I’d never do that. Well, maybe I would. But it’s cool.
So how does it end?
How do I find the disciple to develop a widget that is good enough without anything extra?
Read more…
I like to display the version number in the status bar of my applications. Here’s a way to get that information at run-time via reflection.
private void DisplayVersion()
{
Version v = System.Reflection.Assembly.GetExecutingAssembly().GetName().Version;
lblVersion.Content = "v" + v.Major + "." + v.Minor + "." + v.Build + "." + v.Revision;
}
So I was getting this error:
Error while trying to run project: Unable to start debugging.
The components for the 64-bit debugger are not registered. Please repair your Visual Studio 2008 Remote Debugger installation via ‘Add or Remove Programs’ in Control Panel.
A little surfing and I found a solution. Install the debugger! The 64-bit debugger is not installed by default. The installer is on the Visual Studio install disc. “<Drive Letter>\Remote Debugger\x64\rdbgsetup.exe”
