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!

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…

Pull Requests and Code Reviews

Software development involves a great deal of collaboration.  One of the most basic blocks of collaboration on a software development team is a code review.  There have been many different ways of doing code reviews over time, some of this has been dictated by the tools available.  Git and online source collaboration tools created a set of best practices that are worthwhile of adopting on any team.

About a month ago I have looked at various articles about how to best create a Pull Request (PR) and do a code review and the attached presentation is the result of this research.  The presentation can help you guide your team and develop a set of collaboration practices that works for your particular situation.

It’s good to start out with why to seek a code review.  Having clarity about your intentions helps you guide the person helping you with code reviews and also to manage your expectations about you can get out of the code review.  The reasons for seeking a code review are generally …