raganwald
Tuesday, November 28, 2006
  People want software that is cheap, buggy, and first

People reward developers who deliver software that is cheap, buggy, and first. That's because people want fancy new gadgets now. They don't want inconvenience, don't want to learn new ways of interacting with their computers, don't want delays in delivery, and don't want to pay extra for quality (unless it's obvious up front--and often not even then).

Bjarne Stroustrup, The Problem with Programming

 


Thank you for reading my work. Did you enjoy this post? You can find more like it in the sidebar. Please browse the archives, there are lots of hidden gems. A Brief History of Dangerous Ideas explains what I am up to at the moment.
Comments on “People want software that is cheap, buggy, and first:
I would modify this to be "Marketeers/Sales Folk" want software that is cheap, buggy, and first. If you ask the common person they want something that works without question (high quality) and if you ask the developer they may say something similar.
 
I wouldn't agree to this modification.

People SAY they want something that works, just like Marketing and Sales will agree that quality is of paramount importance.

That said, 'first' and 'lots of features' tends to get the sales, so software companies respond to the incentive, and build software that way.
 
software sale is a scam.
It hooks the client with 80% features the client wants. It is usually full of functional bugs, performance problems due to design, architecture or maybe just immature code of entry level programmer.
Then once the client buys it, then there is another story of fixing the bug behind the scene, re-architected secretly. In the mean time, give the client some hotfixs for them to dream on.
 
Post a Comment




<< Home
Reg Braithwaite


Recent Writing
Homoiconic

Share
rewrite_rails / andand / unfold.rb / string_to_proc.rb / dsl_and_let.rb / comprehension.rb / lazy_lists.rb

Beauty
IS-STRICTLY-EQUIVALENT-TO-A / Spaghetti-Western Coding / Golf is a good program spoiled / Programming conventions as signals / Not all functions should be object methods

The Not So Big Software Design / Writing programs for people to read / Why Why Functional Programming Matters Matters / But Y would I want to do a thing like this?

Work
The single most important thing you must do to improve your programming career / The Naïve Approach to Hiring People / No Disrespect / Take control of your interview / Three tips for getting a job through a recruiter / My favourite interview question

Management
Exception Handling in Software Development / What if powerful languages and idioms only work for small teams? / Bricks / Which theory fits the evidence? / Still failing, still learning / What I’ve learned from failure

Notation
The unary ampersand in Ruby / (1..100).inject(&:+) / The challenge of teaching yourself a programming language / The significance of the meta-circular interpreter / Block-Structured Javascript / Haskell, Ruby and Infinity / Closures and Higher-Order Functions

Opinion
Why Apple is more expensive than Amazon / Why we are the biggest obstacles to our own growth / Is software the documentation of business process mistakes? / We have lost control of the apparatus / What I’ve Learned From Sales I, II, III

Whimsey
The Narcissism of Small Code Differences / Billy Martin’s Technique for Managing his Manager / Three stories about The Tao / Programming Language Stories / Why You Need a Degree to Work For BigCo

History
06/04 / 07/04 / 08/04 / 09/04 / 10/04 / 11/04 / 12/04 / 01/05 / 02/05 / 03/05 / 04/05 / 06/05 / 07/05 / 08/05 / 09/05 / 10/05 / 11/05 / 01/06 / 02/06 / 03/06 / 04/06 / 05/06 / 06/06 / 07/06 / 08/06 / 09/06 / 10/06 / 11/06 / 12/06 / 01/07 / 02/07 / 03/07 / 04/07 / 05/07 / 06/07 / 07/07 / 08/07 / 09/07 / 10/07 / 11/07 / 12/07 / 01/08 / 02/08 / 03/08 / 04/08 / 05/08 / 06/08 / 07/08 /