Re: Bugfixes in Scarab are hard

------=_Part_2332_13636147.1244373529988
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable

> I'm all in favour of 'fail fast'. The faster the code fails, the
> easier is it to find the bug and fix it.=20
>=20
> I also think that Scarab shouldn't have to deal with buggy data in the
> DB. Scarab is the master of its DB. If there is bad data in the DB it
> was caused by a bug in Scarab.

This makes Ronny, and as far as development goes I absolutely agree with
you. Do we take the same approach to production systems though?

What about keeping the checks for inconsistent or null data in the code
but always prefixing them with an *assert* statement so that in
development environments it always "fails fast".

Developers live in the harsh world but production systems get soft
fluffy pillows.

~mck

--=20
"Driving ambition is the last refuge of the failure." Oscar Wilde=20
| semb.wever.org | sesat.no | sesam.no |

------------------------------------------------------
http://scarab.tigris.org/ds/viewMessage.do?dsForumId=3D455&dsMessageId=3D23=
60076

To unsubscribe from this discussion, e-mail: [[email protected]=
.org].
------=_Part_2332_13636147.1244373529988
Content-Type: application/pgp-signature; name=signature.asc
Content-Transfer-Encoding: 7bit
Content-Description: This is a digitally signed message part
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEABECAAYFAkorop4ACgkQkdPrePiuutNMbgCg/FXyOPyAzB4aPr7Xho4D3iZu
XJAAoLDUwBPtktCUuXeqGtBPWAV0xBQP
=MU/p
-----END PGP SIGNATURE-----

------=_Part_2332_13636147.1244373529988--