You’ve Got Questions, I’ve got Answers… Part 2

OK, here's your chance. Blast away.  I did this last year, and got lots of questions from people about how hiring and recruiting works at Microsoft, as well as some test questions.

So, what would you like to know? Something about Sparkle? Or Acrylic? Something about testing at microsoft? Or more on hiring and recruiting?

Here's an Acrylic stitched picture I took during an August camping trip to the Mt St Helens area. The mountain to the left missing it's right (northerly) side, is Mt. St. Helens. The lake that is now 200 feet higher than it was 25 years ago is Spirit Lake. Yep, the bottom of the lake is where the side of the mountain is now.

Click to view original image

Comments (6)
  1. dhchait says:


    How is Sparkle meant to interoperate with Visual Studio, especially given that I hear there’s a XAML designer being contemplated inside VS 2k5 as well?

    Thanks – Daniel

  2. adamu says:

    Hi Daniel,

    Sparkle project types are VS project types. Same compiler, same build system. No difference. So there is full interoperability with VS.

    While we’ve not said anything about a XAML designer in VS, that would be a logical conclusion.

    I would envision that the difference between Sparkle and a VS XAML tool would be the target customer; features would diverge because of the different audience.

    Before Sparkle, I used to work on SQL tools, so I’ll give you a SQL example. You can design the metadata for a SQL Database using SQL Enterprise Manager, using VS’s Server Explorer and Database projects, and in Access (yes, really you can target SQL, not just Jet in Access). Which tool would you use? Each one of those tools has a different audience (IT Pro, VS Dev, and Access Dev) and is customized to that audiences particular needs.

    For Sparkle, first and foremost, the audience is the pro designer. Remember SteveB saying "Develoers, Developers, Developers, Developers" like 30 times a few years back? Sparkle thinks Designers, Designers, Designers, Designers!

    Sparkle should be a comfortable environment for designers. It has a different look and feel than VS does, and has different driving scenarios.

    Because Sparkle and VS have the same project types, Sparkle enables designers and developers to work far more closely together, with the tools that each is most comfortable. A key scenario for Sparkle is the iteration that occurs when a designer builds prototype UI and then a developer has to attempt to emulate what the designer built.

    Another designer feature is our color picker; it’s a typical designer friendly piece of UI that a developer would probably think takes up too much real estate.

    A third example is modifier keys for drawing paths. Holding shift or alt down while drawing to constrain proportion is something that designers are used to, but I imagine that a VS XAML tool would not use these.


Comments are closed.

Skip to main content