Welcome to MSDN Blogs
Sign in
|
Join
|
Help
Steve Rowe's Blog
Ruminations on Computing - Programming, Test Development, Management and More
This Blog
About
Email
Syndication
RSS 2.0
Atom 1.0
Search
News
Disclaimer
Computing
Raymond Chen
Larry Osterman
Audio Fool
Eric Anderson
{codesqueeze}
Coding Horror
Matthew van Eerde
James Whittaker
Testing
Braidy Tester
I. M. Testy
Testing Reflections
Test Obsessed
Tags
Architecture
Audio
Books
Computing History
Learning to Code
Management
Media Center
Netcasts
Other
Personal
Programming
Software Process
Testing
Video
Vim
Windows
Recent Posts
Design Patterns Are Not Outdated
Is there really a benefit in lossless audio formats?
A Review of a Kindle
StackOverflow DevDays
Forging a Team Identity
Archives
November 2009 (3)
October 2009 (1)
September 2009 (1)
August 2009 (1)
July 2009 (2)
May 2009 (2)
April 2009 (5)
March 2009 (4)
February 2009 (5)
January 2009 (2)
December 2008 (6)
November 2008 (2)
October 2008 (9)
September 2008 (6)
August 2008 (5)
July 2008 (3)
June 2008 (9)
May 2008 (9)
April 2008 (5)
March 2008 (12)
February 2008 (10)
January 2008 (8)
December 2007 (10)
November 2007 (14)
October 2007 (11)
September 2007 (13)
August 2007 (19)
July 2007 (21)
June 2007 (7)
May 2007 (11)
April 2007 (23)
March 2007 (14)
February 2007 (15)
January 2007 (16)
December 2006 (7)
November 2006 (2)
October 2006 (2)
September 2006 (2)
August 2006 (7)
July 2006 (2)
June 2006 (4)
May 2006 (7)
April 2006 (9)
March 2006 (11)
February 2006 (7)
January 2006 (5)
December 2005 (2)
November 2005 (3)
October 2005 (3)
September 2005 (2)
July 2005 (1)
June 2005 (2)
May 2005 (1)
April 2005 (5)
March 2005 (3)
February 2005 (6)
January 2005 (5)
November 2004 (3)
October 2004 (1)
April 2004 (1)
March 2004 (2)
August 2008 - Posts
Friday, August 15, 2008 11:11 AM
Code Review Options
There are many ways to conduct a code review. Here are a few ways I've seen it done and the advantages and disadvantages of each. Over-the-Shoulder Reviews Walk over to someone's office or invite them to yours and walk them through the code.
Posted by
SteveRowe
|
2 Comments
Filed under:
Software Process
Wednesday, August 13, 2008 10:55 AM
Code Review Rights and Responsibilities
Code reviews are an important part of any project's health. They are able to find and correct code defects before making it into the product and thus spare everyone the pain of having to find them and take them out. They are also relatively
Posted by
SteveRowe
|
2 Comments
Filed under:
Software Process
Thursday, August 07, 2008 11:00 PM
The Company You Work For Matters
In an episode of Stack Overflow Podcast, Jeff Atwood made an interesting point. He spoke of the difference between companies that deliver code as their product (like Microsoft) and companies who use code to support other business interests (the
Posted by
SteveRowe
|
2 Comments
Filed under:
Learning to Code
Thursday, August 07, 2008 10:59 PM
Test Code Must Be As Solid As Dev Code
All good development projects follow certain basic practices to ensure code quality. They use source control, get code reviewed, build daily, etc. Unfortunately, sometimes even when the shipping product follows these practices, the test team
Posted by
SteveRowe
|
1 Comments
Filed under:
Testing
Saturday, August 02, 2008 11:02 PM
Cause of "Internet Explorer cannot open the Internet Site" found
Perhaps you, like me saw a rash of sites giving the error "Internet explorer cannot open the Internet Site" yesterday. At first I thought one of my machines was messed up. Then I saw it on another machine. This one running XP. A virus perhaps? I can't
Posted by
SteveRowe
|
1 Comments
Filed under:
Windows