Hi William,
The idea is not to spread bad and untested code, the idea is to review our our expectations about testing. Clearly, without enough feedback, we can't set a "black hat" team (hey, sounds like a Joel Spolsky's advice :)). I was first thinking about really, really hard test everything, just to be sure first releases were good enough. And eventually decrease tests as we go further in the project. But we can do the contrary (read: review our expectation): test what can be humanly tested by very busy human & developpers (read: not hard testing), and eventually, *if needed*, increase the level of testing. This is an optimistic approach: what previously worked should still work according to the new involved changes. The problem is to evaluate which changes may break working tests, that is "big changes" (but we here are all experts :)). Building a user base is more important. Of course, it won't happen with bad code, but it certainly won't happen too if we spend 50% of our very busy time testing things again and again. Once we do have an active user base, we may be able to enroll testers, a "black hat" teams, and run a contest. Cheers, Seb 2008/12/19 William <[email protected]> > > Greetings, > > "Free code" is great if you can afford it. It is very costly. Either > to you, the developers, or the end-users, who try to make use of it. > > I urge you, please, do not publish untested code. The world has way, > way too much bad code already. Please don't add to it. > > Software projects spend 50 percent of the time testing. So you may as > well plan for it. If you don't personally enjoy testing, then enlist > others to help. Start a "find the bug" contest. Create a "black hat" > team, whose job is to find and squash those bugs. Make it a > competition -- the designers/implementers versus the "testers". > > The whole purpose of the original JAL "blink the led" web page is that > these are examples that are known to work every time. They are > hardware diagnostics. > > Every JAL board I have ever built has run a HEX file from the JAL > "blink the led" page, first, and also whenever I am debugging, to make > sure that the hardware is at least alive enough to blink the led. > > William > > > > On Dec 18, 2:02 pm, Rob Hamerling <[email protected]> wrote: > > > > I tested a couple of the latest blink samples with the latest device > > files. I didn't test 'm all and therefore I cannot guarantee that all of > > them work perfectly. But what the hack? It's free! If somebody is not > > satisfied with Jallib material ask him what he paid and what he would > > loose by not using it. > > > > > > -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
