WQTS 10

WQTS is ten posts old! To commemorate this milestone–one post per finger (for most of us)–I’ve got an unusually large selection of items for us to shake our heads in despair over.

13-1
Looks like a fairly standard calendar page, doesn’t it? Take a closer look at the middle of the month. Maybe I’m an old fogy, not up on the latest* in matters calendrical, but I still prefer my dates to follow the pattern “18, 19, 20”.

* OK, almost the latest; this is actually a calendar from 2015.

It’s easy to see how this happened, though I would have expected dates to be computer-generated, rather than hand-keyed. But how did nobody notice before the company printed and shipped thousands of these? I’m guessing that a “boundary” test went awry: somebody confirmed that the first was a Wednesday, the thirty-first was a Friday, and assumed that meant all of the dates in between had to be correct. In short, an incorrect choice of tests.

13-2
No, I’m not talking about “remodelation” or the lack of capitalization. This is one where QA was lacking in the development of the specifications. Another pair of eyes might have caught the omission of any indication of what name to look for on Facebook. I checked: it’s not the name of the restaurant.

13-3
“Code hoping”? Ouch! This is from the packaging for a device that’s supposed to let you start your car remotely if you were too cheap to buy the manufacturer’s remote-start option. Let’s hope that the QA folks who tested the security features that ensure nobody can start your car without the fob are not the same ones who reviewed the package copy.

Oh, who am I trying to kid? Chances are neither the package nor the code were QAed. After all, that’s what advertising writers and software developers are for, right?

13-4
Ignore the fact that it’s a pretzel covered in some chocolate-like substance (bleah!). Ignore the fact that nobody at Olivier’s Candies Ltd. can spell “chocolatey,” since my dictionary swears this is an accepted variant* and more importantly, what they meant was “chocolate-” (yes, with a hyphen). But didn’t anybody realize that since these are inanimate objects, they cannot be patriots? Please, people, use your adjectives! “Patriotic Chocolate-Covered Pretzel” Oh, and you might want to add an “s” at the end, since I can clearly see there are at least six per package.

* At least they didn’t spell it “chocolatty”.

Again, a case where there clearly wasn’t any QA done at all. Guys, “copywriter” and “copy editor” are NOT synonyms!

13-5
One more case where a copy editor should have been engaged. Not just for “bakering,” though there is that. But “eaten out of hand” does not mean what the sign-maker thought. Clearly, she* thought it meant to eat something you’re holding. But “out of hand” is actually an idiomatic** expression meaning “out of control” or “immediately, without thinking.”

* Pronoun chosen by coin flip.

** An expression that doesn’t mean what a literal interpretation of the individual words would suggest.

I’ve cropped the picture, so you can’t see the apples, but they’re sitting very peacefully in the bin, hence, not out of control. They also look ripe, but not overripe, so eating them immediately doesn’t seem warranted. Perhaps the intention was to suggest that they should be eaten thoughtlessly. But thoughtless eating is generally the province of less nutritious fare–Patriot Chocolaty Covered Pretzels, perhaps.

Well, whatever. Just remember: No matter what happens,
13-6

WQTS 9.1

My apologies if this spoils your plans for the week. Despite what I said Thursday, there is a post today. I found this little error too amusing to not share, but didn’t want to sit on it until after my vacation.

31-1Many newspapers’ sports sections, including the Chron’s, include a listing of player moves–trades, promotions, suspensions, and so on–tucked away in the back. These are not exactly a fount of stunning revelations. The only people who look at the Transactions report are obsessed geeks, and we usually know all the details before they make it into the paper.

Just imagine my surprise, then, when I found this blockbuster news hidden away in Transactions (Thursday, 5/26/2016 for anyone who wants to confirm that I haven’t doctored the image.)

Apparently the Seattle Seahawks have changed sports, moving from football to baseball.

I can’t decide which is more surprising: that this happened mid-season, or that the ‘Hawks will be playing in the American League, going head-to-head with the Mariners!

I presume there will be a follow-up item in Friday’s paper listing the roster moves necessary to get the 53-man active roster down to MLB’s 40-man limit.

It should be a very interesting experiment in roster construction. Football teams, by and large, don’t have more than a handful of players capable of throwing the ball accurately enough to pitch. That’s going to make for a very skimpy bullpen.

