Episode 4: A new start

On February 9th, I will be starting my new position at Duke Hospital. I will be updating the software that provides the doctors a summary page view of a patient's vitals, recent lab results, and other crucial information with the option to "zoom in" on a given dataset or increase the timespace to twenty four hours, or three months, etc.

This is a crucial application that helps doctors and other healthcare professionals save lives and increase quality of life for their patients. I am proud that I will be part of this team of two contractors with one mentor from the regular IT staff.

At the same time, it's bittersweet leaving Microsoft in the middle of a product release cycle. There were so many more tasks to complete and improvements to make that now may be left incomplete as my team is down on pair of hands. I'm sure they'll get by, but I will miss them.

Changing jobs is never easy. I hope in this blog to track my path toward a gruntled and combobulated place in my work life, and maybe find a little inner zen along the way.

Also, did you ever notice that "combobulated" sounds like "I'm hanging out with a guy name Bob until the wee hours of the morning"?

Comments

Post a Comment

Popular posts from this blog

Managing to Lead

Image
Since I entered the workforce a decade and a half ago, I've had many different managers with distinct approaches to leading. I've learned a great deal from them about what techniques have been helpful and which ones less so. My company recently entrusted me with the responsibility of a people management role. In preparation for the change, I thought back over the years to decide what kind of manager I would like to be. Here are my thoughts on the four responsibilities a manager should fulfill. Going for a Drive Let's imagine that managing is like going on a road trip together with the people who report to you. What steps can you take to make the journey a successful one together? How do you deal with obstacles that arise, and learn from the trip so far? Grease the Wheels One of the most straightforward aspects to managing is to make sure that the people reporting to you can get their work done day to day. Ensure that they have the right tools and equipment, and
Read more

Moving up

The Duke Health Technology Solutions has offered me a full time position and I have decided to accept! This is a marvelous step forward and I'm very excited to join the team. It does mean that I'll have to pass off my current project to another contractor as I'll be shifting my job responsibilities, but I'm confident that the codebase is well commented and clean enough that it should be relatively easy for another software engineer to pick up where I'm leaving off. It's been a very interesting transition. The work environment here is much different than what I experienced at Microsoft. Here, the expectations and pressures seems to be much more reasonable whereas at Microsoft I would have been in dire straits if I did not work at least 50 hours a week. This could partly be my aptitude, but I think that everyone in the local office worked at least that much so I certainly wasn't alone. At Duke, while there will still be pressures of deadlines and deliver
Read more

Please properly dispose old knowledge

Greetings!  I have a confession to make.  When I learn something, I tend to expect that knowledge to remain inviolate and don't continually check to be sure that it hasn't changed.  This is a Very Bad Thing®© TM in the programming world.  Coding conventions and guidance change all the time.  Still, as humans, we are loath to replace old, time worn techniques with new ones. Disposing done wrong For example, I learned from the .NET Framework 2.0's documentation that the IDisposable pattern consists of a "public void Dispose()" method, a "protected void Dispose(bool disposing)" method, and a finalizer.  The first method calls the second with true and then removes the object from the finalization queue.  The last method calls the second with false.  All actual disposing happens in the protected method. using System; public class ResourceUser : IDisposable {     bool m_disposed;     ~ResourceUser()     {         Dispose( false );     }     pu
Read more