Skip to main content

1 Day OS X Lion Test: Three Favorite Things and One Small Problem.

Today I downloaded OSX Lion from the Mac OS App Store. The entire installation went flawlessly: the system upgraded and booted up as expected. I wanted to share the things I noticed as a person who does business communication and software development. For those of you who do not want to read the entire post I have to say that there are good reasons to upgrade, but you have to watch out for a couple of quirks.

Number one most favorite upgrade is the Mail App. It got a complete makeover. Conversation threading really works now. It’s a pleasure to use.
Mac OS X Lion Mail App

The app also seems to be a little faster to start up and that’s always a good thing.

My second most favorite improvement is the way multiple desktops work. Sliding desktops side to side feels more intuitive. The dashboard as a desktop of its own seemed like a brilliant idea as well. I seldom remembered to use my dashboard before but now I pop into it frequently.

Another productivity tool that I very much appreciate is iCal. I connect to multiple calendars and iCal is one of my most used applications. I have it linked to, Microsoft Exchange, Google Calendar and Facebook. In the new iCal I found a nice surprise a port of iPad Day view:
Mac OS X Lion iCal - Day View

It shows the full day agenda and also gives you a way to scroll through the appointment timeline on the left hand side.

All my applications that were installed on the Snow Leopard continued to work with the exception of NetBeans. NetBeans silently stopped launching. I had to go look at the logs to find out that Java runtime has been uninstalled. Issuing java from the shell prompt started an installation and addressed the problem, but I guarantee that if I wasn’t in the tech field I’d never figure this out. Once I have got the Java runtime everything worked as expected.

In Summary I believe Lion is a worthy upgrade. None of the features were particularly breakthrough but Apple showed continuous innovation and polish in a lot of places where it mattered.
Post a Comment

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!

SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Two Critical Questions for Your Next Interview

I’ve interviewed probably over 500 engineering and management candidates over the last several years.  There have been a lot of really smart people who have applied at DocuSign, Microsoft and Tempo Automation. A surprising number of them didn’t have a clear answer to these two essential questions:

Why are you interested in joining our team?Why should we be interested in you? 
If you are an applicant, having a prepared answer for these questions is critical.  If you are a hiring manager, you should ask them and have a clear answer to these questions at the end of the first interaction with your future team mate.

In a field where work is somewhat predictable and static, those questions are less critical, but in software development perseverance, ingenuity and focus make all the difference. These are the two main questions that will separate a subpar and a superb hire.

When I discuss those two questions with an applicant I try to go below the surface.  Generic answers like “it says you ar…

Ego in Your Decision Making

Oxford dictionary defines Ego as: “a person's sense of self-esteem or self-importance”. It says that it is “responsible for reality testing and a sense of personal identity.” For a lot of us techies those were really important functions that probably served us very well early in our career.  We had to be assertive, we had to choose a coding style guide, pick our frameworks and “be decisive”.  However when it comes to engineering management the same things that used to help might be turning into a liability.

When my job changed from writing code to creating an environment where the best code is written - it took me a while to understand how my ego was holding me back.  I kept applying the old tricks - defining the architecture, the final design and task priority.  What ended up happening is those things led me to turn off a lot of the best and brightest people on my early teams.

I remember the feelings of being aggravated when I had to go over an explain my decisions and get buy …