Receivers and kick returners ought to be able to make the transition to the outfield, but stocking the infield may be a challenge. On the other hand, finding players with the traditional catcher’s build shouldn’t be any trouble at all–and while there may be an elevated number of wild pitches (see note above regarding pitchers), I don’t think there will be a whole lot of passed balls. And those new catchers are going to love MLB’s anti-concussion rules.

And talk about offense! Nearly every player on the roster is going to make David Ortiz look undersized. When they make contact and get their bodies into it, well, let’s just say that I expect this team to hit record numbers of 450-foot home runs.

Perhaps the most intriguing aspect of this move, though, is the question of how to lay out a diamond in CenturyLink Field. Looking at the current seating chart suggests that the longest dimension is 420 feet. That’s fine for dead center field, but the fences in left and right are going to be a hell of a lot closer to the plate–maybe 255 feet down the lines. Given the likely quality of the pitching, that’s never going to work. Heck, that wouldn’t work even if the rotation included Felix Hernandez, Madison Bumgarner, and Clayton Kershaw. Some seats are going to have to get ripped out, and that’s going to hurt revenue.

Still, as I said, an interesting experiment. Stay tuned for updates!

WQTS 09

A baseball-related Who QAed This Shit? It’s as American as an apple-and-hotdog pie*!

* Bleah! Kids, don’t try this at home.

Allow me to start by filling in the background for those of you who can’t recall the last time you watched a televised baseball game.

Typically, when a relief pitcher comes into the game, the broadcaster will overlay an box on the screen to provide viewers with some background on the pitcher. This is what’s so delightfully referred to as a “value add” because it immeasurably enriches your viewing experience.

But I digress.

Every network has its own version of the overlay with a layout designed to showcase the information they believe their viewers desperately crave. Here, for instance, is what you get on Comcast SportsNet California, broadcast home of the Oakland Athletics:
24-1

Pretty straightforward. Name, number, team (in case you’ve forgotten which game you’re watching, I suppose), a handful of basic statistics about his performance so far this year*, and, down at the bottom, a single yellow bullet point.

* Occasionally, especially at the beginning of the season, you’ll get last year’s stats or career numbers.

And it all works well–until it doesn’t, as happened last week in a game between the As and the Yankees:
24-2

That’s an interesting bullet point, isn’t it?

Apparently the UI for creating the overlay prefills the data entry field with a helpful reminder. In haste to get the overlay on viewers’ screens, the stats person didn’t supply a bullet point. Oops.

Now, I’m not suggesting that our unfortunate stats person is responsible for a QA failure. That’s not his or her job.

No, the failure is on some anonymous QA engineer at whatever video software house CSNCA hired to create the overlay code. Either nobody ever tested this scenario, or the bug was prioritized too low.

In all seriousness, however, it’s the software design that’s at fault. The overlay software must* do one of two things:

  • Prevent the user from pressing the “Display to 29,000 Viewers**” button if the default text is still in the field.
  • Treat the default text in the same way it handles an empty field.

* I’m using the word in the specification sense. “May” is optional, “must” is not.

** Yes, the As’ TV ratings suck. (That number comes from an article in Forbes last year.)

QA for the Yankees’ YES network, by the way, does the job right:
24-3

WQTS 08

Three food-related QA failures today.

Last weekend, Maggie and I went to “Pints for Paws,” a benefit for Berkeley Humane. Naturally, this being the Bay Area, there were protesters. Mercy for Animals had a question for everyone who attended:
11 - 01They have a point. I immediately saw the error of my ways. I assured the young man who gave me the brochure that I would make changes in my diet as soon as I could find a supermarket that carried canine cutlets and feline fillets. Oddly, he didn’t seem pleased with the evidence that their campaign was working.

In software development, ambiguous specifications are a major cause of bugs. The same is true in any other field. Murphy’s Law tells us that if something can be misinterpreted, it will be. If you’re trying to make an important point, have an independent observer review your copy before you blow your budget on printing.

While I’m on the subject, wouldn’t it make more sense to focus on organizations that are actively working against your cause instead of a group that’s has similar goals, but doesn’t go exactly where you are? I’ve never seen a pro-vegan protestor outside a barbeque restaurant, even in Berkeley…

For what it’s worth, we also went to the Bay Area Book Festival. Oddly, there weren’t any protesters there. Shouldn’t someone have been alerting attendees to the fact that the publishing industry kills trees–but not flowers–to print books, and urge them to go 100% e-book?


A few weeks ago, I saw this display at the grocery store:
11 - 02Yes, that’s a penny that I added to the basket to provide a sense of scale. Those are the smallest, orangest grapefruit I’ve ever seen.

