Torno un attimo sul tecnologico. Mi piace questo concetto, e anche il commento di Tesugen
Kissing Frogs.
Kamen calls this kissing frogs an analogy that I really like. It's not until you get your hands on a potential solution that you are able to judge whether or not it will work. That's why the principle in XP is about trying the simplest thing that could possibly work once you try the simplest thing you can think of, you know whether it will work; and if it won't, you are in a better position to come up with other (simple) things that might have a greater chance of working.
In software it's common to decide for a particular solution, start to implement it, only to find that it wasn't good and then, instead of discarding it, you patch it up here and there until it works. The result is ugly, error prone and require more time to maintain.
You wouldn't get away with this in the physical world it's too obvious that it's the wrong frog.
[via Tesugen] via [Jinn of Quality and Risk]
Il fatto che spesso il software abbia dei problemi è che nel mondo "reale" i prototipi vengono buttati via, nella realizzazione di un programma spesso si aggiustano (una smartellatina qui, una limatina là) e si vendono. Talvolta è vero.
PS: XP nel post sta per Extreme Programming, non per il sistema operativo. 
9:32:27 AM
|