embedded software boot camp

Saving REAL Money on Healthcare

February 16th, 2011 by Mike Ficco

In a previous post (Butcher, Baker, Candlestick Maker) I had a link to my blog at MyPath.  That link was broken when they moved to a new format.  With their permission I have reposted it below so I can fix the broken link.

Origionally posted on MyPath.  Follow @MyPath_MP on Twitter for more career managment advice and resources.

==============

As I changed jobs over the years I never thought much about the medical benefits offered by a prospective new company.  Yes I wanted benefits, but I was more interested in the duties of the job and how much it paid.  It was only during the years I worked as an independent consulting engineer that I became more consciously aware of the convenience and savings associated with a company provided plan.

While the self-employed or unemployed may have a different perspective, it seems most regular fulltime employees of corporations see medical benefits dimly in the background – alongside furniture, stationery, and other things companies are simply expected to provide.  Over the last year, thanks to layoffs and the chaos we call our government, healthcare and corporate medical benefits have been anything but a background issue.  Hyperbole reigns on both sides, from “Electronic health records will save us billions” to “We are headed down the rat-hole of socialism”.

I’m not a financial or healthcare professional, but I do have several decades of experience thinking logically.  It seems to me that putting everyone into a national healthcare system will have several consequences.  One is that we will gain revenue from those who are young and healthy and consciously taking the risk of carrying no health insurance.  Had I done this over the last 30 years, and been disciplined enough to save the extra money, today I would be able to pay for a couple of heart transplants out of the savings.  The trick, it seems, is to have genuine fiscal discipline and to not spend the extra money.  I can’t guarantee I would have been able to do that.  Even our government was unable to resist spending the entire Social Security surplus – leaving us with debt and IOUs for the coming years.

Another consequence of the proposed new healthcare system, which I’m surprised few are talking about, is great risk for insurance companies no longer allowed to reject sickly applicants and no longer allowed to limit expenditures for any customer.  Insurance companies that, for whatever reason, accumulate a large number of such expensive patients will be forced to raise their rates – causing customer exodus to the cheaper companies.  In a world where insurers must take all applicants, it seems reasonable to expect a great deal of customer turbulence.  One can envision wholesale customer migration from expensive companies to economical companies as ailing clients drive the rates up everywhere they go.

Several years ago I had a cold that turned into a cough.  The cold was unremarkable but the cough lasted and lasted and lasted.  After maybe three weeks my cough had become an irritant to everyone around me – including my coworkers and family.  I’d spent a couple of weeks guzzling over-the-counter cough medicines but they seemed more useless than I remembered.  Evidently genuinely useful cough medicine is no longer available over the counter.  Finally I decided to call my doctor.  He refused to write a prescription based on a phone call but I was able to get an appointment the next day.  I paid my $20 co-pay and was seen by a physician’s assistant.  He asked me a few questions and listened to my lungs.  His diagnosis was… a cough.  He wrote a prescription for codeine cough medicine and had the real doctor sign it.  My office visit was $110.  The drugstore sold me the medicine for $10.

After a few days my cough was gone.  The “real” cough medicine broke the cycle of the continual coughing repeatedly irritating my throat.  Breaking this cycle allowed me to quickly heal.  I was cured at a cost of $20 co-pay + $110 office visit + $10 cough medicine + about $20 in over-the-counter “pretend” cough medicine that did nothing.

So here is the question:  If we are SERIOUS about reducing the cost of healthcare why don’t we give more power to the people and let them obtain real medicines?  Let it be the individual’s choice as to whether to see a doctor and perhaps get expensive tests.  Yes we have to protect people from themselves and people are clueless and will overdose and kill themselves and their kids will get the drugs and they won’t understand the contraindications and can’t read the labels and yada yada yada…

Blah, blah, blah – danger… blah, blah – controlled substances… blah…

Laws written by our government with the intent of protecting people from themselves are costing us money and lots of it.  Maybe this was good 20 or 30 years ago but today’s national debt is staggering and the cost of healthcare is spiraling out of sight.  We need to at least have the discussion as to whether such restrictive laws have a place in our current society.

If we want to continue spending money, albeit far less, we could add a safety net by implementing a national tracking database that would email your doctor with a notification every time you purchase a medicine.  We could even implement an Expert System that would warn of excessive purchases, flag interactions, and suggest addiction counseling.  All this can be done far more cheaply than requiring everyone to pay $150 for some cough medicine.

Probability, Stochastic Processes, and Airport Security

