Where will all my bookmarks go?


When first heard the news that Yahoo! was going to lay people off, I was far from imagining that it would affect me directly. Of course, it always saddens me when people are made redundant. But it didn’t even cross my mind that Yahoo! would close down some of its most popular services.

Actually I don’t rely much on Yahoo! except for Yahoo! Groups and delicious. I gave up using my Yahoo! mail a long time ago because I found GMail much better. I barely use Flickr except when I need images under Creative Commons Licence.

I was very surprised yesterday when I first saw some tweets spreading the news. I googled it and came across this article. The article shows a slide on which it seems that delicious only is threatened. That’s a bit of a relief. On the other hand, I find this news pretty odd. Indeed, why not selling delicious or even give it to the community? I can easily imagine that there must be a hell of an infrastructure underneath the product, which must also be costly. I am eager to hear from Yahoo! on the subject in the coming days.

Now, I wonder: Where will all my bookmarks go?

For many years, I have been keeping my bookmarks in the cloud. I love the tagging concept. I can tag my bookmarks instead of painfully try to store them in a static folder structure to find them back. I can look something up inside my bookmarks as well as in other’s bookmarks. You don’t need to thoroughly organise your stuff. Simply categorise it and harness the search capabilities of the tool and find out what others bookmarked. Furthermore I can access my bookmarks from anywhere, I don’t need to care about backing them up. This is the Web 2.0!

Are there worthwhile alternatives out there?

Some didn’t waste time! Evernote already blogged about making the transition from delicious to Evernotes!

Personally, I wouldn’t go for a non-free, non-cloud alternative. Maybe I will fall back to Google Bookmarks as I intensively use Google Products. I still have to look into such alternatives. I did a quick googling on the topic and found some worth reading articles:

In the mean time, if you want to keep your bookmarks, you can export your them to html on the delicious web site: https://secure.delicious.com/settings/bookmarks/export. Lifehacker also posted an article explaining how to export your delicious bookmarks and import them in your browser if you don’t know how to do it: http://lifehacker.com/5714313/

Agile is for cavemen


I am currently reading The Tipping Point, by Malcolm Gladwell. In the book, Gladwell quotes the anthropologist S.L. Washburn:

Most of human evolution took place before the advent of agriculture when men lived in small groups, on a face to face basis. As a result human biology has evolved as an adaptive mechanism to conditions that have largely ceased to exist. Man evolved to feel strongly about few people, short distances and relatively brief intervals of time; and these are still the dimensions of life that are important to him.

Once you think about it, it sounds so obvious that humans are still wired as they were back when they dwelt in caves. It is therefore also natural to feel comfortable in a work environment that reproduces this kind of setting.

In Agile, small teams of five to nine people are recommended. Agile also recommends that team members be collocated, in a single room. Those practices aim at maximising the efficiency of communication and team work while minimising the required amount of ceremony and waste in communication. Those therefore facilitate face-to-face communication as well as osmotic communication, as Alistair Cockburn names it. Agile is therefore an approach to software development that befits our cavemen brains.

Dispersed teams and informal communication channels are thus completely unnatural. Nevertheless, even though our brains haven’t evolved much since the times of our hunter-gatherer ancestors, our societies tend to put more and more distance between people while offering loads of means of communicating and sharing any form of information.

Food for thought…

Heck, blogging is not as easy as I thought


Quite some months ago, I decided that I wanted to start blogging. In my both my personal and professional lives, I spend a lot of time reflecting upon my actions and the actions of others, how to improve activities, processes or attitudes. Blogging sounded like a natural way to crystallize all that thinking. Indeed, thinking through a problem is good but coming to write it down yields even more results. Formulating an idea on paper helps structure it even more.

So far, so good. I know what I want to do and which subjects I want to tackle:

  1. Express opinions
  2. Review stuff I read or use
  3. Share experience
  4. Crystallize some ideas and write about how I do things to get a better understanding of them as well as to improve. Sort of Deming’s Plan-Do-Check-Act.

I am used to writing. At work, I have to write a lot (maybe too much in fact) as I work for a consultancy company. I was wrong. Blogging is not the same as writing a document for a customer or the team or a white paper. At lease, in my understanding of blogging. My idea was to publish short and concise worth-reading posts. That’s quite a high expectation and obviously not really humble. Who am I to say that what I write is worth reading 🙂

Working out a post takes time more time than I thought. It might be because I don’t want to publish anything that meets some level of expectation from my side. I know that I shall not raise the bar too high but this is easier said than done.

Because it takes time and energy to write a valuable post, I haven’t posted much up until now. I’ll make a new year wish mid-July but I’ll try and blog more often. I think it’s part of an ongoing and perpetual learning cycle and well worth the effort.

I’ll try to post at least once per week. Let’s see if I can commit to that!

Cheers!

We are open for business


I’ve just created this blog to share my passion for software development. I’m interested in some specific aspects about which I intend to blog:

  • Agile, iterative and incremental development
  • Software architecture
  • Java, Groovy and whatever I’ll come across
  • TDD and test automation

That sounds like quite a lot but the world of software development is so vast that it makes it really hard to embrace it all.

Cheers!

%d bloggers like this: