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 Meetup.com, 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

Lessons from my 9 Year Journey with DocuSign

After over 9 years at DocuSign I am taking on a new challenge.  It’s been phenomenal seeing the
company grow from from 25 to 2000 employees.  DocuSign has changed the way the people do business and I am proud of it.  The next chapter is going to be heading up software development at Tempo Automation - a 25 person startup that is changing the way people produce electronics.  While I am extremely excited about the future, this is a good time to reflect on my journey and share the things that contributed to the success and things that I will do differently next time around.
1: Focus on the Customer One of the key things that contributed to the success of DocuSign and my personal career is relentless focus on the customer success.  From the very beginning our CTO has taken meetings, listened and prioritized requests and feedback coming from customers.  People who could not be bothered by customer requests didn’t last long.  As a result over time our engineering team retained and reward…

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …

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!