And no, the sign isn’t for the shelf below. It’s hard to tell in this cropped, resized photo, but those yellow things are lemons.

It’s the little things that matter, folks. Developers test their code* before it goes to QA. You can do the same thing in any industry. Take a few seconds to ask yourself if you’ve completed all of the steps before you mark a task as done.

* Well, in an ideal world, anyway.


And then there’s this:
11 - 03I’m sorry, but this is just wrong. I freely admit that I don’t really get the whole “sweet + salt” craze. Sure, I’ll occasionally nibble a chocolate-covered salted caramel* or pretzel, but I don’t obsess about it. And, while I don’t have a problem with anyone who has gone full-on for sweet/salt foods, I will object strenuously to this abomination.

* No, Maggie, I haven’t been snitching yours, despite the temptation.

Let me make it easy: bacon is not a universal food, nor does it make everything better.

Back to the software industry: projects are reviewed many times to ensure that the software can be built as defined and that the design meets the needs of the customer. Same again in the rest of the world. Get someone outside of Marketing to take a look at the plan. And remember that “It won’t kill anyone” is not a sufficient standard of excellence.

It wouldn’t have taken a culinary QA expert to tell them this was a bad idea. Anyone with two functioning taste buds could have said “these flavors just don’t go together.” But I suppose cynical exploitation of a pair of trends trumped common sense.

WQTS 07

Advertising, as I understand it, is the art of making people aware of a product and convincing them they must have it. Sounds simple–especially the first part–but apparently not.

This advertiser is having trouble with the first part.
wqts71
With a what?

My first thought was that it’s with a boat, but I’m not totally sold on that idea. All of the boats are showing wakes. If Google can use barges for mobile “interaction centers,” why shouldn’t these people use shipping containers for mobile farewells to the dearly departed? Especially convenient if you’re going to spread the ashes at sea. OK, maybe not.

They’re obviously shipping something–“all kinds of goods”–to Eritrea. Maybe it’s “with a course”? I don’t know. I’d assume the ship’s navigator would know where he was going. Probably not worth advertising. Or, since it mentions “conveniently secured,” perhaps it’s “with a lock”. That might work. But if that’s the major selling point, you really ought to be more specific.

Then there’s this advertiser, who’s having trouble with the second part of the process.
wqts72
It’s clear they’re pushing cat litter deodorizer, an easily-understood product with a clear market. And yet they completely fail to convince me that I need to buy it.

I’m the first to admit that I sometimes snuggle the cats, which means I wind up getting a nose full of their scent. And yeah, some of them can be stinky at times*. But I don’t go shoving my nose into their “area“. It’s even questionable whether cats have an area in that sense. Millions of people my age grew up with that euphemism, and will make the same association. Suggesting that we want to sniff our cats that way isn’t likely to encourage us to buy the product. And, let’s face it, the cats–who routinely shove their noses into each other’s areas–don’t want to smell deodorizer. They want to smell the cat they’re sniffing.

* Not Ms. Kokoro, of course, who has the sweetest smelling fur of any cat I’ve ever met.

In short, advertisers need to consider all the connotations of the words they use.

Moving on.

Advertising encourages a certain amount of vagueness. In the case of some products–think perfume–it’s not just encouraged, it’s apparently a requirement.

Other fields aren’t as easygoing. I wouldn’t trust a navigator who told me to head “thataway”. Other professions require precision. Baseball, for example. Pitchers need precise control to get strikes. Lawyers spend their lives arguing over the exact meaning of words and phrases.

And there’s medicine. Would you trust a doctor who doesn’t know who you are?
wqts73
I had to fill out this form recently. I won’t ding whoever created the form too much over the redundancy in asking about drinking liquids (there aren’t a whole lot of solids one can drink or liquids one can eat–though apparently Jello is considered a liquid. But I digress.) I’ll also let the oddity of asking about my PCP at the end of the form slide (shouldn’t that be at the top along with my insurance information?)

It’s that middle question that stumped me for a while. I finally wrote “Second Base.”

WQTS 06

This post is a little bit later than usual, thanks to Mother Nature.

It’s raining here in the Bay Area. Despite the way our three-year drought has been monopolizing the media’s attention, the mere fact of rain isn’t really newsworthy. This is, however, a major storm*. We’ve had a couple of days of warnings and–all joking aside, perfectly justified–sandbag distributions.

