



Apparently I am not the only one making comparison tests between the two (not that I thought I was). TheMarker's Captain Digital himself has done his own testing and arrived to the same conclusion as I did – Wikipedia wins, at least for now.
The full article (in hebrew) can be found here: http://it.themarker.com/tmit/article/4100
Anonymous vs. credit
Editing articles
For now I will leave you with an interesting comparison between both knowledge bases on the word "genesis". I know it is not a fair comparison, since knol was just released, but it is still a bit amusing to see the difference:
No - this is not a post on the very funny film by John Landis (http://www.imdb.com/title/tt0086465/).
The article at the bottom talks about people going abroad, that instead of paying for a room in some hotel, they switch their apartment with some people going the opposite direction. This is a very interesting concept. The most obvious reason is that this can reduce the budget of a trip abroad by some very large extent – the example given in the article is that an ordinary hotel room in NYC costs about 250 dollars for a couple. A 10 day vacation in the big apple living in someone else's apartment means about 2500 dollars savings. Moreover, an apartment is usually located in a less touristic, more interesting location, and may have better accommodations, a laundry machine, a bigger TV and so on and so forth…
But what are the chances of me, finding someone from New York, who wants to be in Israel, or better yet, in Hertzelya for the exact time that I want to have my vacation in Manhattan? Does this mean I need to wait for a miracle in which someone chooses my apartment to spend his vacation in and then fly away to wherever he is coming from?
Manhattan sky line - is there anyone in the picture that wants to be my house switch partner?
What do you think about another option – instead of switching places between two people, why not have a circular transition? I will go to New York, the woman from NY will visit Rome, the Italian guy will have a nice apartment in Brazil, and Ronaldinio junior will stay at my place? This cannot be done manually of course, but a simple enough algorithm can try to give everyone the vacation they are dreaming about without going bankrupt.
The original article (in hebrew) can be found here: http://www.themarker.com/tmc/article.jhtml?ElementId=skira20080723_1004603&origin=ibo&strToSearch=%E3%E9%F8%E4%2C%EC%E4%E7%EC%E9%F3
מודעה אחת תפסה את תשומת ליבי, היה בה משהו לא שייך
התקרבתי עוד קצת וגיליתי מה הפריע לי
הבטתי במודעה וחשבתי לעצמי - למי יש ביטחון עצמי כל כך נמוך שהוא שם מודעה בלוח סקווש, לא אכפת לו איזה מין ייכנס לו למיטה ועוד מצהיר על עצמו כרמה בינונית? שאלה אולי יותר גדולה - האם מישהו/י נענה
:-)
I started using it for RSS feeds from the blogs I read, for news and weather information and for other general stuff.
A nice new feature is the theme of igoogle, making it somewhat more enjoyable. I set the puppies theme, which shows me a different puppy each time I enter the site.
It's back; the week of the last build. Frenzy but quite, irritating but fulfilling.
Every four months or so, we, ClickSoftware R&D, publish a new release of Service Optimization. The last month of every release is a time of war – Engineering and QA battle out against the almighty bugs. We usually lose some fights and win others. The final battle is the week in which we must secure the last build. QA has the task of approving every single bug that was fixed for the release, making sure that no bug reappears suddenly. Engineering is supposedly out of the loop – looking into the next release and writing down trainings and documentation. But as we all know – something always goes wrong.
A bug in the last build week turning into a feature.
The week starts optimistic, stating that we are going to create the last build on the first day of the week, and spend the rest of it double checking. It usually takes about three to four hours when suddenly Olivier comes round and asks whether the "Internal Error" he just got is deliberate. Then there are the support calls that were opened two months ago, but just recently came across Engineering. A one minute look at the problem and Amit already knows that this is a bug that wasn't fixed yet, not even in the release we are trying to close. We are already three days into the week when an urgent meeting takes place to decide what to do with the importance 1 bug that was found by accident, when trying to call an SXP that has always worked (but never been used recently).
The only acceptable bugs during the week of the last build.
Thursday morning (I am reminding you that we are located in Israel and work from Sunday to Thursday) comes and last night's build has a great number – 3703. We must turn it into the last build and not ruin this no matter what! But then Lirit finds a problem in the documentation – stating that we round up the seconds instead of rounding down. A quick huddle in the corridor between Miriam and Lirit debating whether to fix the code or fix the documentation turns into a new bug, but at least it's a WORD bug that does not need to recompile and adjust the release number to 3704.
Lirit editing the documentation; if a bug is not a feature, then maybe it's just a documentation bug?
Thursday evening – it's all behind us. The release is already packaged and there is nothing we can do anymore. Just occasional temp fixes here and there…