Collateral damage
http://en.wikipedia.org/wiki/Collateral_damage

Deze blog en alle andere op blogspot waren down:

Het succes van gratis bloggen, veroorzaakt een behoorlijke drukte op de servers van www.blogspot.com
Noem dat collateral damage: ten onder gaan aan het eigen succes.
En dan de reacties van die bloggers:
http://groups.google.com/group/blogger-help-troubleshoot/browse_thread/thread/c308c8e291bd5177/d402ad2af8c0e660?lnk=raot
Quote:
While there have been no offical response from Google, the owner of
Blogger.com, one technician was overheard to say, "Blogs, does anyone
REALLY read this stuff?"

Als alternatief dan maar de nieuwste betas gedownload:
FireFox 3.0Beta3 en IE 8Beta
Het risico van een beta is dat er nog bugs inzitten.
Deze blog editor geeft serieuze scriptfouten in IE8.

En lees deze eens:
http://today.java.net/pub/a/today/2004/02/06/davenandy1.html
Quotes:
Taking Responsibility
In a very structured environment, people tend to abdicate responsibility. People say, "It's not my job anymore. My boss is telling me what to do. A big master plan is given to me. I just have to do this module, and this module, and this module."

Fixing broken windows
The researchers did a test. They took a nice car, like a Jaguar, and parked it in the South Bronx in New York. They retreated back to a duck blind, and watched to see what would happen. They left the car parked there for something like four days, and nothing happened. It wasn't touched. So they went up and broke a little window on the side, and went back to the blind. In something like four hours, the car was turned upside down, torched, and stripped — the whole works.

Of: http://www.codethinked.com/post/2008/03/Reality-Driven-Development---Why-do-good-programmers-produce-bad-software.aspx
Quotes:
It's the fun part!
For most of us we started off hacking away at software in our younger years before we ever knew what specs or customers were.

We think we already know what needs to be written.
By the time that most programmers hear about a new piece of software that needs to be written they are already designing it in their head.

We aren't agile.
We think that specs and requirements are something that you only get before you build software.

Dat zet je wel aan het denken!


Klik op onderstaande afbeelding (moving gif):