Comments on: Joel Test Results http://amazing-development.com/archives/2005/03/04/joel-test-results/ gain new insight now Fri, 05 May 2006 23:56:28 +0000 http://wordpress.org/?v=2.0.2 by: Uli http://amazing-development.com/archives/2005/03/04/joel-test-results/#comment-88 Tue, 08 Mar 2005 15:28:53 +0000 http://amazing-development.com/archives/2005/03/04/joel-test-results/#comment-88 I think the point on "the best tools money can buy" is that a lot of companies know that there are better tools around but for financial reasons, they compromise on the features they get. This is true on version control systems, code quality tools and development environments - especially when the language of choice is not Java, but C++ where no free tools are around and commercial ones are very expensive. You may as well question yourself why that much companies still use CVS although it is really no longer state of the art and there are a lot of better tools for that purpose. So a lot of companies prefer to have no tool cause of the money they would have to spend on it. And this is wrong, since you will have a return on investment very soon (The problem might be that this return on investment is hard to mesure). I think the point on “the best tools money can buy” is that a lot of companies know that there are better tools around but for financial reasons, they compromise on the features they get. This is true on version control systems, code quality tools and development environments - especially when the language of choice is not Java, but C++ where no free tools are around and commercial ones are very expensive.
You may as well question yourself why that much companies still use CVS although it is really no longer state of the art and there are a lot of better tools for that purpose.
So a lot of companies prefer to have no tool cause of the money they would have to spend on it. And this is wrong, since you will have a return on investment very soon (The problem might be that this return on investment is hard to mesure).

]]>
by: Yashima http://amazing-development.com/archives/2005/03/04/joel-test-results/#comment-87 Tue, 08 Mar 2005 09:16:58 +0000 http://amazing-development.com/archives/2005/03/04/joel-test-results/#comment-87 Some points "pro" regular automated builds: - the build machine is usually not your own computer and therefore should be independent to the well-known phenomenon "works on my computer" - there needs to be a certain amount of automation to get regular builds = automation is good because humans keep forgetting details - if more than one person works on a project, a tool like cruise control kicks the butt of whoever screwed up the repository very fast! The more people on a project the more important this becomes IMHO. - last: it is soooo easy to set up automated builds everyone should do it! A good spec/design/schedule is worth a lot but very hard to come by and keep current. If anyone got hints on that one, I'd be glad to hear them Some points “pro” regular automated builds:

- the build machine is usually not your own computer and therefore should be independent to the well-known phenomenon “works on my computer”
- there needs to be a certain amount of automation to get regular builds = automation is good because humans keep forgetting details
- if more than one person works on a project, a tool like cruise control kicks the butt of whoever screwed up the repository very fast! The more people on a project the more important this becomes IMHO.
- last: it is soooo easy to set up automated builds everyone should do it!

A good spec/design/schedule is worth a lot but very hard to come by and keep current. If anyone got hints on that one, I’d be glad to hear them

]]>
by: Frank Spychalski http://amazing-development.com/archives/2005/03/04/joel-test-results/#comment-86 Mon, 07 Mar 2005 16:54:33 +0000 http://amazing-development.com/archives/2005/03/04/joel-test-results/#comment-86 Joel says so :-) Yes you are right, in our cases it's probably overkill but it takes very little time to configure and could help to detect some problems. If I could choose between getting nightly builds and e.g. a spec or quiet working conditions I'd choose the later. But nobody gives me this choice... Joel says so :-)

Yes you are right, in our cases it’s probably overkill but it takes very little time to configure and could help to detect some problems. If I could choose between getting nightly builds and e.g. a spec or quiet working conditions I’d choose the later. But nobody gives me this choice…

]]>
by: schlumpf http://amazing-development.com/archives/2005/03/04/joel-test-results/#comment-85 Mon, 07 Mar 2005 16:00:19 +0000 http://amazing-development.com/archives/2005/03/04/joel-test-results/#comment-85 who says if it's "good" to be able to answer "yes" to a specific question? It depends on the requirements of the project! For <a href="http://freshmeat.net/projects/bibi/" rel="nofollow">my project</a> it would be nonsense to have nightly (yes! you should have nightly, not daily builds!) builds because I don't work on it every day ;-) and unless someone makes a really big donation I'll never work with the best tools money can buy, but that doesn't mean I would write better code if I did (oh, you did want to donate? please do so anyway, I may be wrong!) . who says if it’s “good” to be able to answer “yes” to a specific question? It depends on the requirements of the project! For my project it would be nonsense to have nightly (yes! you should have nightly, not daily builds!) builds because I don’t work on it every day ;-) and unless someone makes a really big donation I’ll never work with the best tools money can buy, but that doesn’t mean I would write better code if I did (oh, you did want to donate? please do so anyway, I may be wrong!) .

]]>