QUOTE (RaGhul)
So what if it's a beta? I find that software produced by just one person is usually better put-together than software from alot of "name-brand" corporations (i.e., Microsoft, Ahead Nero, Roxio, etc...) Too many cooks spoil the broth, I guess. If I find anything, though, I'll be sure to post it.
In the end it's all down to how the project is managed. Most larger projects are
divided into sections with one individual or team being responsible for each
section. I've produced some very high quality software in this way and some
absolute disasters.
One of the most enduring problems I've had over the years is getting programmers
to stick to the specifications. Almost all of them have a "better way" to do
something or think something requested by the client "won't work" or "isn't
necessary".
With a project like nLite where a sole developer has absolute and undiluted
control, the quality of the product reflects the skills and dedication of the
individual.
Compare this with one case I had where an individual programmer didn't like the
interface specification he'd been given and wrote his own. Naturally this meant
his work wasn't compatible with that being done by others and to compound
matters he refused to rectify this stating that everyone else should use his
design as it was "much better than that s**t".
Rectifying that put us three months behind schedule which didn't look good at
project review meetings. I didn't tell the client this of course

I explained
he had fallen ill and had to be replaced while quietly (and desperately) trying
to get senior management to take the matter seriously.