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.
August 15, 2005 at 11:45 AM
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.
August 15, 2005 at 12:03 PM
Lorena said…
This is a great bllog
January 13, 2025 at 5:03 AM
Post a Comment

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .
4 comments
Read more

From Writing to AI: the pattern repeats itself

When I was ten years old, my dad bought a computer and, thanks to an advertising supplement in a Superman comic I read, it was a TRS-80. A month later, he dragged the entire family (my mom and brother were not the most enthusiastic) to a class at Radio Shack teaching how to use microcomputers. At the time, I understood why my mom wasn’t that excited: the computer was yet another gadget in the house. But today I find it fascinating. My mother went to Vassar in the 50s. She learned how to type — not a common skill at the time — but it opened doors. Her ability to communicate effectively led her to a career in adult education and later communications work with the CBC (Canadian Broadcasting Corporation). This isn’t a nostalgia post. Today, the ability to use artificial intelligence, be it through Copilot or simply writing the right prompt, is becoming a critical skill. But is it really that novel? In the 1500s and 1600s, the printing press gradually made reading accessible beyond cler...
Post a Comment
Read more

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...
11 comments
Read more