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)
SCJP 1.4, SCWCD 1.4, SCBCD 1.3, SCJA<br /> <br />blog: <a href="http://jroller.com/page/rharianto" target="_blank" rel="nofollow">http://jroller.com/page/rharianto</a>
Originally posted by rathi ji:
Hi,
I feel, in developer point of view, process is not important, his/her whole and sole work is do coding within time.
So does this book is useful for developer??
Thanks.
sole work is do coding within time
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>
Originally posted by rathi ji:
Hi,
I feel, in developer point of view, process is not important, his/her whole and sole work is do coding within time.
So does this book is useful for developer??
Thanks.
Not even remotely accurate. Do you share the code with anyone? Do you build it? Do you test it? Do you ship it? How do you know what you are working on now? Next? How do you tell your boss what you did last week?
Other shops use shared disks to store their source code instead having a source code management system. They wasted a lot of time figuring out whose code overwrote someone else's.
Having some basic process gives you a framework for interacting with other developers, a reliable way to track bugs, build your product, test your product, etc.
Sorry but I am not getting connection of this with software developement process...
SCJP 1.4, SCWCD 1.4, SCBCD 1.3, SCJA<br /> <br />blog: <a href="http://jroller.com/page/rharianto" target="_blank" rel="nofollow">http://jroller.com/page/rharianto</a>
Originally posted by rathi ji:
I think that is different issue, these basic tools every organization should have, whether they are following any process or not...
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>
Originally posted by Rudy Harianto:
rathi,
I assume that you are a programer..
So how could you said that? you didn't do a unit testing? and worst.. you don't even know what're you doing???
Originally posted by rathi ji:
I think I got it right now, Software processes (any one XP, UP etc) tells us to follow certain processes or rules that helps to make standard product.
Use version control tool is one example of that.
[ August 04, 2005: Message edited by: rathi ji ]
Dogma does not mean the absence of thought, but the end of thought.
Gilbert Keith Chesterton (1874�1936)
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>
Originally posted by Jared Richardson:
Process is about creating code in a repeatable way. It sounds like you have a more heavyweight thing in mind. Process should be (in my opinion) just enough to guide the developers, not slow them down.
I've been in shops where there was no process and no-one could build the product except for the one person. They didn't have a build process. So when that one person left, they couldn't build the product. They didn't save much time by not automating the build and they couldn't reliably build the product even with their superstar. A simple Ant script gave everyone the ability to build (and run) the product.
Other shops use shared disks to store their source code instead having a source code management system. They wasted a lot of time figuring out whose code overwrote someone else's.
Having some basic process gives you a framework for interacting with other developers, a reliable way to track bugs, build your product, test your product, etc.
Not even remotely accurate. Do you share the code with anyone? Do you build it? Do you test it? Do you ship it? How do you know what you are working on now? Next? How do you tell your boss what you did last week?
All process.
Unluckily, boss do not care about the process but the output i.e. your software should be function well. Good process adopted but malfunction software developed will let your boss continue to blame you.
Even process helps you to reduce the problems of multi-developer, some problems still exist. For example, each programmer/developer writes codes in different style in the same program, program or system is still difficult to build, trace or debug.
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>
Originally posted by Jared Richardson:
First, the boss who cares about how well your software functions should care about the process you use to build it. The two are connected I think.
Second, if you are developing malfunctioning software, you need a better process! A good process will make allowances for testing, code reviews, and other practices that will help minimize bugs.
Very true. The idea is to adopt the process that helps you the most. It sounds like you haven't found a process that fits you yet.
I must say that most people I know that don't have a good software process think that developing software is much harder that those who have mastered an effective software process.
If you were a carpenter and you never learned how to use your tools, you might think building furniture is pretty hard... and it would be! But building furniture (and software) can be easier, maybe even fun, if you know how to use your tools!
Also, just my opinion! Could be wrong too!
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)
Originally posted by Tony William:
My view is that Process cannot make your a carpenter over the night. Having said that, it should help to build up your the project management skill, give you something to follow, and review the status (so that you know where you are or how far you are from the destination).
For the team, it helps to improve the team efficiency, how the members communicate etc.
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>
Originally posted by Jared Richardson:
Agreed. People don't master tools or design patterns overnight... there are no silver bullets. Anyone who promises differently is selling snake oil.
Rudy, don't be rude man.
I never thought that these unit testing, reviews etc are the part of any process.
SCJP 1.4, SCWCD 1.4, SCBCD 1.3, SCJA<br /> <br />blog: <a href="http://jroller.com/page/rharianto" target="_blank" rel="nofollow">http://jroller.com/page/rharianto</a>
Originally posted by Peter Sin:
Unluckily, boss do not care about the process but the output i.e. your software should be function well.
Good process adopted but malfunction software developed will let your boss continue to blame you.
Even process helps you to reduce the problems of multi-developer, some problems still exist. For example, each programmer/developer writes codes in different style in the same program, program or system is still difficult to build, trace or debug.
Software development is a complex issue.
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
Originally posted by rathi ji:
I think I got it right now, Software processes (any one XP, UP etc) tells us to follow certain processes or rules that helps to make standard product.
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
Originally posted by Peter Sin:
To conclude: What are the benefits of "Process" ? Please refers to "Ship It! A Practical Guide to Successful Software Projects". I just want to test the author debate technique.
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>