Creating a Check-In Policy
Jim Presto from the Team Foundation Version Control team is creating a series of blog posts (Create Policy – Information) that discusses how to create check-in policies. He posted step 1 today (Create Policy – Step 1).
To experiment with policies in the Beta 1 Refresh release, be sure to download the Policy Driver (Visual Studio 2005 Team System Prerelease Utilities: Workspace Home).
Paul Chapman, the Build & Release Manager for Developer Division documentation (e.g., .NET Framework SDK, Visual Studio, Visual Studio Team System, etc.) has an opening on his team for a Software Development Engineer/Test (SDE/T). The primary responsibility of this job is ensuring that the documentation we produce is of high quality by testing it using automation. You can view the job description online (Job Details). If you’re interested, register and submit your resume online (Microsoft Careers) and then send an e-mail to PChapman.
You’re using Visual Studio 2005 Beta 1 Refresh and you stumble upon what appears to be a big juicy bug. What now? Marie Hagman has posted (Bug Reporting Best Practices) some information on making the most of the MSDN Product Feedback Center.
Process is the Problem
In their annual survey of software developers, InfoWorld asked 467 respondents, What do developers want? The results were not too surprising, but according to this related article, The process is the problem for developers:
… the most important problems lay not in the code, but in the inner workings of their development teams and processes.
… development initiatives would be more successful if the project-management process could be streamlined and made more transparent.