* By local standards, naturally. Those of you in hurricane and monsoon zones may snicker derisively. I also grant permission for those of you in snow zones to laugh hysterically.

And, Pacific Gas & Electric workers have been making the rounds, trimming branches that might bring down power lines, and preparing as best they can to handle the inevitable outages.

Before I start discussing the failures here–and they go beyond QA–I want to be totally clear that I’m not dissing PG&E’s field employees. They do a vitally-necessary job that carries a high level of risk even in the best circumstances. Kudos to them.

But.

At 7:59, I got home from driving Maggie to BART. This had nothing to do with the weather; I drive her most Thursdays; that it means I’m not trapped at home if the storm knocks out the power is purely a bonus feature. I pulled out my phone and started to send her an e-mail assuring her that I had made it home in one piece. At 8:02, while I was still writing, the power went out.

I was a little surprised it had stayed on as long as it had. I finished the e-mail, sent it off, and made the rounds of the house, shutting off computers (yes, we do have multiple UPSes; doesn’t everyone?) At 8:10, I called PG&E’s automated outage line. This is a voice-recognition system. None of that old-fashioned business of punching numbers on the phone.

The first thing the system does is ask if you’re calling to report a dangerous situation, such as a downed line. I said “no,” and the computer played a pre-recorded message extolling the virtues of using the Web to report outages. Finally it asked “Are you reporting an outage?” I assured the friendly silicon that was exactly what I wished to do. It matched my phone number to billing records, asked me to confirm my address–it was correct–and then informed me that there was not a known outage in my area.

That was the first sign of trouble. I’ve never been the first person to report an outage, even when I’ve called immediately after the lights went out. By the ten minute mark, there’s no way I’m the first. So, Failure Number One: either the design of the system is faulty, in that it does not inform users when there’s a problem retrieving outage data, or there was a QA failure, and the error detection routines were inadequately tested.

But, OK, fine. I assured the computer that my power was out and I wanted to file an outage report. “OK,” said my electronic buddy, “is this a complete outage or a partial outage?”

“Complete,” I replied.

“I’m sorry, I didn’t understand that. Please say either ‘complete outage’ or ‘partial outage’.” Failure Number Two, and I put this one squarely on the design team. Why should I have to say “outage”? The important–and distinctive–information is the first word.

“Complete outage,” I said, willing to go along with the joke.

“Please hold,” PG&E’s electronic idiot said. A moment later, I heard a new voice.

“Hello, this is [name withheld to protect the innocent] in Sacramento. Do you want to get the status of an outage?” Failures Three and Four. Design flaw: I was not informed that I was being transferred to a human operator. Design or QA flaw: Said human operator was not alerted that the system had failed while taking an outage report.

NWTPtI was very polite and helpful. The first piece of information she asked for was my address. Failure Five–the automated system had correctly identified me; my account information should have been transferred along with my call. Again, this could be either a design or QA failure.

“There are three hundred forty six people affected by an outage in your area. There is no estimated time for the return of power yet, but a worker has been dispatched,” NWTPtI informed me, and then asked if I would like to be notified when an estimate was available and again when power was restored, and offered me a choice between text message or automated phone call.

I chose the latter, gave her a few more pieces of standard information*, and we concluded the call.

* Including the closest cross street. Shouldn’t that come from a geographical database as soon as she entered my address? I could call this another design failure, but why pile on? After all, it could have been some kind of perverse validation that I wasn’t pranking PG&E.

At 8:47, the power came back on. At 9:59–more than an hour later–I got an automated call from PG&E informing me that my power had been restored at 8:50. I’ll give ’em a pass on the time discrepancy; three minutes is within reasonable rounding error. Hell, I won’t even ding them for the delay in calling. It would be unreasonable to expect them to have enough lines to contact thousands of customers in real time.

But there’s still Failure Number Six: I’m still waiting for the call with the estimated time to make the repair. This one I’m throwing at QA. Either a policy change was made and nobody caught the resulting error in NWTPtI’s script, or software QA missed at least one condition under which a call wouldn’t be made.

The bottom line is that the power is on. That’s far more important than letting me know how long it’s going to take–I’d rather sit in illuminated ignorance than enlightened darkness–but really, PG&E, much as I respect your field workers, I’ve lost quite a bit of respect for your back office personnel.

WQTS 05

