"He also claims that the King James Version of the Bible is God's Word."
What is it with all of the versions of the bible?
Reminds me of the joke: A pastors daughter was watching her father writing the sermon for the next day. She asked "How do you know what to write?" He says "God tells me." She asks "Why do you keep erasing things?"
Heh, I played D&D weekly when that came out. When asked what I thought about it, all I would say was that if a player was significantly unbalanced, it could possibly happen.
I was really fortunate to be able to hire some extremely qualified staff in the last few years. Each of them have brought insights which can only be gained through time. They have prevented mistakes being made or propogated by being able to recognize the pitfalls.
The only difficulty I have is keeping them motivated in the face of roadblocks and protecting them from the high level of beaurocracy.
That is all well and good. I guess I should have phrased the question as: "Why did "liquid hydrogen could seep into those voids" in the first place?".
I know that, in hindsight, it is easy to find flaws.
If the gluing of the foam is inexact and the potential of liquid hydrogen leaking can be high and even the sun warming the foam imposes a level of risk, what are the mitigating factors for these risks?
Think about what you first used Windows (or DOS, if you're old enough). What did you know then. How long did it take you to learn everything you know about Windows?
Why should you think that you should be able navigate around Linux with less exposure? Is it that because you know Microsoft's version of "computing", you know computers?
I know only a little about linux because I'm still learning. If I look at how long I've been in the MS environment and what I know now, I've got a few years until I am fully proficient with Linux. I am willing to give myself, and Linux, the latitude of tha learning curve.
1) Winrunner is less expensive in the initial purchase. Robot has a very low cost on the upgrade side in comparison. (There are a lot of upgrade costs to Mercury's.NET solution. It is a whole new product.)
2) "Thick" developers need to learn new languages to remain current so why should it be any different for professional testers?
Hint: Know the intricasies for a professional function before you use a derogatory term.
Certified Analysits should be able to work from well written specifications. You do provide complete and acurate TDS (Technical Design Specifications) for architectural details and FDS (Functional Design Specifications) for system operation, don't you?
When I first started in the testing profession, I coined the phrase "the over the baffle testing". The developers would literally pass a diskette with a recompiled component over the baffle and say "Here, try this". We were then expected to reinstall the component and see if it fixed the problem.
I agree with most of what you say, except for the "boring" part. The Mythical Man month is still relevant today. Just as there is a creative rush in building a working software system out of the ether, there is an equal rush and creative element is software testing.
Testers and developers think differently but have the same purpose in mind. At the end of the day, both want the best possible product to be delivered.
I suggest signing up to StickyMinds as a good place to start.
Automation is only good for stable applications. Elements that are going to or may be further developed will negate any benefits achievable from test automation. The "Industry Standard" tools such as Mercury's, Compuware's or IBM Rational's test automation suites require a significant amount of coding effort themselves. "Simple" design changes can blow away weeks of scripting.
Automating stable components is the best way to go. As each component is completed and stable it can be automated for regression testing. Adding the completed component scripts to your test harness will flesh out your test suite.
The above mentioned tools are very expensive but very effective. I'm looking forward to the subproject from The Eclipse Foundation the number of big name contributor is quite encouraging.
If you like to code and have reliable and creative testers available, join up.
Slashdot is tested every day. Bugs are reported publicly, as evidenced by your post. The only difference between this and what I do for a living (enterprise web application testing) is that the developers don't listen or don't know how to fix things.
Slashdot Mirror
"He also claims that the King James Version of the Bible is God's Word."
What is it with all of the versions of the bible?
Reminds me of the joke:
A pastors daughter was watching her father writing the sermon for the next day.
She asked "How do you know what to write?"
He says "God tells me."
She asks "Why do you keep erasing things?"
Heh, I played D&D weekly when that came out.
When asked what I thought about it, all I would say was that if a player was significantly unbalanced, it could possibly happen.
Why do the words "Specification" and "Speculation" sound so similar?
Cripes.
I've seen it worse than that.
I've seen people so fresh out of tech "training" be hired and then given the courses to GET the bloody MCSE!
Makes me ill just thinking about it.
I was really fortunate to be able to hire some extremely qualified staff in the last few years.
Each of them have brought insights which can only be gained through time.
They have prevented mistakes being made or propogated by being able to recognize the pitfalls.
The only difficulty I have is keeping them motivated in the face of roadblocks and protecting them from the high level of beaurocracy.
You see, we're a Gov't tech shop.
So, the P2P users who state "Share or you will be banned" are inciting infringment as well as violating copyright?
Try w3schools
Heh, maybe their next step will be a new marketing slogan: "Get Real!"
That should have been "10.24 kilobytes"
Sorry, but this is a nit begging to be picked.
1/100 megabyte=1.28 kilobytes.
60 ????
70 Profit!
--
excusez-moi
That is all well and good.
I guess I should have phrased the question as: "Why did "liquid hydrogen could seep into those voids" in the first place?".
I know that, in hindsight, it is easy to find flaws.
If the gluing of the foam is inexact and the potential of liquid hydrogen leaking can be high and even the sun warming the foam imposes a level of risk, what are the mitigating factors for these risks?
What I'm curious about is: How "liquid hydrogen could seep into those voids" in the first place?
How about "Sonny""?
No, no, no.
Don't protect that "tarbox"!
$ wget --mirror katie.com
201-463-8663 (her U.S. cell phone
I wonder if she has text messaging?
It figures. Someone makes a reply that is intellegent and and telling when I was going to say "MOD PARENT UP!"
I just gave my dog a linux machine. He lifted his leg at it the same as he did with XP.
Of course his idea of an "intuitive" interface is a bit more simple than mine.
His goes like this: "If you can't eat it or screw it, piss on it."
Think about what you first used Windows (or DOS, if you're old enough).
What did you know then. How long did it take you to learn everything you know about Windows?
Why should you think that you should be able navigate around Linux with less exposure? Is it that because you know Microsoft's version of "computing", you know computers?
I know only a little about linux because I'm still learning. If I look at how long I've been in the MS environment and what I know now, I've got a few years until I am fully proficient with Linux.
I am willing to give myself, and Linux, the latitude of tha learning curve.
1) Winrunner is less expensive in the initial purchase. Robot has a very low cost on the upgrade side in comparison. (There are a lot of upgrade costs to Mercury's .NET solution. It is a whole new product.)
2) "Thick" developers need to learn new languages to remain current so why should it be any different for professional testers?
Hint: Know the intricasies for a professional function before you use a derogatory term.
Certified Analysits should be able to work from well written specifications.
You do provide complete and acurate TDS (Technical Design Specifications) for architectural details and FDS (Functional Design Specifications) for system operation, don't you?
When I first started in the testing profession, I coined the phrase "the over the baffle testing".
The developers would literally pass a diskette with a recompiled component over the baffle and say "Here, try this".
We were then expected to reinstall the component and see if it fixed the problem.
I agree with most of what you say, except for the "boring" part. The Mythical Man month is still relevant today.
Just as there is a creative rush in building a working software system out of the ether, there is an equal rush and creative element is software testing.
Testers and developers think differently but have the same purpose in mind. At the end of the day, both want the best possible product to be delivered.
I suggest signing up to StickyMinds as a good place to start.
Automation is only good for stable applications.
Elements that are going to or may be further developed will negate any benefits achievable from test automation.
The "Industry Standard" tools such as Mercury's, Compuware's or IBM Rational's test automation suites require a significant amount of coding effort themselves.
"Simple" design changes can blow away weeks of scripting.
Automating stable components is the best way to go. As each component is completed and stable it can be automated for regression testing. Adding the completed component scripts to your test harness will flesh out your test suite.
The above mentioned tools are very expensive but very effective.
I'm looking forward to the subproject from The Eclipse Foundation the number of big name contributor is quite encouraging.
If you like to code and have reliable and creative testers available, join up.
Slashdot is tested every day.
Bugs are reported publicly, as evidenced by your post.
The only difference between this and what I do for a living (enterprise web application testing) is that the developers don't listen or don't know how to fix things.
WAIT A MINUTE: There is NO difference.