Now that might seem like a strange thing to say but if you don't fail at some things then it means that "you are not trying hard enough".
If we always take the "safe" option that has guaranteed success then we will never truly move on and progress.
When I started this blog, and it took a lot of convincing to do it, I took a decision that this blog would not be the usual Joomla blog.
My intention is to write articles that are of interest to a wide audience and to not only provide "tips and tricks" and republished "product news" but also to write articles that are "challenging and make you really think".
On Friday I did something that I never thought I would ever do. I bought a Mac. To be more exact I bought one of the new aluminium Mac Book Pro.
I've been a PC user for more years than I like to remember and although I have dabbled with OS X on occasions in the past I have never before succumbed.
Right now I feel a little bit like Adam being tempted to take a bite out of the apple by Eve, I just hope it doesn't lead to the same result.
So what made me take the leap?
Release early - release often or release once when it is ready?
It is often quoted that an open source project, like Joomla, should release early and release often as this is the best method to find bugs and provide new features.
However I believe that is an overly simplistic approach and does not translate to real world use in all but the simplest, single use projects and definitely not for Joomla.
As soon as you have a piece of software that third parties extend and build upon you run into serious issues.
In the last few weeks I have received numerous approaches from people who claim to have the next big thing.
With their idea they are going to storm the web and it will soon be the hottest thing, bigger than twitter, skype, youtube etc
So what do they want from me?
I was recommended an extension for joomla this week via twitter, so naturaly I had a look. The link provided to me was to the Joomla extensions directory where I saw that the extension was both licenced under the GPL and non-commercial.
I read the description and the reviews and it sounded promising so I hopped over to the developers web site to download it for myself and have a play.
And that is when my blood started to boil (again).
You would think that is a stupid question. Of course every web master wants their site to be usable by the largest number of users. And no web master wants to break the law, and there are many laws around the world that attempt to create an equal playing field.
Yes it is true that to create some of the cooler aspects of a web site in an accessible manner can be very hard but there is NO EXCUSE at all for a site to missing ALT tags.
Handing over a web site to a client is always a satisfying feeling but is it always finished?
Of course you should always aim to complete everything on the client's brief and to their specifications but are there times when it is best to hand over the site when you still have some work to do?
Recently I have found more and more that I am handing over web sites that are perhaps only 90% complete or that have temporary solutions in place.
Do we need vowels in order to read effectively?
Neither arabic or hebrew use vowels in common use so are they really necessary?
Does our brain automaticaly fill in the missing information for us?
I've got another new toy.
I was having a little trouble today to think of a blog post that would actually be interesting.
I was going to write about my experiences testing an SVN a copy of joomla I. 6 but the current state of the svn made that unproductive.
