Good evening, Slashdotters. Feel free to check out the rest of our Windows 7 launch coverage, including a quick video interview with Microsoft Corporate Vice President Brad Brooks as well as a rundown of how the Windows 7 tweet-up went on Thursday night

We’ve tried to withhold ourselves from sourcing our news from leaky valves in Microsoft as of late (and you can see where that’s gotten us. ahem), but we don’t just stay away for the sake of keeping ourselves out of that eternally stressful race for content. We tend to stay out of it because behind every leak, someone’s job suffers as a result.

I had a very open interview with someone at the launch event. This person frequently deals with product leaks, and as a result, it’s fair to say that the person knows exactly how said leaks impact work, the lives of everyone connected to the project, the public perception of a product, and so forth. My interview with this particular Microsoft employee was fulfilling in the sense that I’m able to offer an uncensored glimpse into what Microsoft has to deal with whenever someone decides to leak a build, leak a screenshot, break an embargo, and what not.

Check the break to read about how it all went down. Keep in mind that there’s no video or audio and that this is, indeed, a long read apparently not as long as some people have seen in the past. Thanks is due to the anonymous commentators who pointed this out.