Thanks to the magic of Twitter @Malarkey sent a very curious message about this error message:
So, the calendar can’t be used because the javascript that’s supposed to handle it was made for the Netscape Navigator browser which I imagine no one thought would ever ever go away. Unfortunately it went away in March 2008, after years of almost nil market share. Someone must have thought that people actually bothered to install the gazillions CDs that AOL polluted the world with for about a decade.
Unfortunately that was not the case and hardly anyone has used Navigator since 2002, and so what could have been seen as a bold move by the developers betting their all on the success of one single browser now survives solely as a curious error message that I think could also be a haiku.
On the other hand it could be that the error message should be “The developers of this site are either too stupid or too lazy.”
So, kids, let this be a lesson to you: don’t develop for a single browser, make sure your code degrades gracefully and, if you are the website owner, check your websites more often than once every five years, preferably with what people would most likely be using to see it.
Recently some guy pocking around the innards of his new iPhone 3G found a little piece of code that seemed to do something like stop the phone from running whatever piece of software Apple didn’t want it to run. It was quickly named a “Kill Switch” although no one knew for sure what it would do.
Turns out that it actually is a Kill Switch. The bad news is that it’s not something useful, for example it won’t allow you to kill the people in front of you in a line, like that lady who is paying her weekly grocery shopping with pennies, but what it actually does is stop the iPhone from running whatever software Apple doesn’t want it to run. Steve Jobs says that it would be irresponsible not to have one, the reason why is easy to see, after all only those developers who have paid for the privilege to develop for the iPhone are able to upload their wares to the iTunes store, which is the only place from where you can get software for the iPhone, and it’s not like the Apple people spend weeks reviewing the submitted software before posting it on the site. Oh! wait, they actually spend weeks reviewing the submitted software.
Apparently this is not enough and Steve needs more control over your iPhone, making sure you are only running safe and preapproved software; after all, you were naïve enough to buy an iPhone, God only knows what dangerous crap you can be suckered into downloading by giving it a bit of a shine and putting a vowel in front of its name. It also gives Jobs the option to outsource the software review process to underpaid 10-year olds in Vietnam in the future and if one of those kids misses something crucial, maybe he didn’t have breakfast that day… or month, then it’s no problem because Apple can still deactivate it remotely after firing the kid.
You see, by getting an iPhone you have also become part of a very exclusive community, one that is kept isolated from the outside world, one in which not anyone can make changes or improvements without prior approval, where there are people making sure you stay within the predetermined limits for your protection, and where you can be reasonably sure that all the other neighbours will be of a similar stature and position in life. Of course, you have plenty of freedom, you can change the colour of the screen and have different ringtones, so your iPhone will be completely unique… but not too much, otherwise it’d be just weird.
Oh, did I mention that thanks to the GPS the iPhone now knows where you are?
Today is TRIEC away day at the Toronto Islands where we talked about the relationship of Maytree with TRIEC, future Maytree projects that involve TRIEC in some way and an update on the TRIEC programs. It was a bit sad for me because this is the last away day I enjoy with the TRIEC team before moving 100% to the Maytree site.
Andy Rutledge writes in his blog about how he feels that educational institutes are not doing a good job currently in forming good web designers in their graphic design programs. I think he is totally right, specially on his recommendations about how students can overcome this and the four fundamental areas where they should fill the gaps.
The Employable Web Designer should be required reading for anyone who is thinking about developing web sites professionally, whether they are graphic designers or not. However I would go as far as to say that much of the reason why graphic designers are not being well prepared as web designers is because both are different disciplines, just as graphic design is different from interior design or industrial design. Specially for those technological areas that Andy points to as omissions in the graphic designer curriculum, the ones about html, css, affordance, usability, etc. are what makes web design differ enough from graphic design to be considered as a discipline of its own and not a subset or specialization.
As technology develops and the variety of uses for a website becomes greater these differences will be more and more evident. RSS feeds, mobile devices, APIs, microformats, readers for the sight-impaired, etc. already demand a unique set of qualifications and knowledge from a web designer, in many ways different from the one required as a graphic designer.
Although the principles of graphic design apply to parts of a website (namely the interface) there are many other things to consider when creating a website that go beyond the interface and into concepts of information architecture, knowledge management, usability and others. The faster the web designer recognizes these fundamental differences, the more marketable she or he will become.



