It certainly has that feel... that you can make statements (express constraints) about a given configuration item — in any order — and the final result falls out (having satisfied all constraints or "errors").
> There have never been things like this that just grow in complexity forever. The evolution of the species? Homo sapiens seem rather complex. Perhaps what we'll see is that over time, large portions of what have been…
Nice hypothesis! Reminds me of the shearing layers from Foote & Yoder's "Big Ball of Mud" — http://www.laputan.org/mud/mud.html#ShearingLayers
Another feature of the model could be stability of product vision. Is there a correlation between the half-life of committer membership and that of the code? How has the problem space of the product changed over time?…
I wish we could capture the "inventiveness" of a particular project — how well the problem was understood when the project initiated. There had been _many_ *nix'es by 2006, so the territory had significant prior art and…
It certainly has that feel... that you can make statements (express constraints) about a given configuration item — in any order — and the final result falls out (having satisfied all constraints or "errors").
> There have never been things like this that just grow in complexity forever. The evolution of the species? Homo sapiens seem rather complex. Perhaps what we'll see is that over time, large portions of what have been…
Nice hypothesis! Reminds me of the shearing layers from Foote & Yoder's "Big Ball of Mud" — http://www.laputan.org/mud/mud.html#ShearingLayers
Another feature of the model could be stability of product vision. Is there a correlation between the half-life of committer membership and that of the code? How has the problem space of the product changed over time?…
I wish we could capture the "inventiveness" of a particular project — how well the problem was understood when the project initiated. There had been _many_ *nix'es by 2006, so the territory had significant prior art and…