Ken Tilton <firstname.lastname@example.org> wrote:
| Duane Rettig wrote:
| > ... anyone who does not do testing at various steps along the design
| > _and_ maintenance/redesign process is just begging for trouble.
| I thought that is why we occasionally move code into production. There
| is no substitute for real world conditions, if you ask me. Oh, sure, I
| could sit here spinning my reals trying to reassure myself my code is
| correct, but it's just no good, is it? I'll never think of everything
| anyway, So why hold up a production release?
Just a couple of recent examples why not: ;-} ;-}
Deploy first, test later
Arizona State University decided to act like a 90s-style .com:
deploy first, even if the software is buggy, try to cope with
the problems, and fix the code later. ...it didn't work very well.
3,000 employees were unpaid or underpaid, and the backup procedures
couldn't scale by nearly enough.
LAUSD payroll fiasco
...a similar fiasco has been afflicting employees in the
Los Angeles Unified School District (LAUSD) since early this year.
Some eight months after "going live" with their new payroll
system, employees are still receiving incorrect paychecks or no
paychecks at all. The administration does not yet know whether
correct W2 forms will be issued in January. Employees retiring
cannot get correct pension benefits.
Rob Warnock <email@example.com>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607