November 28th, 2010 by Mike Ficco

I’m an engineer.  This means, like most engineers, I survived a couple of courses on probability.  For some engineers this knowledge is critical to their work.  For many it merely provides background knowledge about the behavior of the physical world.  As a group, however, engineers have a much better understanding of probabilistic events than the man (or woman) on the street.

The average person so poorly understands probability and probabilistic events that casinos get to sell a guaranteed long-term loss as gambling.  For example, engineers understand that if you play a slot machine long enough, you get back exactly what you put in minus the casino’s take.  Not only that, electromechanical slot machines can be and are easily adjusted by the casino as needed to accommodate their marketing and profitability needs.

Engineers understand there is no magical force connecting statistical events such as coin tosses.  That is, no matter how many heads in a row have been tossed, a fair coin will always have exactly the same probability of heads on the next toss.  The chance of heads on the very next toss does not decrease because heads has already been tossed repeatedly.

Given that engineers, at least those who stayed awake during their classes, understand the basics of probability, one must wonder why the fraternal order of engineers has not complained loudly against the concept of random searches for terrorist related activities.  Specifically, if a terrorist organization has thousands of followers ready to die for a cause, random testing does no good whatsoever.  This is worth saying again.  Read this until you understand it.  Testing 3%, 10%, or 50% does nothing.  If you happen to thwart one terrorist, the next one or the next or the next will get through and accomplish the mission.  Anyone in a position of authority recommending random testing or searching either has some agenda in mind or has a dangerous lack of understanding of probability.  Anything other than 100% testing or searching is meaningless with respect to terrorist activities.  Yep, the fear of getting caught may deter NFL players from using steroids but getting caught means nothing in the terrorist scenario.  They just recruit the next in line willing to blow themselves up.  If the target were important to the terrorists they would send their minions until one slips through the random searches.  Numerically speaking, not many would have to be sent to get through even 50% testing.  3% testing seems useless.

OK –

So if we assume the proponents of random searching for terrorist activities have a brain, or at least listen to knowledgeable advisors, their reason must be something other than actually dissuading terrorist activities.  To me, the answer seems obvious.  All in the position of protecting us from harm know they will eventually fail.  There is no question about this.  No matter how good you are and how hard you work, you can’t be perfect every time and every day.  Sooner or later a bad guy will get through.  Sooner or later we will lose another plane, or a train, or perhaps even a city.  When this happens, the executives in charge of protecting us will be pilloried by congress and the press.  The executives need a way to deflect blame and the way they seem to have chosen is highly visible security theater.  Given my somewhat poor understanding of human nature and the society in which we live – I predict that, in fact, the TSA executives will get an automatic free pass for failure if they are summarily ordered to back down from intrusive searches.

I found it remarkable for many years that our monuments were still standing.  From perhaps the 1970s until 9/11, I would occasionally reflect that someone was doing an incredible job.  I assumed every nut in the world wanted to do us harm – yet our monuments were untouched, there were no explosions at the super bowl, and political figures were rarely assassinated.  Then, somebody screwed up and 9/11 happened.  Suddenly everything that was being done quietly in the background became theater.  At the airport I observed people pulled from the security line and searched within view of the other passengers.  Being an engineer I understood that such random attention was meaningless and perhaps even harmful in that it gave those with a poor understanding of probability a false sense of security.  The fact that it was done within view of others in line made it terribly obvious the intent was to visibly covey those in charge were doing everything possible to keep all of us safe.

As a society, we transitioned from our guardians quietly doing their job in the background to overtly warning us that we are in danger and need protection.  We now live at a perpetual threat level of “elevated” and regularly hear of new risks that are being detected.  We hear, for example, that German agents have apprehended the great uncle of some guy who heard from his cousin that there is some plot involving bottles of shoe polish.  In response, bottles of shoe polish are banded from carry-on airline luggage.

Look, guys…

Why do you feel you have to advertise these kinds of things?  You are wrong if you think occasionally publicizing the great job you are doing or periodically reminding us how much we need you is going to protect your job in the event some terrorist manages to accomplish their mission.  If a problem occurs, you guys are screwed and heads will role.  Sorry, it isn’t fair but that is our society.  Just do your job the best you can, quietly, as your predecessors did.

