In reply to New D7
CodeSatori
What I can't wrap my head around is why there are so many bugs. When I code, and trust me I have coded a whole lot of software similar to Dolphin, the bug-fix phase will take about 10-15% of the total development time (except with cross-browser HTML/CSS with certain browsers).

What's the design approach here? Do the developers just shoot in from the hip all sorts of features in whatever manner and shape, and at one point declare it Feature Final and start figuring out what the heck exactly they see more put together?

That's pretty Frankenstein for an approach, but I fear quite on the mark, just as was my note two few weeks back on July 10th bringing us an Alpha 2 labeled as Beta.

Why not code something that works from the outset? If there are tons of bugs, it indicates 1) the design of the base framework is bad, 2) the development is disorganized and unstructured, or 3) the developers lack in skill. I like to think it's primarily the first, and to an extent the second, which are both something relatively easy to remedy with the right action plan.
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.
PET:0.035858869552612