Sign in
|
Join
|
Help
Search
Your Daily Mark.Net
Treat others as you want to be treated
Home
Contact
RSS for Posts
Atom
RSS for Comments
Recent Posts
Every build you break
Redirecting the copy of output assemblies for individual solutions
No time to read and try
Unit test papers
Object Mothers
Tags
.net IBM Websphere MQ C#
Code analysis
Team build
Team Foundation Server
vs2005
web site build performance
News
Currently reading
Community
Home
Blogs
Media
Email Notifications
Go
Links
Personal blog
Archives
April 2008 (1)
March 2008 (2)
January 2008 (8)
August 2007 (3)
July 2007 (2)
March 2007 (2)
February 2007 (1)
October 2006 (1)
July 2006 (1)
June 2006 (2)
May 2006 (1)
April 2006 (1)
January 2006 (1)
December 2005 (1)
November 2005 (5)
October 2005 (1)
September 2005 (1)
August 2005 (2)
The Joel Test: 12 steps to Better code
the 12 steps to better code by Joel
.
These are the 12 steps:
The Joel Test
Do you use source control?
Can you make a build in one step?
Do you make daily builds?
Do you have a bug database?
Do you fix bugs before writing new code?
Do you have an up-to-date schedule?
Do you have a spec?
Do programmers have quiet working conditions?
Do you use the best tools money can buy?
Do you have testers?
Do new candidates write code during their interview?
Do you do hallway usability testing?
This is the link to
the dutch article
Posted:
Mon, Jun 26 2006 3:24 PM
by
Mark Henneman
| with
no comments
Leave a Comment
Title
(required)
Name:
(required)
Website:
(optional
)
Comments
(required)
Remember Me?
Please add 7 and 1 and type the answer here: