is faster really better?

I work in software development and we are constantly being asked to do things faster.  This doesn't sit well with me.  Let me explain.

There are many things we can think of that you (yes, You) don't want to do "faster".  Take a minute and think of a few.  The first ones I came up with are (in no particular order):

• sleeping (imagine someone telling you to sleep faster. you would laugh at them.)
• driving to work (the policeman may not like this)
• taking vacation (woo-hoo! we took that vacation in record time!)
• eating (besides the nutritional downsides...)
• breathing (please, please do this)
• playing games (whew, another speed round of cards.  now get back to your electronics, kids.)
• writing a blog post (wait, what?)

There are more, I am sure.  the point is: when did it start making sense to develop software faster?  It seems that we are over-learning our days in track and field where faster/farther wins the race...I can also see when the product you are developing is directly affecting the bottom line of the company insofar as the competitor may be working on the same product and being first in the market is important.  Otherwise, it just drives me crazy.  Without substantiation, not all software should be developed faster. 

I would even propose that faster is not better in 99% of all cases.  Make it correctly and be efficient.  Minimize waste.  Maximize the work not done.  But faster just appears to me to be the moaning of someone not in tune with mature software development.

And what does faster mean?  Aren't we doing this fast enough?  Would you prefer more defects or shoddy code faster, if faster is all you are interested in?  Why aren't we asking for fewer or (gasp) zero defects?  Why aren't we as coders demanding well-formed code?  We should be creating something we are proud of, are you?  And if you ask me to do it faster, you strip me of my pride in my code.