Microsoft //Hackathon: Surface Pro 3 i5 4 gig ram and 128 SSD

Translate This Page

Microsoft //Hackathon: Surface Pro 3 i5 4 gig ram and 128 SSD

  • Comments 1

Well I can’t talk about the AMAZING thing I built with a team made up of people from Microsoft Research using TouchDevelop, Services, High School Interns and College Interns, but I can discuss that I used the I5 based Surface Pro 3.  Let’s just say that our Hackathon project was very physical and could break things, the Surface Pro 3 survived a lot of abuse. 

I ran Visual Studio 2013 Ultimate, Office, 2013, Eclipse, Chrome, IE 11 (my preferred browser), TouchDevelop, some analytical tools and visualizers, and so forth.  No problems, this included an emergency download and installation of Visual Studio 2013 Ultimate early in the //Hackathon, while using Visual Studio Express 2013 in the background. 

Our product used the Microsoft Windows Phone (sadly only the high end phones would work for this pass of the product), Azure cloud technology and WHOLE lot of fun!  My goal was to have a great demo for students and I got it.  Just have to wait till I can discuss the product, it is AWESOME!

So to give a teaser for the app…umm, no I can’t.  Sorry.  But it is way cool.  Just like the Surface Pro 3.  But if you watch the NFL, let’s just say it could have been down there on the field…ok, not really, but it could be at your home around Thanksgiving.  If you make it.  Yourself. 

(Note to Microsoft internals, please vote for my //Hackathon project!  Any questions please direct them to me at my internal email, thanks!)

Leave a Comment
  • Please add 8 and 3 and type the answer here:
  • Post
  • Sounds exciting! This kind of end user experience is definetly something that will give a boost to developer adoption of MS3 as a viable alternative to the power laptop/desktop. Waiting to hear more on the project itself!

Page 1 of 1 (1 items)
Generic Content

Legal Note:

  1. The author, Sam Stokes, is an employee of Microsoft
  2. There is no guarantee that anything I write is correct, I do try to make sure that what I write is correct.
  3. Use anything written in this blog at your own risk
  4. Test what I write about before using the information
  • Sometimes posts will disappear because I realized that they really don't fit with the total chaos of what I write about
  • Links are tested and available on date of publication, what others do with their links are out of my control

Restrictions:

  • Whatever I write on this blog is unedited by management or anyone, which should be obvious from the randomness of the blog.  I simply write about things I like.
  • Microsoft does not restrict me in anyway, so I generallyblather about whatever I want to.
  • For personal reasons I will not write about:
    • Company confidential stuff, mainly because Microsoft is more transparent than any company I have ever worked for.
    • Other people unless they give me permission to write about them