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.

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 accessible…

Should this be a microservice?

After having developed several distributed systems and been a part of dozens of architectural discussions I decided to put together a way to frame the microservices debate. Microservices have been fashionable for some time. A lot of it stemmed from the fact that big and successful cloud companies are using microservices.  It seems reasonable that to create a “serious system” one must be using serious tools and architecture, today it’s microservices.  No engineer wants to be called out for creating a solution that “doesn’t scale.”

The definition for a microservice varies, but overall it tends to be a piece of your system that can run somewhat independently (unless of course it depends on other microservices) and has a REST or queue processing interface.  Overall code encapsulation and separation of concerns have all been around for a long period of time.  Current evolution with containers, fast networks and REST API allows people to easily integrate pieces of their system using web se…