The battle against terrorists is a continuing evaluation of relative risk.  This means everything is about acquiring information, statistics, and probability.  Our uniquely American culture believes that all life is precious and must be protected and nurtured.  As an American with more than 50 years of experience with this culture, I think we will all or almost all agree that the lives of those who fly on commercial aircraft are of exactly equal value to those who drive cars or are patients in hospitals.  If this is true, if all lives are of equal value, how do we explain our infatuation with airport security and neglect of other areas badly in need of money and attention?  Every year, every single year, we kill something like 40,000 people on highways.  Every year, every single year, hospital errors are responsible for the deaths of 90,000 people.  How many airline passengers died last year due to terrorist activities?  In fact, the enemies of bad software and mechanical failure statistically seem to be far more dangerous than any terrorist activity.

To be fair it is possible that our low incidence of terrorist related aircraft death is due to the skill and hard work of the various protective organizations.  Consider, however, that something like 770 million people fly through American soil each year.  If we assume a flight on average carries 200 people, terrorists would have to blow up 200 flights per year to match our automotive death rate and 450 flights per year to match the number of hospital deaths.

Why are we so fixated on aircraft issues?  Well, one big reason is aircraft were the vehicle of choice for the 9/11 attacks.  Had the terrorists used busses, we would have focused on them.  Our kneejerk responses to various attacks do not bode well for our ultimate safety.  There are an infinite number of ways we can be attacked and pouring all or most of our resources into protecting us from the old methods may make us unnecessarily vulnerable to a new method.

OK, so what about those new airport scanners?

The media continually refers to the new security devices at airports as “scanners”.  Although I’m an engineer and somewhat in tune with technology, only last week did I understand that these devices are based on two emission technologies – one emitting x-rays and the other emitting microwaves.  Remarkably, I haven’t heard much about dangers and risks associated with these devices.  New x-ray devices, like new pesticides, are always deemed “safe” when they go into use.  Years later we find out how dangerous they really were.  History says only a fool would say that these x-ray and microwave devices pose no danger whatsoever to any risk group – even people with skin cancer or pregnant women.  I haven’t been to an airport recently and wonder if they have warnings posted for pregnant women.  Hopefully the TSA is righteous enough to recommend pregnant women get fondled rather than x-rayed.

It is reasonable to assume some frequent travelers who are repeatedly subjected to x-rays or microwaves will suffer soft tissue damage, develop cataracts, cancer, or other problems.  Once again, we are looking a relative risk…

But won’t the naked pictures of travelers and personalized fondling make us all safer?  Sadly, no.  What it will do is force the evil organizations to surgically implant bombs or biological devices inside the terrorist’s body.  Only visual inspection of the body will detect scars from the implantation of non-metallic devices.  Also, a terrorist need not get on a plane to create terror.  What do we do the first time someone detonates a bomb while standing in line waiting to go through security?  We have no answer to that.  The first time this happens, our protectors will look like the keystone cops running in circles.   I can’t even imagine the solution they will propose for this problem.

Likewise, it is merely wishful thinking that any images obtained could never-ever be released to the public.  Consider what Wikileaks has done with secure military information.  Banks seem to accidently expose credit card numbers on a disturbingly regular basis.  Do you really believe it is absolutely impossible for images to be leaked?

Gee, I wonder if recognizable tattoos show up in these images?

What of homosexuals?  Do they have the option of being fondled by someone of the opposite sex?  For that matter, do heterosexuals have the option of being fondled by someone of the opposite sex?

What of homosexuals working for the TSA?  Does TSA execute a don’t-ask-don’t-tell policy?  Can there be undisclosed homosexuals doing pat-downs/fondling passengers?  Is it absolutely impossible for a sexual pervert to make it into the ranks of the TSA fondlers?

Who cares anyway?  If your job requires travel and you don’t want to deal with the airports – just quit that job and go get another one to support your family.  Jobs are plentiful.

But enough negativism –

If we do continue down the current path, I see a number of unique opportunities offered by this new surveillance technology.  Consider:

  1. Aluminized foil appliqués worn under the clothing for advertising purposes.  Prostitutes, for example, might have a message something like – “Like what you see?  Call 800-555-1234″.  Or the foil advertisement may suggest a place for the TSA agent to eat when they go off duty.  Or a new movie may be advertised.  Or…  The sky is the limit here.
  2. Nevada, for example, could offer airport secure saunas and messages.  Highly trained TSA certified masseuses could cavity search travelers – and provide a number of other relaxing services.  The secured travelers would then be escorted directly to the aircraft.  For an extra fee, some may choose to be bound in latex for the duration of the flight.
  3. Somehow the homosexual thing must be solved.  The easy solution also opens and entire world of other money making opportunities.  Simply line up the TSA agents, both male and female, and let the traveler select the one to conduct the fondling.  Some agents would likely develop regular customers from among the frequent flyers.  Yes, I envision a frequent flyer telling Lars, the large TSA agent of Scandinavian heritage, “[wink] see you next week, Lars”.

