Skip to main content

One week on a Mac

It’s been a week since I’ve switched to the MacBook as my primary machine for work.

For a long time Windows user (since the DOS days) and having worked at Microsoft for 5 years I would say that I am a Windows Super User. There is something in Windows that I don’t know but it ain’t much ☺.

So after a week my productivity is still down. The coolness factor is up. I actually like taking my computer around with me again. It’s very light and it makes my DELL Latitude look and feel ancient.

Positive emotions come from:
- Spotlight which is absolutely awesome!
- Installing/uninstalling applications is amazing.
- Unix shell and all unix things installed.
- Doc
- Application management – I actually like the fact that you can see which applications are loaded and that closing a word document doesn’t quit word.
- Super fast startup and shutdown time
-

Negative emotions:
- Outlook is the best e-mailing and scheduling program ever. I miss it.
- Not being on the Windows domain is an inhibitor.
- I like pushing alt and seeing the shortcuts, I also like being able to use the keyboard for menus.
- Ctrl+Del is a great shortcut that allows me to delete a word at a time.

Couple of must get items I found so far:
- Firefox with a del.icio.us plugin.
- Windows Live Mesh to keep my documents synched up.

A couple of cool items that I found on the Mac:
- Aquamacs – a nice looking emacs.

I still use Windows for my development because I know Visual Studio and .NET better then all other stacks, but for Office use MacBook is a pleasure to use.
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…