Skip to main content

When is a Beta a Beta

This has been discussed numerous times before but Windows Vista brings it up once again.

I went on a rant on this on this week's FoxShow related to user interface design but I agree.

"As I pointed out last week, it's not a beta until it's feature-complete. Microsoft is showing off a prototype, a demo. When they have the new UI in place, and lock down the features they plan to actually ship, then it is time for beta evaluation and testing."


Ted's Radio Weblog

Comments

Anonymous said…
I have to dissagree with this. The primary purpose of beta testing, at least as my company does it, is to get feedback from real world users in real world situtations on feature sets and usability. Secondary would be performance and stress testing in a live environment. Finding "bugs" is only a minor reason to send a beta version to customers.

So, if you have locked down functionality and design you might as well call it a release candidate.
Andrew MacNeill said…
Bob,

The piece in "quotes" were from Ted's original post - I was quoting as opposed to giving my entire view (which was done on the Rant )

I agree with you that it's certainly needed to get feedback from real world users but wouldn't you agree that you should generally be interface-complete for the beta stage?

Agreed that for the an Alpha stage, the interface shouldn't be locked down but by the time you get to beta, the interface should be pretty much set.

I completely agree with the performance and stress comment.

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction