[PetiteCloud] final set of design philosphies
aryeh.friedman at gmail.com
Thu Feb 13 07:53:01 PST 2014
On Thu, Feb 13, 2014 at 10:34 AM, Michael Thoreson <m.thoreson at c4labs.ca>wrote:
> On 13/02/2014 8:51 AM, Aryeh Friedman wrote:
>> 1. There is no such thing as a free lunch in cloud computing. Namely
>> you can not create resources or anything out of nothing. The do need to
>> run on real (non-virtual) hardware at the end of the day.
>> 2. *ALL* problems have simple and elegant solutions. If the one you're
>> currently working on one does not then redefine it until you find one.
>> 3. Time and resources are finite so only focus on critical functionality
>> finding it's hands into end-users ASAP. If we get that right then the
>> rest will follow. If we get it wrong then nothing can be built on it. But
>> at the same time it is better have something out the door then have it
>> perfect and never leaving the lab.--
> Agreed. However we can't sacrifice polishing features and fixing bugs to
> the point that it becomes a project only worthy of Microsoft ideology of
> push it out the door and fix it later.
We call this the "no broken windows" rule... namely for any terriary
version unless it is known to be currently unsolvable (like the linux as a
host issues) our requirement for release is zero bugs in known_bugs.txt and
every known bug found by us or reported is put there... see my comments on
the other post but I think 408 (always growing) automated tests are a good
back stop (the idea of the tests is not to catch *NEW* bugs [for computer
science reasons that is certainly impossible] but to make sure old ones do
Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the petitecloud-general