The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Joined: Oct 05, 2001
Ilja, CruiseControl sounds cool. Can you please elaborate or offer more resource on this tool? Thanks. [ March 12, 2002: Message edited by: Doug Wang ]
It covers automated testing and building, continuous integration, as well as refactoring as the authors refactor the case study many times. IMHO, its an invaluable resource. I have the book myself and love it!! These tools make life easier as a developer, because it automates a lot of the things we would have to do at the command lind by hand. A lot of developers that I know, think that it adds too much extra work (like making test cases), which is a load of rubish! I guess that's why their projects are always so buggy These tools when used together and effectively will make you a more effiecient programer!! Your code will have less bugs as you are constantly testing it, and you'll learn how to effectively test your applications for performance and scaleability issues. No Java/J2EE developer today should over look these tools. Even if your don't adopt the whole XP methodologies, adopting automated builds and testing is a must!! Just my two cents, /rick [ March 12, 2002: Message edited by: rick salsa ] [ March 12, 2002: Message edited by: rick salsa ]
Joined: Jul 11, 2001
Originally posted by Doug Wang: Ilja, CruiseControl sounds cool. Can you please elaborate or offer more resource on this tool? Thanks. [ March 12, 2002: Message edited by: Doug Wang ]
While on the subject of XP: There are a lot of aspects of XP that I find appealing (probably because I already thought along those lines without realizing it had, or would have, a name): the emphasis on testing, constant refactoring, and so on. What I was wondering was if anyone had any actual experience using the two-programmers-at-one-monitor approach, and how that worked out?
I think Rick Salsa post pretty much sums up what I would say... The focus of the book is on automatic testing and continous integration. BTW Cruise Control was not released when we started the book. We will consider it for the second edition.