Skip to main content

What will make me use SkyDrive


I saw the UI updates from SkyDrive team a few days ago.  It reminded me that I had a SkyDrive account.   I actually used SkyDrive for a couple of years.  It was really never my go-to solution for sharing. 

It didn't have desktop tools. Supporting Mac was an afterthought and in general there was nothing special about it.  In comparison Box.net had great plugins and corporate sharing.  DropBox had a great folder that I could use, but SkyDrive has been kinda neither here nor there.

SkyDrive was also very confusing with Live Mesh and its still competes in a way with Windows Live Sync.

In my test of Windows Phone 7 it was nice to see that you could upload photos to SkyDrive automatically, but again it wasn't really enough for me to say: "wow, I really should move my photos to SkyDrive"

There is one place in my house where I would really LOVE photos off SkyDrive and that is on my XBox.

I've been one of those cord cutters who uses Comcast purely for internet now and my XBox 360 reigns supreme in my living room.  I don't have a stationary desktop and there is no way I am going to create a "home server" which will be collecting dust somewhere in the corner.  My photos are on my laptop, flickr and Facebook.  What would be really killer is if my XBox natively connected to SkyDrive and I could show my friends photos directly from SkyDrive.

User Experience would be very key.  It would be nice if based on my XBox Live ID my SkyDrive photos folder was automatically available and I could easily go and show slideshows from the folders.  XBox is powerful enough to do caching of the images on the local drive and pre-fetching to make slideshows and browsing through folders very simple.

If that was in place I'd use SkyDrive all the time.  I think I am not alone.

Comments

Popular posts from this blog

Quality of Code is Quality of Life

About 20 years ago when I started working in technology companies I remember “the best” engineers had similar patterns:
-They worked crazy hours
-They knew the systems no one else knew
-They could react and deliver something faster than anyone else
You could always hear other employees say: “Bob is really smart, no one knows how to get anything done in system X besides him!”

This reinforced optimization around being the only person who knew how to do something in some part of the code.  That in turn reinforced job security and bargaining for those engineers, but also chained them to a particular system.  We had big code bases of C++ or Java code where some “Bob” hacked up features as soon as he possibly could.  “Bob” would have occasional nuclear disasters where he’d sleep in the office or through the weekend and then everyone would thank him for how he “saved the day.”  “Bob” sacrificed his quality of life to get praise when he hacked stuff up quickly and then the second time when n…

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…