Microsoft Mobile Development

Since taking my position as a .NET developer I've really been exposed to a variety of experiences. Most recently I've been doing a great deal of Mobile platform development for Microsoft Windows Mobile. It's been great experience that's taught me to be really resourceful in terms of managing network connectivity, memory, screen space and in general device capabilities. I feel like any developer or aspiring developer should be involved with this sort of environment moving forward in their career.

SOA And Windows Mobile Networks

Service oriented architecture approaches to development make building applications on the .NET framework a real pleasure. You can quickly deploy solutions for mobile, windows and web with very little client based development. Since I've been involved in this approach I've been amazed at how quickly I can build an application for our mobile devices and then turn around and crank out a standard Windows/Web version for regular use.

The Samsung Blackjack II Sucks

Unfortunately my experience with Trios, Symbols, Acers and a few other PDA's I don't remember has taught me that my Windows Mobile 6 Samsung Blackjack is a really limited piece of junk. It won't render many of the more advanced controls and the interface with the joystick is not so user friendly. Many devices out there are far more worth what you pay for them. However the Blackjack is a very durable device that can take one hell of a beating. This is coming from someone who knows what it is to really beat a device up.