On 14 mai 2012, at 18:28, David Kastrup wrote: > "[email protected]" <[email protected]> writes: > >> For me, it is faster to write a lot of kludgy code, see what it >> breaks, and then write good code [1] rather than trying to write good >> code from the get-go. So cheap regtests definitely help. > > That sounds uncomfortably like: "It's ok to design stuff above one's > head since we have a procedure for finding most of the easy to diagnose > bugs." > > There is a rule of thumb: you can debug code at about half the > complexity that you can design it. If you design at the limits of your > capacities, you will not be able to debug your code. > > And this sounds like you think we have mechanisms helping with designing > code beyond the limits of your capacities. >
No, I mean that my capacities are not static but dynamic and only grow when I see how things work, which often times comes from seeing how things fail. Cheers, MS _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
