Skip to main content

Windows 8 Impression

The big news this week was the unveiling of Windows 8. There is plenty of coverage of features and the video that shows the new GUI. Here is coverage from the site that I use for my hardware news: http://www.engadget.com/2011/06/01/microsoft-unveils-windows-8-tablet-prototypes/

Here is my take on Windows 8:

The new GUI is fantastic and is borrowing heavily from the great work that was put in place by Windows Phone 7 team. I like that interface because it's elegant, minimalistic and it actually doesn't require heavy 3rd resources so that those can be used for processes that actually need them.

I also love the fact that OS supports HTML5 and JavaScript. I think Microsoft finally learned from WPF and other proprietary frameworks - people don't like them. HTML and JavaScript are adopted by millions of developers and it is going to be an easy adoption curve.

What I don't like is that the new GUI seems like it just sits on top of the old desktop. I suppose it makes a lot of business sense and Microsoft did do that with Windows 3.1 when it was sitting on top of DOS. What I'd prefer is that if they actually switched the whole thing around. The native OS would be using Metro and HTML interfaces and a Virtual Machine would pop up to run your legacy applications if you ever needed those.

A couple of things that I didn't see but I was hoping to see:
1) an application store that had curated Windows8 applications
2) a cloud integration where OS heavily relies on Live services. Synchronization and data sharing should be built directly into the new OS and work between my XBox, WP7 and W8.

Those features might still be coming but something and I am keeping my fingers crossed.
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…

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…