IBM announces the very first cognitive computing chips

Handpicked

 

From the IBM Research blog:

4. These systems won’t be programmed like traditional computers are today. Rather, cognitive computers will learn dynamically through experiences, find correlations, create hypotheses and remember – and learn from – the outcomes, emulating the human brain’s synaptic and structural plasticity (or the brain’s ability to re-wire itself over time as it learns and responds to experiences and interactions with its environment.)

5. To accomplish this new kind of system, IBM is combining neuroscience, nanoscience and supercomputing together to rival the function, power and space of the brain.

I find this stuff both incredibly fascinating and somewhat scary. With all the science-fiction literature we’ve been exposed so far, it’s hard not to imagine disquieting scenarios where the computers start being completely self-sufficient and take over the world. (But who knows, maybe they’ll manage to do a better job than us!)

See also The official IBM press release page.

Joe’s First Computer Encounter

Handpicked

The always great Lukas Mathis recently pointed to Jennifer Boriss’ blog, and it’s been a really interesting discovery. She is User Experience Designer at Mozilla Corporation and her article, User Testing in the Wild: Joe’s First Computer Encounter, was a fascinating read. It’s the account of her experience conducting a usability test with a 60-year-old man who has never used a computer.

The amount of things we tech-savvy geeks take for granted is staggering. She concludes (emphasis mine):

• There is little modern applications do to guide people who have never used a computer. Even when focusing on new users, designers tend to take for granted that users understand basic concepts such as cursors, text boxes, and buttons. And, perhaps, rightfully so – if all software could accommodate people like Joe, it would be little but instructions on how to do each new task. But, Joe was looking for a single point of help in an unfamiliar environment, and he never truly got it – not even in a Help menu

• No matter their skill level, users will try to make sense of a new situation by leveraging what they know about previous situations. Joe knew nothing about computers, so he focused on the only item he recognized: text. Icons, buttons, and interface elements Joe ignored completely

We shouldn’t assume that new users will inquisitively try and discover how new software works by clicking buttons and trying things out. Joe found using software for the first time to be frightening and only continued at my reassurance and (sometimes) insistence. If he was on his own in an internet cafe, I think he would have given up and left after a minute or so. Giving visual feedback and help if someone is lost may help people like Joe feel they’re getting somewhere

• Don’t make too many assumptions about how users will benefit from your technology – they may surprise you!

I can confirm Boriss’ words when she writes that Joe found using software for the first time to be frightening and only continued at my reassurance and (sometimes) insistence. I’ve seen it first-hand some years ago when I helped in some computer courses for novices. The general approach of first-time computer users (especially of a certain age) was in most cases overly wary. In other words, they were constantly afraid of ‘breaking something’ or doing some kind of destructive action (not literally destructive, of course; more like “what if I make a mistake and cannot revert to a previous state?” situation). 

Another thing I noticed was that some beginners raised interface-related questions that caught me a bit off guard; exactly because, as a power user who is accustomed to computers and their interface paradigms & metaphors, I was taking for granted everything on the screen. For instance, a man asked me: “If this disk [pointing at the icon representing the boot drive] contains all this stuff in these folders [pointing at the other icons on the desktop], why is each folder as big as the disk? Shouldn’t the disk be bigger than them?”. Another user found the idea of deleting a document by dragging its icon in the Trash ‘intuitive’, but then added: “So why don’t I have to drag a document icon on a Photocopier icon to make a duplicate?”. Sure, you smile, but try to be there, answering these questions, before people who are not asking rhetorical or tongue-in-cheek questions and want straight answers right away.

I should write a full account of my experience at those courses, but meanwhile here’s the moral of the story: designing interfaces is hard. Harder than you think.

Morrick’s Digest

Tech Life

When you migrate to a new web place, you’re bound to deal with your archives sooner or later, especially if you’ve been writing online for years like me. Admittedly, my English material constitutes a smaller corpus than the Italian’s (my first official Mac-oriented blog started in 2005 and was in Italian). When I was preparing this website for launch, roughly a month ago, I considered doing a simple export-import operation from my previous blog The Quillink Observer. Both this site and that blog run on WordPress, so importing the archives should have been a pain-free process, at least in theory.

In reality, as always, things aren’t that simple. Two main problems arose:

  1. This blog has only 5 categories and a very strict group of tags (no more than a dozen), the old blog was a mess in this regard, with categories and tags implemented in a more careless fashion and being more than 80 in total. Now, importing more than 600 posts at once and then having to go through them one by one, deleting and adjusting tags & categories would have taken a huge amount of extra time — surely delaying the launch of this website of a few more weeks. Something I didn’t want.
  2. The second problem is related to internal linking (posts containing links to other posts within my blog) and images. My archive of more than 600 posts contains self-referencing links and images hosted in the free WordPress.com installation of The Quillink Observer. If I had performed a mass import of all those posts, I would have had, again, to go through them one by one, correcting the links, uploading all the images on this space then changing the links that point to them when you click to see them bigger. Another daunting, time-consuming task.

So I decided to import only the most recent articles (say, from January 2011 on), and then revisit the archives periodically and proceed with small, incremental imports — starting with English articles, since this website is meant to favour English content.