Halloween is coming (and there will be a full-sized Halloween post tomorrow), but I thought it would be a good idea to remind you all how not to observe the occasion.

  • w5-2Your kids are going to want to collect “hella candy”. Or maybe “hello candy”*. Either way, this collection bag isn’t going to do it for them. Considering how much of the lettering has flaked off already, by next Friday, it’ll probably be down to “hell and,” leaving the kids to supply the damnation.* That sounds like either a disturbing porn movie about hospital volunteers, or an attempt to subvert Sanrio’s intellectual property.
  • w5-1No matter what they collect their loot in, you can bet that they will not want to find any of these “Despicable Me Fruit Flavored Snacks” in with the candy. What do despicable me fruits taste like, anyway? Judging from the picture on the box, much like a faded, hairy Twinkie. Bleah! (Full disclosure: I’ve never seen “Despicable Me,” so my apologies if the movie discusses the flavor of the fruit it’s named after.)

WQTS 04

“The Fault In Our Stars” is a Spiderman movie? Who knew?
spi

Apparently, our local supermarket knew. Maybe they were fooled by the upside-down character on the cover?

Seriously gang, if you’re too cheap to buy a new cardboard display rack, at least take thirty seconds and cover the text with duct tape. There’s some in Aisle 5.


OK, that was clearly a mistake. A preventable mistake, certainly, but most likely not something done with malice in mind.

On the other hand, we’ve got the latest piece of mind-warping stupidity from Organic Valley.

I’ve complained about OV before, but this radio spot sinks to new depths in its casual disregard for logical thought and scientific accuracy. Of course, as we know, OV has no interest in science. Start doing science and you might come into contact with chemicals!

You don’t have to take my word for the accuracy of my transcription. Organic Valley’s advertising agency, Solve, has kindly archived several of their radio and TV ads. By all means, go take a listen to “Bats and Frogs”.

Back? Good. Let’s break this down. According to Organic Valley and Solve, OV’s farmers listen for bats and frogs because “where there are bats and frogs, there are insects.” Yeah, OK. Not all bats and frogs are insectivores, but enough of them are that I’ll give OV a pass on that claim.

“Where there are insects, there’s healthy soil free of toxic pesticides.” Well, no. Haven’t they ever heard of mosquitoes? Bats and frogs love ’em, but their presence is more likely a sign of stagnant pools of water than healthy soil. Many insects don’t much care about the presence of “toxic pesticides”* in the soil either. Unless they’re one of the few species that breeds underground, pesticides in the soil have little effect on them.

* A redundancy if I ever heard one. What’s the point of a non-lethal pesticide? (OK, yes, there are some that interfere with the pests’ breeding cycle. They’re in the minority–and OV doesn’t like them either.)

“Where there’s healthy soil, there are acres of organic pasture grasses.” Or acres of forest. Or a tiny lawn behind a tract house. The quality and health of the soil says very little about the use people are making of the land.

“Where there are acres of lush pasture grass, there are happy, healthy Organic Valley cows that spend their days eating that grass…” Not stated, but strongly implied: OV cows eat only pasture grass and only OV cows eat pasture grass. The first is untrue according to OV’s website (per my previous rant, the website acknowledges that a significant portion of nutrition comes from stored dried forages, including corn). The second is self-evidently ridiculous: non-organic dairies may or may not give their cows as much pasture time as OV, but most give them some. How useful that pasture time is, is another question, given that even OV admits that their cows need supplemental nutrition.

“and producing delicious Organic Valley milk as part of a thriving ecosystem.” “Delicious” is subjective, of course. I doubt whether OV can point to any legitimate double-blind tests that show their milk to be any more delicious than any other dairy’s, but I’ll let that pass. “A thriving ecosystem.” Hmm. Last I checked, a thriving ecosystem was, by definition, a closed system. Nothing needs to be brought in from outside to stave off collapse. Do the cows produce enough natural fertilizer to keep those pastures lush? Do those bats and frogs have sufficient breeding grounds? I tend to doubt the claim of a thriving ecosystem, but I can’t actually disprove it. OK, I’ll give OV a pass on this bit.

“Just don’t forget to thank the bats and frogs.” OK. Uh… just what am I thanking them for? Are you seriously suggesting that the bats and frogs are responsible for the “delicious milk”? They’re not producing the insects and the insects aren’t producing the soil. OK, yes, the soil may be producing the grass, but the cows aren’t a product of the soil, the insects, the frogs, or the bats. Or is OV hinting that they’re not selling cow milk, but actually bat milk? Probably not. We can be sure it’s not frog milk, since frogs aren’t mammals and don’t produce milk.

Look, I’m sure Organic Valley milk is no worse than any other milk you can buy, and it’s probably tastier and more nutritious than some, but this kind of fuzzy thinking presented as advertising is insulting to the intelligence of the listener. It’s exactly the kind of wishful thinking that suggests that vegan diets can halt climate change.

WQTS 03

Meet Grace.
grace

Grace is a product of Grace Digital and she has a problem.

Don’t get me wrong. I like Grace quite a bit, but she’s plagued by a bug. A particularly annoying one, and one that she shares with a number of her siblings.

Grace Digital no longer makes this particular model of internet radio, but they have several current models with similar internals. They specialize in low end Wi-Fi audio systems–most of their models sell for around half the cost of a Sonos system. They keep costs down by making incremental hardware updates and updating the firmware as little as possible. Once a particular model is out of support, it gets no more firmware updates.

Grace’s model was released in 2009 and received several firmware updates before she went out of support. The very* last release added support for Grace Digital’s iOS and Android apps.

* I’m working from memory here, as the version history is long-gone from the website and I haven’t found it in any archives. Rest assured that if it wasn’t the last release, it was very close.

It’s that last release that introduced the bug.

In pre-app releases, turning Grace off actually turns her off. When she comes back on, either via the power button or an alarm, she has to reconnect to your Wi-Fi network. The delay annoyed some customers and it created a problem for the apps: if the radio wasn’t connected to Wi-Fi, the apps had no way to turn it on. Not very useful for a remote control…

So that final firmware introduced a standby mode in with Grace’s display turns off, but the Wi-Fi radio stays on and connected. Problem solved, right? Music starts almost instantly, and the apps can scan for radios and turn them on. Works great. Except for one itty-bitty problem.

Shortly after the firmware was released, customers started complaining that their radios turned themselves on spontaneously. When you have the radio in your bedroom so you can use it as an alarm clock, having it come on in the middle of the night is annoying, to say the least.

At first Grace Digital had customers send the “defective” units in for testing, but once they isolated the problem, they solved it in a very direct way: customers who complained that their radios turned on spontaneously were advised to disable the standby setting.

Now, I know what you’re thinking: Grace was unsupported, so why release a fix? Well, remember what I said about incremental hardware changes between models and minimal firmware changes? Other models of radios put out by Grace Digital that were still supported use very similar hardware and closely-related firmware. Some were even released to the public after the bug was discovered. It’s not fixed in the firmware for those devices either–I have an “Allegro” model that was released late enough for its manual to explain how to turn on the standby feature, and the bug is still present in the last-released firmware for that model as well. I have no direct evidence beyond a few suggestive Internet posts, but I believe the bug is still present in Grace’s current models.

As I said, I like Grace–and her siblings–and I still use mine, just not in the bedroom; I’m not fond of 3 AM wakeups, especially unplanned ones. I have no qualms about recommending Grace Digital’s products to anyone looking for a decent, low-priced media streamer. If you don’t need all of the features of a Sonos player, Grace’s current descendants are an excellent value. I find it surprising that the bug hasn’t been resolved, but I suspect it’s a marketing decision: my suspicion is fixing the bug would break backward compatibility with the apps, requiring Grace Digital to support two versions going forward.

So why is this post a WQTS item? Simply because it’s clear from the sequence of events that Grace Digital was unaware of the bug when they introduced the standby feature. Granted it’s an intermittent problem, but it’s not hard to find, either. Heck, it should have turned up in any test of the long-term stability of the standby mode. The simple test of putting a radio on standby and leaving it overnight should have uncovered the bug. The fact that Grace Digital required radios to be returned for troubleshooting shows that either the bug was not found–indicating inadequate testing–or the bug was not logged–indicating inadequate testers.

WQTS 02

zThanks to Maggie for pointing this one out.

OK, leaving aside the absolutely mind-bogglingly useless nature of the product–none of the sports represented by the containers has anything to do with Easter, and only one is even arguably a Spring sport–didn’t anybody catch the correct spelling?

Seriously, if you’re going to intentionally misspell “Sports” and “Balls”, it doesn’t make any sense to spell “Eggs” correctly.

Come on, guys. “Sportz Ballz Eggz” It’s that easy.

Oh, and while you’re at updating the packaging, would you be so kind as to either delete the word “NET” or add another line specifying the gross contents? Thank you.