Final thoughts –

I’m an engineer, so I really like engineers getting paid to build sophisticated equipment.  On the other hand, I’m also a taxpayer.  Can’t we make air travel secure in a more economical fashion?

We live in a democracy.  If the majority decides airline travelers must be strip-searched and anal-probed, then so be it.  But… We don’t need sophisticated technology for this.  Why not just have everyone strip and be cavity searched?  They would then be issued an airline provided prison gown and put on the plane.

Another possibility comes to mind.  This has the down side in that it takes power from the hands of the bureaucrats and gives it to the people.  Hence, it is not likely many in big-government positions of power would support it.  What if… now I’m just thinkin’ here… what if instead of pat-downs and high-tech x-ray imaging we just told everyone getting on the plane:

” Do not let anyone take over this plane”

I look forward to hearing from those who can correct any of the information or statistics I used in this article.

Oh, and one final, final thought –

I hear that, because of their well-established security credentials, members of Congress are exempt from the new imaging and fondling.  Does this mean that EVERYONE with a high-level security clearance is exempt, or is it just the kings and queens of society?  Hummmm, kings and queens…

Engineering vs. Banking

November 4th, 2010 by Mike Ficco

One of the great advantages possessed by engineers is that many of us can do arithmetic.  An engineer friend of mine used his ability to multiply and realized his bank was more than a little deceptive.

With interest rates at historic lows and the grim reaper seemingly poised over the stock market, many people, including engineers, are struggling to find ways to get a good return on their money.  Banks are well aware of this situation and devote great effort to attracting new customers, sometimes to the disadvantage of their existing customers.

Over the past few years the rate on my friend’s interest paying checking account had decreased to 0.01% (one hundredth of one percent).  He just assumed that was due to the pervasive low interest rate environment.  Then one day he was looking at certificate of deposit interest rates on the bank’s web site and quite accidently noticed that interest checking was supposedly earning 0.15% interest.  He double checked his account and verified that the bank was advertising a 15x higher rate than he was getting.  How dare they advertise such nonsense he thought?

To my friend’s surprise, the bank’s customer service center verified the advertised rate.  It seemed the interest bearing checking account he had was no longer offered.  Apparently he, and thousands of other banking customers, were “grandfathered” into a product with 0.01% interest while new customers were receiving 15x higher.

The good news is the bank allowed him to convert to the new type of account.  He had only to ask.  The bad news – he had to know to ask.

What does all this have to do with engineering you say?  Well, small engineering companies make lots of money and become large engineering companies in a number of ways.  One very successful approach is to create a new market segment and grow that segment (think PCs, wireless LANs, and smart phones).  Critical to growing a new market segment is to publish a standard, then to work with other vendors to create “killer apps” that adhere to the standard.

Small and large engineering companies may also attempt to improve their bottom line with the highly exotic and mystical approach of making a great and reliable product and selling it at a reasonable price.  Sometimes companies purposefully sacrifice profit to grow their market share.  Their plan is not to give away money, but to give customers such a great deal that the company rapidly attracts a large number of customers.  This forward thinking strategy believes that by foregoing profits today, the company will reap much larger profits tomorrow.

Technology companies seem to create an endless stream of new products and new markets.  I don’t work in a bank but it looks a little harder to create new products in the banking world.  A long time ago someone created the mortgage.  More recently the credit card was invented.  Still more recently we got debit cards.  These are innovative products to be sure, but far from the avalanche of new electronic stuff we see every year.  It seems to increase profit; banks must attract more customers and figure out how to extract more money from each of them.  Charging 20% interest on credit cards worked well, but banks are losing this revenue stream as people pay down their debt (and the government implements greater protection from gouging).

To be fair, it’s not just banks that continually shift the rules of the game.  All companies based on providing a service do this to some extent.  Subscribers to Internet services, for example, regularly discover the service they have is no longer offered to new customers.  They discover they were “grandfathered in” to a no longer available product that is less desirable than that being offered new customers.

