Systems & Software Talk | |
They Need To Test More...... before doing this: http://news.yahoo.com/s/ap/20091220/ap_on_re_us/us_cell_phone_warnings What exactly does Maine hope to achieve?
How about if the (US) Fed (FCC) simply passes a law requiring all cellular phones to be equipped with GPS, such that if a vehicle is in motion:
I am more than willing to bear the additional expense. I am tired of:
Maine, here is the real danger: http://www.livescience.com/technology/050201_cell_danger.html Certainly there are some people in your legislature who might be more interested in legislation designed to counter real and proven dangers??? If my suggestions are not feasible then at least consider adding the following to the legistlation:
The above would be more progressive as in California-progressive, correct? Maine, if you are thinking the brains of cellular operators might suffer damage because of cellular usage, get out on the highways more often. Brain damage is bountiful. Software DisorderIs it time for the system and software development community to embrace more of, and – accelerate the truth-hiding patterns of the rest of America other than those truth-hiding patterns already common in software development such as the true state of any project? In the slightly paraphrased words George Carlin (may you who left us way too soon and your brilliant mind – rest in peace) "You can't be afraid of words that speak the truth. I don't like words that hide the truth. I don't like words that conceal reality. I don't like euphemisms or euphemistic language. And American English is loaded with euphemisms because Americans have a lot of trouble dealing with reality. Americans have trouble facing the truth, so they invent a kind of a soft language to protect themselves from it. And it gets worse with every generation. For some reason it just keeps getting worse.” More of this brilliant rap can be found here.
I as many of you have always embraced the term “software defect”. But these days it seems as if the term is losing its effectiveness. Rather than spark the intended level of interest and ownership it seems it does more to trigger fear, blame, and shame. Plus, the word “defect” has that hard-hitting and concurrent voiceless velar plosive. It is no wonder that it triggers fear. The blame and shame are just a consequence of that as no one wants to be the proud owner of a defect. And, in the computing industry there is an overabundance of trigger fingers ready to launch blame-ridden projectiles. It is more tolerable to be the owner of a disorder. I have never seen anyone blamed because of a disorder. People, who point out a defect unintentionally or otherwise, promote blame and shame. People hearing of a disorder in others expect that those others are receiving treatment of some order to mitigate or cure disorder. People have compassion for the owner or host of a disorder. (And surprisingly, for what we most think of as a disorder; no one seems to care that the treatment for said disorder may result in death. Pharmaceutical companies know this. That is why their TV commercials have beautiful funereal music. )
Since disorders spark compassion, research and treatment without debate; might it make sense to increase the odds that defective software will receive compassion, trigger research and subsequent treatment? I think so. Therefore I vote that we as a community of test engineering folk push to replace the term software defect with software disorder. Software disorder sounds much softer and kinder than defect. The term software disorder does do a bit to hide the hard-hitting truth – someone f#*cked up. Try the following experiment. Stand in front of a mirror and in a soft falsetto, vocalize the term software defect. Look at your eyes. Upon hearing the term software defect, you have been trained such that your eyes will convey fear. Your bio-target-acquisition driver will dart your eyes as they seek to lock onto the blame target. You also have a look not unlike the OMG-look looking back at you when you ask your teen daughter to wash dishes or not use a cell phone at the dinner table. Now execute the experiment. In a soft falsetto voice utter the term software disorder. Observe! You are soothed. All is well. If you are a male, utter it again while squeezing your scrotal sack. Ahhh.... isn't that nice? Now the world is a better place! Your bio-target-acquisition is paged out of your bio-processor. Compassion is paged in. You expect and know that the disorders will be treated! You are soothed. (Men, if as a result of squeezing your scrotal sack you are feeling aroused as opposed to compassionate, you were not paying attention. Please refocus and try again.)
As a final experiment and concept test-drive do the following. Place yourself for a moment in a defect-handling meeting where the accepted term is now software disorder. People are expecting that the software will be treated. That expectation eliminates a lot of typical arguing and bickering! Take it a bit further. Perhaps the software has so many disorders that it simply needs to die. You may be able to expedite that certainty by taking a boom box into that meeting. Put on some funereal music just like the pharmaceutical companies use in their TV commercials. Ahhhh… the world is a much better place. People in that meeting are mellow and accommodating. Blame is absent and therefore shame is on hiatus. All are willing to get the software into either treatment or interment.
Join me in promoting the term software disorder. Let us know when you file your first Software Disorder Report (SDR). Software Disorder Report Number: SDR-000000001 Title: Computer brand drop-down list exhibits disorder. Description: The drop down list is disorderly in that the items are disordered. Recommend checking the alphabetizing sort algorithm in order to restore order where there is currently disorder. Steps to Reproduce: Go to main page. Click Show Computer Brands Tab. Locate and click/pull down the Computer brand drop-down list. Observe disorder in that the list is not in alphabetical order by manufacturer. Software App Version: TBA Test Case: TBA
Software Testing Misunderstandings and Disrespect update. Part II is almost complete and will be released within 3 weeks of this entry. Are Rock, Paper, Scissors-based Decisions Obsolete?Do computing industry personnel really use the Rock, Paper, Scissors (RPS) method to make decisions project management, design, development, testing, or releases? Should they not be using the BFD method? Before you go there, "BFD" means Binary Finger Display. There actually is a RPS Society. I think the computing industry needs a BFD Society. I think the BFD game should be played by simply using one hand to flash fingers and/or the thumb. A finger or thumb not extended on the count of three means a zero. A finger or thumb extended on the count of three means a one. General Rules/Qualifications:
The rules:
Cure for ATDDDoes your automation test suite suffer from Automated Test Deficit Disorder (ATDD)? Are your automated tests often ridiculed because they:
You are not alone and there is hope. Retryalia tm and Recoveratin tm in combination may be right for treating ATDD symptoms in your automation test suite, providing you adaptability and recoverability benefits. Retryalia tm in 187 of 200 computerinical trials proved effective at countering the effects of object-focus-loss and windows-fixation, thus reducing the rate of incomplete tasks. Retryalia tm should not be used in treating automated tests directed at applications using __VIEWSTATES, as network death is certain. Recoveratin tm in 196 of 200 computerinical trials proved effective at countering null or useless automation test results for an application-under-test (AUT) borne of hasty and otherwise sloppy and inflated ego-driven application design and development practices. Specifically in these situations Recoveratin tm proved effective at countering both blue-screen hell fears and gooey mess. Speak to your management and recommend organization-wide training before using Recoveratin tm in your automation test suite. Recoveratin tm in your automation test suite will auto-file defect reports and reject applications not thoroughly development- tested and prematurely thrown over the wall. In these situations Recoveratin will profile AUT source code and via email automatically broadcast profiling results, and - recommend source code changes to your entire organization. Also in these situations Recoveratin tm has been known to locate and publicize source code on how-not-to project-manage, how-not-to-design and how-not-to-develop application websites. Recoveratin tm computerinical trials showed no added benefit for automated tests in organizations which promote sound project management and application design and development practices. What are the causes of ATDD or Automated Test Deficit Disorder? ATDD in most cases is a mere but costly misguided perception leading to the belief that the automated tests are at fault and incorrect. ATDD is usually triggered by poor organizational practices. Those poor practices drive misconceptions of automated testing. Of the many delusions suffered by management, one will find silver-bullet perceptions, notions that it-is-just-record-and-playback, and any-monkey-can-do-it mindsets. ATDD is also caused by unskilled automation-tool implementers. In situations where ATDD is the result of deceptive and unskilled automators, Recoveratin will simply lock out the test-automator and to the test-automator, recommend a new job matching the would-be automator’s skills-of-deception, such as bonus-administrator at AIG. In those very common situations where management delusions are bountiful and the AUT is clearly one which commands very low-levels of organizational pride, another benefit of Recoveratin tm is triggered. In those situations Recoveratin tm is known to change perceptions and counter delusions. Recoveratin tm will automatically administer Boostaplatformalis tm. Boostaplatformalis tm is intended to enable, optimize and showcase deserving robust automation test suites and redirect the undue blame-driven scrutiny to the root cause – the AUT and the processes and practices (or lack thereof) which produced the application. With a periodic injection of Boostaplatformalis tm your automation test suite will perform effortlessly and not be the subject of undeserving scrutiny. How does Boostaplatformalis tm work? Boostaplatformalis tm gathers intelligence about your entire organization and its network topology. Boostaplatformalis tm will use this intelligence to adapt itself and optimize its execution speed and programmatical correctness such that the AUT deficiencies and issues are always obvious. What are some ways in which Boostaplatformalis tm works? Boostaplatformalis tm with its network topology intelligence, will automatically provision and order maximum bandwidth for itself – charging back to R&D. Boostaplatformalis tm will also order upgrades to network appliances and automatically create appropriate emails, service requests and work orders along the way. Boostaplatformalis tm will also order new automation test suite hosts to replace non-Mac hosts, or upgrades to existing hosts in the interest of eliminating automation test platform host security and performance issues, again charging back to R&D. If the new Mac automation test hosts have to be backordered, Boostaplatformalis tm will order Mac logos to serve as a placebo for the existing automation test platform hosts until Mac backorders can be filled.
Let your automation test suite stand tall, proud, and erect. Order your Boostaplatformalis tm today!
(Mac is a product of Apple, Inc.) The Collapse of JakeBrake Investments, Inc.?JakeBrake Investments, Inc. (JBII) has been in business for 12 years. JBII has a proven track record grooved with sound business management practices. JBII co-founders have a proven bi-partisan relationship. Co-founders JakeBrake and Mrs. JakeBrake realized long ago that a successful business such as JBII requires honesty, integrity, properly aimed ideals, solid work ethic, and - is devoid of greed. At JBII you will not find the co-founders:
You will not find Co-founders JakeBrake and Mrs. JakeBrake:
JBII Co-founders JakeBrake and Mrs. JakeBrake cannot Uh Ford such behaviors.
JakeBrake and Mrs. JakeBrake will always maintain their modest, non-flaunting-of-excessive-capitalistic-success, low-frontage-cost, non-sky-reaching, non-marbled, non-glass-walled, non-lobby-pianist-equipped, non-executive-parking-stall-equipped corporate headquarters in the USA, and - do their American-citizen tax-paying duties – on time with the full-amount owed.
Times have certainly changed. You will now find JBII on the brink of collapse as JBII co-founders JakeBrake and Mrs. JakeBrake scramble to aid in the rescue of large corporations who cannot repeat the success of two non-MBA-equipped, non-law-degree-equipped individuals.
Mrs. and Mr. JakeBrake are certainly not dancing the Freddie, nor are they taking American tax-payer $$ to fund research intended to understand the differences between the poop of the red and the poop of the gray squirrel; with an option for additional funding to determine how the poop of an albino squirrel contributes to global warming. { Last Page } { Page 1 of 3 } { Next Page } |
About MeMy Profile Archives Friends My Photo Album LinksCorey GoldbergEffective Testing? Bj Rollison I.M. Testy Blog Alan Page: Software Testing & Rants Dmitry's LoadRunner and QTP Blog Veterans History Project Air Traffic Control Watch Music Making Fun My home 1972-1975 CategoriesFunctional TestingPerformance Horror Development Performance Testing General Tools Tips Warped Humor LoadRunner Tips and Tricks Recent EntriesThey Need To Test More...Software Disorder LoadRunner (tm) & RTE 4 Func/Regr LoadRunner (tm) Random Think time Function Are Rock, Paper, Scissors-based Decisions Obsolete? FriendsLauraScharpphilk10 richardw100 aalhait jimhazen strazzerj Lynnem bru EklecticTester jgottlieb leakybrain michaeljf prainbow rajeshmathur rstens Yury zeeslo whollymindless SyndicationRSS Site Feed |