| Author |
What tools are discussed?
|
Tony William
Ranch Hand
Joined: Jun 27, 2005
Posts: 54
|
|
By looking at the TOC of the book, tools in different areas (such as Code Management, build script, issue tracking etc) are discusse.
Are the software / tools discussed mainly open-source? or in fact commercial software that the reader needs to buy so that we can try?
|
MCP, MCP+I, MCSE(NT4), MCSE+I, MCSE(2000), MCDBA, MCSD(VS6)<br />SCJP 5.0, SCBCD 1.3<br />ICED(v5.0), ICSD (WSP5.0)
|
 |
Jared Richardson
author
Ranch Hand
Joined: Jun 22, 2005
Posts: 113
|
|
Originally posted by Tony William:
By looking at the TOC of the book, tools in different areas (such as Code Management, build script, issue tracking etc) are discusse.
Are the software / tools discussed mainly open-source? or in fact commercial software that the reader needs to buy so that we can try?
We kept the book topics as language and vendor neutral as we could, but included language specific resouces in the appendixes. I've also set up an online version here.
We've provided links to both open source and commercial vendors, but honestly, you can almost always set up the entire system with open source software if you're willing to invest the time. One of the blog entries that I haven't written yet is how I would set up a shop if I was starting from scratch.
So, no, there are no tools you'd have to buy to try these ideas out.
|
Check out <b>Ship It! A Practical Guide to Shipping Software</b><br /> <br /><a href="http://www.pragmaticprogrammer.com/titles/prj/" target="_blank" rel="nofollow">http://www.pragmaticprogrammer.com/titles/prj/</a>
|
|
Barry Andrews
Ranch Hand
Joined: Sep 05, 2000
Posts: 523
|
|
|
Does the book talk about the pros and cons of using open source tools/libraries in a software project?
|
|
Jared Richardson
author
Ranch Hand
Joined: Jun 22, 2005
Posts: 113
|
|
Originally posted by Barry Andrews:
Does the book talk about the pros and cons of using open source tools/libraries in a software project?
No. Ship It! focuses more on using a tool. We have no strong preference for closed source versus open. Find a tool that works and use it. To me, it's better to use a any source code management tool (open or proprietary) than no source code management at all.
Some environments really want the support contracts that come with a commercial product (however there are more companies offering similar support for open source products these days). Other companies with tight budgets tend to want open source because the up front cost is lower.
Personally, I've spent enough time at startups to be a confirmed cheapskate and generally use open source tools when they are available. I've also run into bugs in the past that we've been able to fix, which is also nice.
|
|
 |
|
|
subject: What tools are discussed?
|
|
|
0