There is a core difference between service companies and product companies.  Both benefit by trimming their costs.  Both benefit by having more customers.  However, when a service company desires more money (and their stock holders would be unhappy if that was not their goal), they tend to invent ways of getting more money from current customers.  They offer credit protection plans, reduce payments or benefits, and raise fees.  In a sense, the consumer must be aware of always-shifting terms.  This is a somewhat retroactive Caveat Emptor – “Let the buyer beware that they no longer have as good a deal as they had previously”.

Haggling over the price of a new car or waiting for a sale on a new television may be painful but at least you only encounter such problems every few years.  In dealing with service companies, however, it seems the consumer’s work is never done.  There is always the next rate change, software update, or change in terms and conditions.  There are no regulations that require banks or other service providers to notify existing customers that new customers are getting a better deal.

The consumer’s pain seems only destined to get worse as our economy slides ever further from manufacturing towards a service based economy.  I think engineers may be especially susceptible to overlooking changes in rates and fees since their personality is highly optimized to nail down a problem and move on to the next.  As a service consumer, however, they must continually revisit already solved problems.  As a geeky engineer I feel compelled to paraphrase the last line of the classic 1951 science fiction movie “The Thing” (aka “The Thing from Another World”).

“Watch The Fees”

Cut And Paste Engineering

September 9th, 2010 by Mike Ficco

Several years ago I was involved in a project that expected to have a large production volume.  The development group was working with a few prototypes but the manufacturing team was not yet fully engaged.  Part of my work required a unique device serial number for security and other purposes.  Unfortunately, our prototypes had no serial numbers since they were not produced by the normal manufacturing process.  I needed a serial number so I came up with a relatively simple solution.  On power up I would read the area of non-volatile memory that was intended to hold the serial number and other information.  If the information passed a validity check I would write the serial number into another special area of non-volatile memory.  If the validity check failed I would instead write a fictitious serial number[1].  All other code made use of this “special memory” that I created and managed.  My immediate development problem was solved and all the code would automatically start using real serial numbers as soon as the equipment was being made on a production line.  Problem solved!

The product shipped and actually did get produced in high volume.

Fast-forward about eight years.

A coworker came into my office and asked if I could take a look at some old code.  We walked to his office where he brought up a page of code I had not seen for many years.  It was my power up serial number initialization function.  Well, more accurately, it was a descendent of my code.  After many years and several million devices, the code was still present.  The operating system had changed at least three times and several people – perhaps more than a dozen had their fingers in the surrounding code.  The details had changed and the content of the structure that was validity checked had changed.  Even the method of doing the validity check was different.  Yet there was my fake serial number and my privately managed memory.

The developer said he didn’t understand what the code accomplished or why it was needed.  He asked the person that previously worked on the code and he didn’t know either.  Some of the original project folks had left the company.  I had gone off to new products and problems.  Others had seen the code but did not know the rationale behind it.  Eventually my name came up as he continued to ask questions, so he thought he would come talk to me.

I quickly explained what the code was for and that it was no longer needed.  I also took the opportunity to congratulate him for being conscientious in wanting to get the code right and bold enough to ask about the code when so many who came before him had not.

This is a true story and you may or may not have enjoyed it.  The problem is such stories of tracking down the meaning of mysterious code are far too rare.  More often code proliferates and becomes progressively more convoluted as programmers are afraid to touch or delete what they don’t understand.

One very popular coding technique is to copy an existing piece of code that solves a problem similar to the one on which you are working.  Over time a large code base becomes fabricated from bits and pieces of old code.  This is outstanding in that it is something like code reuse.  It is beyond horrible in that such reuse is occasionally perverted into a bloated and unreliable mess.  It seems basic instinct for most programmers to allow poorly understood code to remain.  I have seen developers and managers too fearful, and I truly mean fearful, to remove bizarre code because it might be doing something worthwhile.

Last year I worked on a one-chip-wonder micro controller.  I inherited over 90K of buggy code that needed additional features.  Four months later I had 5K of reliable code that had all the needed features.  Not all of my projects result in a 1800% code reduction, but this basic scenario has played itself out over and over.  A great deal of my work finding and fixing bugs on legacy products has involved removing large amounts of code.

Let me leak out a well-kept secret:  If you want your code to be reliable, you have to understand what it does.

You are not a very good developer – at least not one confident in your ability – if you are afraid to touch some mysterious code for fear of breaking it.  Poke it!  Tweak it!  Test it!  Figure out what it does and determine if it does that correctly.  You or your manager may worry that this is wasted time, but my personal experience has been that mysterious and bloated code is often the cause of problems and takes forever to debug.

Well-understood code is not only shipped faster, but you can also ship it with pride.


