The world is changing. At some point in the future, says Ray Kurzweil, computers will be more intelligent than humans. He thinks it will happen in the year 2045 to be exact. That’s a scary thought, but he could be right. Many say he is the smartest man in the world.
But today I realized that Salman Khan is ahead of him. Khanacademy is an online tutorial for everything including math, biology, economics, chemistry, physics, history, and more. And Khan made all videos himself.
But not only did he do that, he is expanding at an exponential rate, to offer his courses to classrooms. And that could revolutionize education.
And all of that… for free, because he is filthy rich anyway, and doesn’t care about making more.
The value in a social network lies in social. So the friends should be people you have met in real life and value in your social circle, which revolves around your life, not your business. A page is a business tool so that is what you should have.
The cap may be nonsense, but unfortunately there is no way for Facebook to validate that you actually know the ‘friend’ personally.
One other side-effect in which Facebook bites it’s own hand is that apps and games (OK and businesses) thrive by the amount of ‘friends’ you have. That is an incentive to make fake friends. I started to play CityVille only to find out that none of my friends did. If I were true to Facebook’s dogma I would quit playing or be an obnoxious friend who would evangelize CityVille to all my friends all the time, until they unfriend me. Now I play it happily with over 30 fake friends whom I’ve never met. I even block them from my wall, as I don’t want them in my real social circle. Once I stop playing CityVille I will quickly unfriend all these people.
Still, I fully agree that Facebook should work on a solution, which in my opinion is definitely not removing the cap but some way to have people in your network for a certain purpose, and have great distinction in how you treat and communicate with them.
All the positive talk about Twitter’s agility: don’t become so vigilent, or should they also remove the 140 character cap!?!?!?
I have always been appalled at the nomenclature of new applications: Friend and Like come to mind. I call them ‘close-related-marketing-profile’ and ‘increase-marketing-keyword-potential’.
Jeffrey, you don’t get to 5000 friends without making a few enemies 😛
Jeff Zeldman writes a compelling argument for Readability 2.0. Readability is an open source tool that transforms a web page to a reading page, removing all clutter, including ads. Readability 2.0 will now actually pay the content providers (website owners) every time a user switches on Readability to read their pages.
At first I thought: Does this mean publishers don’t need to sign up?? So they get an unexpected check from a seemingly philanthropic web company?? But after looking at the site, I realize publishers do need to sign up. And that, I think, makes it quite unpractical. Let me tell you why.
How about promoting Readability on a site with ads? That’s like saying: click here to screw with all our other clients. So that’s virtually impossible.
I believe we can divide the site owners in four groups
1. The small site owner, not being able to get advertisers easily, not making enough on Google Ads. They could promote Readability, but wait: there are no annoying ads on the page. Duh. What’s the point? Well, to be honest, they could litter the site with Google Ads and then have a shiny button that says : “don’t like ads? click here to remove them”. The user would then learn about readability, sign up and start paying.
2. The large site owner who is in a clinch with advertisers, and says: we’ll just move our whole platform to readability, @#$% you very much. You pay Readability, after which you get a ‘pro’ account which gives you access to more content. That would require a partnership with Readability I guess, unless there is a technical solution (checking to see if you are using Readability).
3. The large site owner who has littered the site with ads, who likes Readability too, but is unable to promote it, fearing the wrath of advertisers. There’s no way for this owner to put a button on the site.
4. Like Zeldman.com, the large site owner who is not in it for the money, or actually, makes enough doing other stuff and just uses the site for self-promotion. They don’t have ads, and using Readability is nice, but unnecessary.
I am dying to see some stats soon, so we can see if offering Readability instead of advertisement is a valid business decision. If it is, it will spread and transform the web. At some point Readability then needs to be taken over by a big player, or it will be simply sued to death by angry advertisers.
When we write for the web we most certainly write for the fast paced audience that has no time to read pages and pages of text. That’s a given, and it’s what sets it apart from writing for paper. The other characteristic is links: if you need to explain something, it’s easier to just link to wikipedia than to insert the actual text. Also you don’t want to infringe on copyright.
Let’s look at our goals for writing for the web:
Make it easy to read
Make it easy to use
Make it easy to find (search engine position or ranking)
Make it sell (in case you’re selling, but you’re always selling ideas)
Make it look good
Those goals are also connected to viewpoints from certain people: the writer, the usability expert, the SEO specialist, the sales representative and the designer. These fantastic four have to make sure the page adheres to all their standards. And here is where it starts to itch:
easy to read: plain fonts, short sentences, short text, clear message, bold, pictures and diagrams that explain difficult topics.
easy to use: minimal use of text, clear and large buttons, minimal use of design elements
easy to find: clear headings, short sentences, keywords in bold (not the same ones), no pictures required.
sell: everything leads to a buy, no navigation on cart page
look good: creative fonts, no bold text, plenty of non-illustrative pictures (preferably photographs) and design elements
In my opinion you should work from the outside in: make it look good, then make it easy to use, easy to read, easy to find and easy to sell, in that order. But as you make it look good (design process) you can of course have some consideration for the other aspects. It should also be noted that SEO is still voodoo, since nobody knows how Google really works. Also, search engines, in particular Google, change their ways of working constantly and they get better and better at identifying your pages. So don’t try to fool them, it’s not worth it.
There will probably always be a battle between usability experts and designers, because their worlds are so far apart. But to a modern web user something like useit.com looks like it was made 20 years ago and doesn’t instill trust in a user, something that is vital to sales.
Remember I may not be an expert in all those areas, but the ideas presented do come from the leading experts in these areas.
First of all, I hate the “Like” button. However, I have to be honest, I hated the “fan” button even more. Now I am not just being negative. Let me give you some background on this.
The Fan button
The first time I saw the “become a fan of ….” button on Facebook I didn’t know what to think of it. I started thinking, OK, so what am I a fan of. I soon realized it’s a very short list, that also changes over time: Rubik’s cube, Aikido, House, Monk, Rush, Led Zeppelin, and some others some to mind. But to say I am a fan of e.g. Harry Potter is quite exaggerated. So, reluctantly I clicked the fan button for “House” (the TV show, not just any house). The next thing I knew I found myself drowned in messages about (from?) my temporary favorite TV show. It’s just plain stupid. I do want people to know I like the show, but not get stupid messages all the time from it. So I stopped being a fan of anything else.
The Like button
I was happily surprised when Facebook decided to change the Fan idea to a “Like” idea, thinking they must have heard some voices echoing my thoughts. Unfortunately though, the button still does the exact same thing: squirting out a barrage of nonsense messages. I soon found out though that now it’s quite easy to hide those messages without losing your ‘like’ status.
Another thing I am fan of is Google Reader. Ever since I got a new PC I never felt like installing applications. I realized that even though compiled software is faster, and sometimes has really nice features, using online software just works anywhere, and is good enough for me. Also I have been moving around between computers more, so it becomes quite necessary to synchronize application status. But that’s another story.
Google Reader has had a “like” button perhaps even longer than Facebook (can anyone tell me if that’s true?). And since Google Reader doesn’t followup the click of a “like” with a barrage of nonsense messsages, I was happy to click “like”. After a while though, I found out that on the top of my ‘suggested reading list’ were a hole bunch of really stupid posts. I thought: “there must be something wrong with Google’s algorithm”. And then it hit me: Google uses the “like” button to learn what you want to read. But I had been using it all wrong. I clicked “like” usually when something was really, really funny. And so Google decided I was mostly interested in humor. And that’s pure BS. I like a joke once in a while, but not all the time, when there’s interesting serious news ahead. And it was impossible for Google to tell what I found really hilarious and what I found just plain stupid (a sense of humor is not a computer’s strong point).
So I revised my like-button-decision-making-process and was happily surprised when only weeks later Google had adapted itself back to a more serious note, and I could suffice with reading the top 50 or 100 items, and send the rest of the news to a peaceful death.
Still, I was faced with another issue: once in a while I read interesting news about natural disasters. But I found it morally appalling to mention to Google that I liked the fact that over 200,000 people died in Chili, or that dozens died in a freak accident. But I learned the hard way now it’s wrong to think that way, we have to redefine the “like” button to an “adjust-neural-net-weight”-button, even though that sounds a lot more complicated.
Now what’s next?
I am going to continue clicking ‘like’ for everything that I wish to associate myself with, or wish to receive messages about in the near future. My advice to readers: please realize that there is a commercial incentive to all this ‘liking’: ads will always be tailored to the user, wherever possible. And Facebook nor Google can do this properly when it doesn’t know what you ‘like’.
So far, I like where it’s going, though the wording is wrong in every single way.
I’d like to make a proposal for a new kind of programming (at least new to me, LOL). When I was studying back in the nineties I became interested in something called ‘sociocratic organization‘. This is a form of organization based on Cybernetics. Cybernetics is the study of systems with feedback loops. When you think of a thermostat in the room, it has a feedback loop. When it gets too hot, it cools, when it gets too cool, it warms up, and that way it keeps the system in balance. In computer programming we don’t deploy such features normally. We pray that all goes well, and that we didn’t forget anything, and if it does go wrong, the whole system usually crumbles apart. In web programming that’s usually a minor glitch, since just one page of our whole system breaks. In desktop computing it’s much worse. And in embedded programming it’s disastrous. Now instead of writing numerous unit tests, or mathematically proving our program, perhaps it would be possible to use this idea of a feedback loop in many aspects of our programming.
Consider you have to write a program that is to determine the best results for a search, similar to Google (but not as vast, so let’s say a small web site). We need to display what’s relevant to the user, but we don’t know what is relevant. So you just do a simple text search to find a record within a table. Now you check which of the results is clicked for this particular search result, and then you log the search term, and with it the clicked result.
Then a new user shows up and does the same search, and clicks the same result. You increment the counter for this result on this search in the log. After a while we should see our statistics in the table represent what people were searching for, and which records were ‘successful’ to them (at least they clicked it). Depending on these results you can now decide to alter the order of the search results, where the highest scoring record is put on top of the search results page.
Pretty nifty. I Googled it and found that Microsoft Research has written a paper on something similar. So expect this to Bing us soon.
What am I talking about? Client side “apps”, by which I mean browser based, server-less HTML pages, where everything is done on the client. Examples of such applications are CD Rom viewers, Touch Screen Console applications, and Information Display (like the train station screens).
Recently I got a request to make an Information Display. I started happily to look at how this would work using modern browser based techniques. After a couple of days of experimentation I must say that it was a wonderful journey, and I am convinced this technology will have a great future.
I have used the following technologies, and will explain hereafter how:
Excel serves as my database. It consists of worksheets of tabular data. The data is exported to an XML file using the XMLTOOLS addin, which you can find on the microsoft site. It is very loosely designed: when I need an extra column, I insert it and start typing. I will have to re-generate an XML mapping then, and export the contents to an XML file. The advantage: the person working with this ‘database’ only needs to know Excel, and how to click on a few buttons.
jQuery and Cycle
I added jQuery most and for all for the Cycle plugin. It allowed me to create stunning visual transitions for ‘slides’. The slides are actually simple divs in an HTML page.
I used CSS3 for creating nice looking gradients. Also I used CSS3 for zebra tables and drop shadows on images. Overall it means there is no need whatsoever for images to enhance the visuals. I think that’s how future web development will and should occur.
SVG and/or Canvas
Ultimately I decided to use SVG for both my static vector based images (floor plan) and my animation (a clock). The SVG animation actually looked better than the canvas one and I wasn’t very interested in modifying the default look.
For the floor plan I hunted for a good SVG or Canvas editor. What I found was Google Docs (!). Recently they added a diagram editor, that can export to SVG. The resulting code unfortunately looks like hexadecimal soup, but the good thing is you can easily modify the diagram on Google Docs and export again.
Right now my app only works in FireFox 3.6, and that’s just fine, baby!!
Note: I cannot share the application since it’s made for our organization, but if you need help in setting up one yourself just add to the comments…