diff options
| -rw-r--r-- | spm-slides.tex | 20 |
1 files changed, 18 insertions, 2 deletions
diff --git a/spm-slides.tex b/spm-slides.tex index 32ee615..bb71fc5 100644 --- a/spm-slides.tex +++ b/spm-slides.tex @@ -502,6 +502,7 @@ A new release is like a booster shot to boost users' interest. Make sure you give people at least one Big booster shot yearly. +However, too-frequent releases are considered not necessary for mature products. Why? %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \foilhead{Joel Test} @@ -613,6 +614,7 @@ Make the company successful. Make themselves successful. +Employ only one employee for a consistent architecture at early days. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% \foilhead{Software demo} @@ -1160,8 +1162,22 @@ Release notes: \url{http://wiki.inkscape.org/wiki/index.php/Release\_notes} {\bf Development status should always reflect reality}. -Conservativism pays off in the long run; it's always better for the -software to be more stable than the user expected than less. Alpha (first release, with known bugs). Beta (serious known bugs fixed, asking users for detailed feedback). Production. +Conservativism pays off in the long run; it's always better for the software to be more stable than the user expected than less. Alpha (first release, with known bugs). Beta (serious known bugs fixed, asking users for detailed feedback). Production. + +{\em 10-year Rule}. \href{https://www.joelonsoftware.com/2001/07/21/good-software-takes-ten-years-get-used-to-it/}{Good Software Takes Ten Years. Get Used To it}. + +Lotus Notes. 5 years' work before 1.0, released in 1989. From first line of code in 1984, to 10m users in 1995, 11 years have passed. +Oracle DB (1977). Microsoft Word 1.0 (1983). All selling billions of dollars yearly. + +Lessons: (i) it takes many years before your software is good enough and serious enough for people to buy it. The Overhype syndrome. (ii) No time to add many wanted features to 1.0 in a short period of time. The Get Big Fast syndrome. (iii) When it is done, it is {\em done}. Additional features are not essential. (iv) ``We’ll Ship It When It’s Ready'' syndrome. + +Keep 1.0 quiet. + +We are not writing software any faster than before. We just release more often. + + + + {\bf Downloads}. Downloadable as source code. Conforming to standard build and installation methods. Otherwise, someone visits a web site, downloads the software, tries to build it, fails, gives up and goes away. |