[1] Our serial numbers were to be based on the production shift, production line, and the date and time of production.  I worked with the manufacturing group to create a serial number based on a non-existent production shift and line to guarantee my fictitious serial number would never be mistaken as genuine.

The Tragedy of Low-Flow Plumbing

July 13th, 2010 by Mike Ficco

I’m a middle-aged man, so you can guess what this blog is about…

Yes, that’s right, bathroom fixtures!

Today we are examining the high-tech, highly political, and seriously flawed attempt at conservation by reducing the rate at which your plumbing can deliver water.

I lived in my house for over 20 years and the bathroom fixtures are showing their age.  In something resembling temporary insanity I bought a couple of new faucets.  They were chosen because they were attractive and reasonably priced.  I never even knew there was an issue with the water flow rate.  After all, we’ve been making water faucets since there has been indoor plumbing – why should they change now?

But change they have…

After installing my pretty new fixtures, I was disappointed to find water flows from them much more slowly than the originals.  My first thought was a manufacturing defect.  What’s wrong with these things, I thought?  After some inquiry I learned I must actually thank my government for this.  Since 1994 federal regulations have placed upper limits on the water flow rates of bathroom faucets.  My research led me to the EPA website (www.epa.gov) where I was disappointed to find a classic case of government Newspeak.  On this website the low-flow faucets, which I initially thought were defective, are called “High Efficiency” faucets.  They may as well be called doubleplusgood faucets!

It seems “legal” bathroom faucets must conform to the EPA WaterSense® program specified American Society of Mechanical Engineers (ASME) A112.18.1 standard.  In brief this standard sets the maximum flow rate of 1.5 gallons per minute (gpm) for the common household water pressure of 60 pounds per square inch (psi).  This is, as Colonel Sherman Potter would say, “Horse Hockey” (if you are too young to understand this, look it up).

Don’t get me wrong.  I’m as “green” as anybody.  I conscientiously recycle and turn water off when I’m not using it.  I absolutely agree it makes sense to re-engineer the classic design of the flushing toilet.  This makes sense with a toilet because the device autonomously uses the designed amount of water.  Faucets, however, do not.  They are – oh what’s the word I’m looking for – ummm – oh yes!  Adjustable!  Legislating an upper flow rate of a trickle is not sanitation engineering, it’s social engineering.  Even worse, it is misdirected social engineering.  This was done so I would use less water but that has not been the result.  Instead of a short quick blast of water to rinse my toothbrush, I have to let the water trickle onto the brush and rub my thumb back and forth.  Cleaning my twin-blade razor is even worse.  I can’t blast it with water and rubbing my thumb on it doesn’t seem like a good idea.

The flushing toilet was designed when the world population was about 1 billion.  It seems reasonable to revisit this design now that 5 billion more people are flushing.  The inefficiency of the WC has long been recognized.  Thrifty people back in the time of your grandparents would put a brick in a toilet’s water basin so less water would be used.  However, and I’m back on my engineering quality horse again, when you ship a product it should actually work.  The first reduced water toilets were, to be frank, a piece of crap.  Many of them had to be flushed two and three times and, therefore, actually consumed more water when one considered real-world usage.

As I researched my “defective” faucets I found claims that these low-flow devices reduced water consumption by 30% or more.  Balderdash!  This isn’t about the arithmetic of comparing the maximum flow of traditional and crippled faucets.  It’s about social behavior.  I guarantee, based on my own behavior, water saving is minimal if any because the slow water jet is not strong enough to accomplish rapid rinsing.  Instead, the legislated trickle rinses and rinses and slowly does the job.

I applaud industry and government attempts to conserve our dwindling resources, but get it right and be realistic.  Don’t create some imaginary world where there is some arithmetic relation between obstructed water flow and water savings.  MP3 became a spectacular success because it was designed around the real world of human perception.  Those who legislate the behavior of our bathroom fixtures would do well to get out of their ivory towers and consider actual human usage.

Let me say again, unlike the toilet, a faucet is adjustable – ADJUSTABLE!

Do not assume I use water with malicious intent.  These low-flow and certainly not high efficiency faucets were designed with the unwarranted assumption that the government knows better than me how to save water in my bathroom.

Bad idea.  Bad, bad idea.

If you want me to save water, tell me to save water.  If I don’t save enough, penalize me in some fashion – perhaps by raising the price of water.  If water costs enough, I guarantee I can save more with personal effort than you can force me to save by crippling my faucet.

What were you guys thinking and how has this gone on for so many years?