"Your product is awesome. It's exactly what will change the world of programming and community editing."
— Joey Stanford
Software Developer & Blogger
"I've prototyped enough of a collaborative environment to know that local editing is the key, introducing a potentially nasty merging problem if two people's edits clash. I believe UNA solves this well... I wonder if this is a Clayton Christenson-style disruptive innovation. The elements seem to be in place. The basis of competition is shifting from individual productivity to fine-grained, real-time collaboration."
— Kent Beck
Father of Extreme Programming

Comparisons

To address the quality problem, the software industry has developed a battery of quality practices. These practices are designed to either simplify programs, so they are easier to change (design theory training, code ownership), or to make the consequences of changes to more obvious so that defects can be spotted earlier in the development cycle (code reviews, test-driven development, unit testing).

The UNA Paradigm recognizes the importance of these quality practices, and attempts to improve on them through the power of collaboration. The interactive table shown below overviews a variety of quality practices, and explains how the UNA Paradigm takes them to new levels of efficiency.

Continue
"UNA is a special platform... I usually hate group collab on code and design because the communication and miscommunication gets in the way. UNA is different because the collaboration is weirdly seamless and actually real-time - you all see the same things, you chat inline, code completion just works, everything is tracked, and never once does the group feature take precedence over just coding."
— Russell Foltz-Smith
President at Crossroads Access
"He worked from his computer halfway across the country from me, and I worked from mine, and it was just as effective as if we had been in the same room... To me, this was unprecedented, since it cut coding time by at least half. We were able to check each other's code as it was being written, so debugging was no problem at all."
— Will Kraft
Editor at ADTMag