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.

Comments

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!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers. Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily acce

Intuitive Programming - Comments

Comments are a topic of vibrant discussion.  Ever since programmers could leave some text in the program that was ignored by the machine the debate started: “what’s a good comment, what’s a bad comment, why comment?” There are endless instructions to programmers that say many of the following things: 1) Describe your function! 2) Don’t write in the comment what you wrote in the code. 3) Tell people why you are doing what you are doing. What I think has been missing from this discourse is the audience for comments and through those audiences there is intent.  The code is being read, skimmed or analyzed by people and tools.  So what are the audiences and reading modes? 1) Maintaining and enhancing the code 2) Skimming through the entire module or file to figure out what the overall structure is 3) Reviewing the test files to check out the test coverage and edge cases 4) Seeing the docstrings of functions while being in a separate file altogether 5) Reviewi