>>To be clear about it, I'm not advocating Thundering Train Programming as THE technique for whole applications. But I have the feeling that certain, as such identified, parts of applications can be safely done using this technique. A crash in such a part is, well, an error message and eventually some data damage.
The data and the code will need some repair indeed. But is that really always a bad thing?>
>Peter;
>
>It depends! Does the data have value? Can the customer wait for a repair?
Who will be blamed? In my example probably the user who erased the table. Or else the functional designer.
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