The other day I patiently imported articles I wrote between January and May 2010, and I stumbled upon a few ones you have probably missed, since 1½ years ago my blog was surely even more obscure than it is now. So here they are. My very favourites are in bold.

  1. The lameness of netbooks — Some observations in response to Jeff Atwood’s observations regarding netbooks and their place in personal computing. (17 January 2010)
  2. Who’s afraid of the iPad? — Where, by judging some reactions to the iPad’s introduction, I feel it’s 2007 all over again, and where I make some observations regarding the iPad’s potential. (2 February 2010)
  3. A wake-up call for the current state of personal computing — It seems that a lot of people, after realising the effectiveness of the iPad’s touch interface and general user experience, have started to question and discuss what’s wrong with the current state of personal computing. (5 February 2010)
  4. Synchronised writing — Or: How I Learned to Stop Worrying about Word Processors and Love Synchronisation. (17 February 2010)
  5. Magic Mouse: out with the old, in with the new — After tolerating its shortcomings for too long, a couple of days ago I decided to stop using the Mighty Mouse with my primary Mac, pass it to my faithful G4 Cube, and buy a Magic Mouse. (19 April 2010)
  6. Not so fast — Goodbye point-and-shoot cameras? Perhaps. Goodbye laptops? Not so fast. (28 April 2010)
  7. Books are bricks — important ones. — Or: Why I’m not going to renounce my library of printed books no matter how digital the future becomes. (28 May 2010)

As always, thanks for reading.

The @-symbol, part 2 of 2

Handpicked

I almost forgot to link to the second part of this great piece by Keith Houston on his Shady Characters blog. Part one is here.

Though the origins of the ‘@’ symbol’s visual appearance are murky at best, its use as a shorthand for ‘at the rate of’ is rather better attested. One scholar in particular saw his work reach a far wider audience than might have been expected of an otherwise minor piece of paleographic research: in 2000, a number of newspapers reported on the work of one Giorgio Stabile, an Italian academic who had finally unearthed convincing documentary evidence of the symbol’s meaning, if not its visual appearance.

Stabile’s search for the birth of the ‘@’ started with an analysis of the symbol’s various names. A online survey conducted in 1997 revealed that the symbol went by a multitude of names across 37 different countries, many of them playfully inspired by its shape […]. French and Italian have both ‘proper’ terms — respectively arobase, an archaic unit of weight, and anfora, or ‘amphora’ — and also the more whimsical escargot and chiocciola, both meaning ‘snail’. English uses the cheerlessly direct ‘commercial at’ or, simply, the ‘at sign’.

Stabile observed that despite the symbol’s many metaphorical aliases, only certain names stood out as unrelated to its shape: the English ‘commercial at’, the French arobase (also rendered in Spanish and Portuguese as arroba), and the Italian anfora, or ‘amphora’. ‘Commercial at’ evidently described the character’s typical usage, but arobase/arroba and ‘amphora’ bore further investigation.

Source: Shady Characters » The @-symbol, part 2 of 2.

Why I still prefer Tweetie 1.2.8 over the official Twitter for Mac

Software

They say that you never forget your first love. Well, in the microcosm of Twitter clients, the old saying has proven true for me. Tweetie has been the first (and for a long time the only) Twitter client I used. At a certain point, all the talk about a forthcoming ‘Tweetie 2’ raised my expectations. Tweetie is fast, well-designed, easy to navigate — I said to myself — it can only get better from here.

Imagine my disappointment when finally Tweetie 2, or rather the official Twitter app for Mac, was released. As I already explained in this article, the main reason why I haven’t switched to Twitter for Mac is its exclusive use of the Twitter-sanctioned t.co URL shortening service. However, I have to slightly revise a brief observation I made in that article regarding Twitter for Mac’s interface. I wrote:

Most complaints [about the app] seem to be interface-related. Not mine. In fact, I really haven’t got any problem with Twitter for Mac’s interface. I don’t mind its non-standard GUI elements, I don’t mind its animations or their inconsistencies.

While this still holds true considering Twitter for Mac on its own, recently I put the old Tweetie and the new Twitter side by side, and I have to say that I like Tweetie 1.2.8’s interface more. Disclaimer: I now use Tweetie with a ‘re-skin’ customisation made available by Yummygum Studio some time ago (it’s available on Iconpaper), but since it doesn’t change Tweetie’s interface drastically and only improves what I already liked, I still think it’s a valid comparison.

Tweetie and Twitter for Mac

Left: Tweetie 1.2.8 — Right: Twitter for Mac

Now, these are very personal impressions, but here goes:

• Tweetie visually separates each tweet from one another, and the author’s avatar from the tweet, and my eyes find that more pleasing than Twitter’s all-white timeline where each tweet is barely separated by a light 1px line.

• Tweetie uses Lucida Grande as main font, which I find more legible than Helvetica at that size.

• I prefer Tweetie’s always-on tab design.

Feature-wise, here’s what I like about Tweetie:

Tweetie General preferences

Tweetie can display users’ full names, while I find mystifying that Twitter for Mac still lacks this feature. I don’t know you, but I prefer reading people’s full names in my timeline.

Tweetie, most importantly, lets you choose among 5 URL shorteners. In Twitter for Mac there’s only t.co, so you don’t even have a drop-down menu to choose from.

Tweetie Advanced preferences

Tweetie’s ability to preview short URLs is also welcome. Twitter for Mac is sorely lacking in this regard — again, mysteriously, since I assume it derives from Tweetie, so I don’t understand why certain features have been dropped. Being able to preview short URLs is handy and user-friendly.

After Twitter changed the authorisation method, Tweetie cannot handle direct messages anymore. If it could, and if Twitterrific for Mac weren’t so awesome, Tweetie 1.2.8 would probably be still my main Twitter client.