DigillRev should have ignored the DMCA just based on the fact that it states something about a trademark. They didn't even bother to read the intro on the WikiPedia page on the DMCA or they would have understood there's no way this letter means anything.
Thanks, I prefer communism over the patriot act anyday!
I did that for quite a while, or maybe you are to stupid to remember the USSR?? I prefer that over the freaking Patriot act any day, cause then at least I know who is watching me and when I am liable to be picked up by the fucking gestapo (oh! sorry, they are called FBI these days right?)
I agree these practices are not quite nice, but come on, look at the EULA you sign with just about any kind of service provider online.
But did any of you ever stop to think about the difference between having and not having this kind of agreement?? Cause if you ask me, it doesn't make a difference. Have a look at the Patriot Act, that basically states that the US government doesn't care about your rights, they reserver the right to shove just about anyhing up your behind without giving you any notice at all!
THe way I always work is simply using Bugzilla (make it the homepage on all machines for all I care!) and have the bugmaster run through all issues at least once a day, he/she can than decide who's gonna get the bugs in order to fix em and also check for dupes.
Bugzilla is by far easiest and cheapest to implement in any environment. It is free and webbased and moreover, it is very easy to customize it. If your management doesn't want to spend too much money on quality it is their problem, but keeping your work fun and somewhat easy is your own.
So just implement a solution and after a couple of weeks show the improved results to management.
Another thing to improve stuff is by implementing UnitTesting. Have developers write UnitTests before writing any code and run your unittests with every build (Contiuous Integration is Heaven for testers!!) If Unit tests fail, it is no use testing software by hand and you can start kicking developers around.
Sounds to me as a very very expensive way. THe way I always work is simply using Bugzilla (make it the homepage on all machines for all I care!) and have the bugmaster run through all issues at least once a day, he/she can than decide who's gonna get the bugs in order to fix em and also check for dupes.
Bugzilla is by far easiest and cheapest to implement in any environment. It is free and webbased and moreover, it is very easy to customize it.
If your management doesn't want to spend too much money on quality it is their problem, but keeping your work fun and somewhat easy is your own. So just implement a solution and after a couple of weeks show the improved results to management.
Another thing to improve stuff is by implementing UnitTesting. Have developers write UnitTests before writing any code and run your unittests with every build (Contiuous Integration is Heaven for testers!!) If Unit tests fail, it is no use testing software by hand and you can start kicking developers around.
Additional to all this, if you are looking for a bit of a student experience but cannot go to the US (or do not want to go there, that was my problem) there are many highly regarded Universities in Europe as well. I probably is worth your while to try to go to an esteemed university somewhere in Europe instead of doing an online one. One of the many benefits I found is that it really boosts your network of colleagues over the world which may come in handy in many ways (like finding a new job and helping you out with problems during your thesis etc.) So I would definitely go for a real university instead of a virtual one.
Anything is easier than freakin' WebSphere!
I don't understand the choice made here, why on earth use an evaluation licence of websphere i fyou can use a full version of JBoss! ?
If you have questions about either one, or of course about some hard core testing, let me know (mail plz).
I am always willing to help out ppl.
Good luck with it all! and remember:
We, in a software developing company, ship latent bugs at a rate in the range of 0.2 to 20 per 1000 delivered source instructions.
Ok, last piece of advise from my side than.
Do you guys use Unit testing ? Avoids a lot of problems as wel. and since you only have to developers, try working in some XP ideas. That really boosts the quality of work if you do it right!
I, along with a developer, introduced our former company to XP and our bug counts went down and the productivity went sky high!
so try it, have a look at: http://jibe.sourceforge.org and http://XProgramming.org
Jibe might help you forward somewhat... is one of our opensource projects, started it some time ago and we use it extensively, unfortunately only one active external developer at the moment though...:(
I was just 'pullin your leg'.
I know and understand your problem. We usually have the same kind of troubles here at my new company. Our CEO keeps changing his mind along the projects. Really annoying and makes it really hard for me as a tester to plan ahead, let alone for dev.
But like I said. The only title I know as being anything worth while is Design Patterns.
But trust me when I say that having a third party, like an experienced tester, review the designs already takes out quite some problems.
If you have testers at your CO Use 'em and abuse em! Test early and test often as XP says!
So have them do some early stage reviews for you...
If you believe your code can be 99.9% stable if you do it right the first time I'd have to say you are somewhat naive, also if your assumption is true, why do you still need books about a design process if you already think you can do it?
Invite an experienced tester to test your code full-scale (so design-review, code review and all level testing) and you may find out where some flaws in your design are.
Since I don't like coding I cannot help you with a title for a good design process. Unless of course you don't have 'Design Patterns' yet. good book, helped dev at my former company a lot in gaining somewhat stable code at quite an early stage in the development cycle...
It is a nice option to use large scale bete testers, but you have to make sure your testers know what they are doing.
Take 500 morrons and tell them to test an OS does'n make a good army of beta testers, like you said yourself, look at microshaft to find out how NOT to do it.
Testers need some sort of training (at least I have had great benefits off it, both for myself and for testers working for me)and to train an army will take a lot of time and even more of your resources away.
So don't just take an army of volunteers, take a small army of experienced tester (same as the difference between an army and SAS)
as XP says...
The prupose of testing a program is to find problems in it, not to verify that a program runs correctly. A test that reveals a problem is a success. A test that did not reveal a problem is a waste of time.
However, if the design has flaws, your program will be sure to have too many bugs for your own good.
Ever tried reviewing the designs with an experienced tester? They might find some nice flaws and possible bugs even before you have written a single line of code.
Slashdot Mirror
DigillRev should have ignored the DMCA just based on the fact that it states something about a trademark. They didn't even bother to read the intro on the WikiPedia page on the DMCA or they would have understood there's no way this letter means anything.
Thanks, I prefer communism over the patriot act anyday! I did that for quite a while, or maybe you are to stupid to remember the USSR?? I prefer that over the freaking Patriot act any day, cause then at least I know who is watching me and when I am liable to be picked up by the fucking gestapo (oh! sorry, they are called FBI these days right?)
I agree these practices are not quite nice, but come on, look at the EULA you sign with just about any kind of service provider online. But did any of you ever stop to think about the difference between having and not having this kind of agreement?? Cause if you ask me, it doesn't make a difference. Have a look at the Patriot Act, that basically states that the US government doesn't care about your rights, they reserver the right to shove just about anyhing up your behind without giving you any notice at all!
THe way I always work is simply using Bugzilla (make it the homepage on all machines for all I care!) and have the bugmaster run through all issues at least once a day, he/she can than decide who's gonna get the bugs in order to fix em and also check for dupes.
Bugzilla is by far easiest and cheapest to implement in any environment. It is free and webbased and moreover, it is very easy to customize it. If your management doesn't want to spend too much money on quality it is their problem, but keeping your work fun and somewhat easy is your own.
So just implement a solution and after a couple of weeks show the improved results to management.
Another thing to improve stuff is by implementing UnitTesting. Have developers write UnitTests before writing any code and run your unittests with every build (Contiuous Integration is Heaven for testers!!)
If Unit tests fail, it is no use testing software by hand and you can start kicking developers around.
Sounds to me as a very very expensive way. THe way I always work is simply using Bugzilla (make it the homepage on all machines for all I care!) and have the bugmaster run through all issues at least once a day, he/she can than decide who's gonna get the bugs in order to fix em and also check for dupes. Bugzilla is by far easiest and cheapest to implement in any environment. It is free and webbased and moreover, it is very easy to customize it. If your management doesn't want to spend too much money on quality it is their problem, but keeping your work fun and somewhat easy is your own. So just implement a solution and after a couple of weeks show the improved results to management. Another thing to improve stuff is by implementing UnitTesting. Have developers write UnitTests before writing any code and run your unittests with every build (Contiuous Integration is Heaven for testers!!) If Unit tests fail, it is no use testing software by hand and you can start kicking developers around.
Additional to all this, if you are looking for a bit of a student experience but cannot go to the US (or do not want to go there, that was my problem) there are many highly regarded Universities in Europe as well. I probably is worth your while to try to go to an esteemed university somewhere in Europe instead of doing an online one.
One of the many benefits I found is that it really boosts your network of colleagues over the world which may come in handy in many ways (like finding a new job and helping you out with problems during your thesis etc.)
So I would definitely go for a real university instead of a virtual one.
Anything is easier than freakin' WebSphere! I don't understand the choice made here, why on earth use an evaluation licence of websphere i fyou can use a full version of JBoss! ?
If you have questions about either one, or of course about some hard core testing, let me know (mail plz). I am always willing to help out ppl. Good luck with it all! and remember: We, in a software developing company, ship latent bugs at a rate in the range of 0.2 to 20 per 1000 delivered source instructions.
Ok, last piece of advise from my side than. Do you guys use Unit testing ? Avoids a lot of problems as wel. and since you only have to developers, try working in some XP ideas. That really boosts the quality of work if you do it right! I, along with a developer, introduced our former company to XP and our bug counts went down and the productivity went sky high! so try it, have a look at: http://jibe.sourceforge.org and http://XProgramming.org Jibe might help you forward somewhat... is one of our opensource projects, started it some time ago and we use it extensively, unfortunately only one active external developer at the moment though... :(
I was just 'pullin your leg'. I know and understand your problem. We usually have the same kind of troubles here at my new company. Our CEO keeps changing his mind along the projects. Really annoying and makes it really hard for me as a tester to plan ahead, let alone for dev. But like I said. The only title I know as being anything worth while is Design Patterns. But trust me when I say that having a third party, like an experienced tester, review the designs already takes out quite some problems. If you have testers at your CO Use 'em and abuse em! Test early and test often as XP says! So have them do some early stage reviews for you...
If you believe your code can be 99.9% stable if you do it right the first time I'd have to say you are somewhat naive, also if your assumption is true, why do you still need books about a design process if you already think you can do it? Invite an experienced tester to test your code full-scale (so design-review, code review and all level testing) and you may find out where some flaws in your design are. Since I don't like coding I cannot help you with a title for a good design process. Unless of course you don't have 'Design Patterns' yet. good book, helped dev at my former company a lot in gaining somewhat stable code at quite an early stage in the development cycle...
How about Testing Computer Software?? However I have to say that 'Rapid Testing' did me more good, as did 'Lessons learned in software testing'
It is a nice option to use large scale bete testers, but you have to make sure your testers know what they are doing. Take 500 morrons and tell them to test an OS does'n make a good army of beta testers, like you said yourself, look at microshaft to find out how NOT to do it. Testers need some sort of training (at least I have had great benefits off it, both for myself and for testers working for me)and to train an army will take a lot of time and even more of your resources away. So don't just take an army of volunteers, take a small army of experienced tester (same as the difference between an army and SAS)
as XP says... The prupose of testing a program is to find problems in it, not to verify that a program runs correctly. A test that reveals a problem is a success. A test that did not reveal a problem is a waste of time. However, if the design has flaws, your program will be sure to have too many bugs for your own good. Ever tried reviewing the designs with an experienced tester? They might find some nice flaws and possible bugs even before you have written a single line of code.