| «« Spec-tacularly Productive Weekend | Object-File Persistence Layers and Durham »» |
|
About
I'm Ryan Lowe, a Software Engineering graduate living in Ottawa, Canada. I like agile software development and Ruby on Rails.
I write this blog in Canadian English and don't use a spell checker. Typos happen.
Projects
» Full-time Ruby on Rails freelancer
» Full-time with Rails since May 2005 » Former committer for RadRails (now Aptana) » I also have a few Rails side-projects in development: 1. wheretogoinTO.com Toronto nightlife 2. Hey Heads Up! TODO list and sharing 3. Layered Genealogy family history research 4. foos for foosball scoring 5. fanconcert for music fans (on hold) Hiring Rails developers? I can telecommute by the hour from Ottawa, Canada »» Email: rails AT ryanlowe DOT ca
BulletBlog
Now hosted on Hey! Heads Up -- check it out!
Syndication
Pings
Recent
Derek Lowe's (Ryan's older brother) words at Ryan's funeral
blog@ryanlowe.ca no more Forging Email Headers: Good, Bad or Ugly? Sarcastic Dictionary (Part 1 of Many) Tags Hierarchies Twisting Rails is Risky Business Risky Business? My Take on Early Alphas Whoa, it's August 2007 Closing Comments A Postscript to "Growth at the grassroots" »» All Blog Posts
Linkage
del.icio.us/ryanlowe
technorati/ryanlowe.ca/blog Aurora Roy Jim Andrew Trasker Travis Kibbee Karen Dr. Unk Ayana Van Bloggers Joel Spolsky Robert Scoble Tim Bray Dave Winer Raymond Chen James Robertson Ruby/Rails Bloggers rubyonrails.org weblog David Heinemeier Hansson Dave Thomas James Duncan Davidson Mike Clark Jamis Buck Signal vs. Noise Tobias Luetke Amy Hoy: (24)slash7 Jeremy Voorhis Eclipse Bloggers Planet Eclipse EclipseZone Luis de la Rosa Eclipse Foundation Kim Horne Billy Biggs Ian Skerrett Mike Milinkovich Bjorn Freeman-Benson Denis Roy
Archives
|
The Dilution of Beta
Forgive the rant, but it's interesting that there's so much attention being given to the term "beta" when it comes to software. This could be yet another great example of how insular technical people can be, not that we needed more examples. The vast majority of people -- and it's vast -- had no idea what beta meant in the first place. None. So why is such a big deal being made now? I'm not quite sure. Maybe it's because developers are really concerned about covering their asses. And what better way to cover your ass than by saying your released software is beta? Or by giving it some version number less than 1.0 and hiding that version number in the Help menu. Then if people run into catastrophic problems you can say "didn't you see you were using Product beta version 0.94? Didn't you read the EULA?" Yeah right. It's all meaningless. People won't and do not care about version numbers or alpha, beta, gamma or even epsilon. If you release software people will use it. They'll inadvertently find 1000 different ways to break it. They'll pack it in their kid's lunches and use it as a hat on cold days. Maybe it will even do what it's supposed to do. Once it's out there though, it's out there. If the software is free they might forgive you if it eats their homework or makes a mess on the rug. If they ever run into a catastrophic data munging bug in something they paid for they'll probably be less forgiving. Until they read the cover-your-ass EULA they didn't read in the first place they might even consider suing you. Labels like beta on software are completely meaningless to almost everyone but a very small minority of keyboard-wielding geeks. Unless you can be absolutely positive your audience is only other geeks who know how to use a test release, care should be taken with each release you put out. Once you make your software publicly available -- even a so-called alpha or beta -- people will grab it and break it. You have released it. Like many other people, I've only pointed out the problem -- I haven't come up with a solution. Blaming users for being ignorant of industry jargon is not a solution. Blaming companies for messing up the meaning of industry jargon no one else cares about is not a solution either. </rant> Posted at February 14, 2005 at 04:58 AM ESTLast updated February 14, 2005 at 04:58 AM EST Comments
The thing is, is that version numbers and the word "beta" don't really mean anything. A quote from my girlfriend pretty much sums this up: Firefox is only 1.0? I've never seen a program at 1.0 before. And that's pretty much it. Because even though it's only 1.0, it's at least as good, and I'm sure better in many ways to let's say, Internet Explorer 6.1. So you get this symptom where by developers end up fudging version numbers, *cough* Java 5 *cough*, in order to make their software seem better. The word beta is purely subjective. I've run beta software that crashed anytime something even remotely unexpected happened. I've also run beta software that, as far as I could see, had no bugs, or at least not more than the average program which is not beta. » Posted by: Kibbee at February 14, 2005 08:59 AMGreat post, Ryan :^) It's true. To add rant-balance, the use of the term can be useful in coaxing reluctant product managers into allowing select customers to actually get their hands on your work. In some cases, this may be the only way to get this kind of feedback. » Posted by: Ben at February 17, 2005 01:08 AMBen: true, beta is synonymous with "almost ready" or "feature frozen" among geeks. But to other people it means nothing. I like the terms "test release" or "release candidate". RC I like less because people go "huh?". At least with a "test release" people know exactly what they are getting themselves into. » Posted by: Ryan at February 17, 2005 10:00 AM
;-) Hehe ... sneaky. ;) » Posted by: Ryan at March 10, 2005 09:58 AM |