*Grumble*

Okay, so my blog isn’t big and it’s still hidden in a sub-domain, but it’s constantly changing based on my needs and ideas – be it design, layout, or content.

Everything, as you say, is in constant flux and evolution and thus it makes labelling any such site as a ‘Beta’ as totally null. The only place I’d expect to see it it when a program is being coded, i.e. before the first full and stable release is made.

Life is beta. When it’s finished, you die. Stay in beta!

Hell, I think from now on when someone has a complaint to say about me I’m just going to tell them I am in beta because I still have some bugs to work out and some Scrivs’ features that need to implemented. You think that will fly with the ladies at the bar? Don’t think they would be too impressed that I’m only at Scrivs 0.48 right now though, but it is worth giving it a shot.

Best thing I’ve heard all year! I’m going to tell everyone that I am in beta too, and I’m going to invite people to join my open beta test.

Being in BETA serves two clever purposes: firstly it creates a kind of underground buzz where people think they’re getting a sneaky preview of something before it’s released – they think they are ahead of the game; the second purpose is that if a product is in BETA you don’t need to offer support for it – it’s a caveat against all the things that might possibly not work.

I can assure you Google will already have thoroughly tested its products before they get released to ‘BETA’ – its just a marketing tag.

Is that your alcohol intake level? Honestly, I find it that when my brother (I don’t drink) goes to a bar his alcohol intake level needs to be around 1.4 just to double the ladies, otherwise for some strange reason no one talks to him…

Hmmmmmm…

Since the Web is dynamic by nature, things are always changing. Something is being updated, tweaked, refined, or totally reworked until the latest and greatest, must have technology arrives at which time it all starts over.

There are too many new and cool designs, features, scripts, and technologies that we always want to implement. If we didn’t implement some of those features our site/application would become dated and thus unused. So our sites are in a constant state of upgrade and or change, and so maybe really never in a state of final release.