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

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!

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…

Hire Fast, Fire Fast? Not so Fast.

Silicon Valley is full of advice and it frequently comes from people who have little experience on the subject matter.  A popular topic surrounds hiring and terminations with the king catch phrase being: “Hire Fast, Fire Fast.”  To me, what that usually means is lack of diligence, thought, communication and courage.

When hiring people love going with their gut feel, often with disastrous results.  There is an obvious subject of diversity of thought, appearance and background.  When thinking “fast” you are probably hiring people like yourself because humans quickly react to people who they believe are in their tribe.

A startup that lacks the resources of a big company often becomes so desperate to get technical staff that when a decent candidate comes along, excitement ensues and the employer doesn't slow down to put them through a more rigorous hiring process.

I highly encourage technical founders and engineering executives to write out their precise hiring process.  Of course, y…