Thursday, November 27, 2008

FireStatus 1.5 meets Del.icio.us

FireStatus 1.5 is out and it supports saving bookmarks on delicious. If you select the delicious checkbox a second text line will appear to enter tags for the bookmark. You don't have to select the "include url" checkbox for delicious unless you want to send an update to the other supported services. Delicious support also includes receiving bookmarks from your friends on del.icio.us in the usual way with popup notifications.



In the preferences, you have to give your delicious credentials and set the interval for polling for bookmarks from your friends. Be careful not to set interval to less than 30 minutes because you risk being temporarily throttled by the service.



The future
The next feature to be implemented is a list of all updates received from all enabled networks. Popup notifications are popular but if you miss one there is no way to see it, so the plan is to have a list (a sidebar maybe) with the past notifications (maybe the last 50?).

After that the most ambitious feature will be to create a post in your blog with your daily activity on the firestatus supported networks. Blogger will be the first to be supported (I use blogger. That 's why :-))

Download here and more info here.

Wednesday, October 15, 2008

FireStatus meets urlBorg

The next release (1.2) of FireStatus supports more than TinyURL for url shortening. The new option is urlBorg created by Panagiotis Vryonis a Greek programmer, so we (Greeks as well) felt obliged to add support for his child :-)

The preferences window has been changed to accomodate a new section for url shortening services.For the time, tinyUrl and urlBorg are supported but we plan to add more in the future as well as a fallback mechanism if the selected service fails. Thanks for all the positive comments and don't forget to leave a review :-)


Reblog this post [with Zemanta]

Monday, October 13, 2008

Minor changes ...

Notice the new items on the sidebar of this blog. Newcomers are the Followers widget which display my only follower and FireStatus co-creator and the Blogs I read. I hope the followers list gets longer over time and the blogs I read gets shorter :-) So if you read this blog add it to your following list and I promise I add yours to mine.

Monday, September 29, 2008

Meet Firestatus

... a status update utility for multiple social networks. So, what 's this all about? The story goes like this: You see a cool page on the net and you 'd like to share it with your friends or you just want to update your status, the "Good morning, I just woke up" kind of twit. But your friends don't seem to have reached a consensus about THE social network. So, some of them use facebook, some other use twitter, some use friendfeed and you go on and on and on. What do you do to share the cool link with all of your friends (assuming that you have accounts in all of their networks)? You go to each and every social network page and write the same text again and again ? No. You need a client that can communicate with as many networks as possible and send the update to all. I certainly had that need. However the few clients I had seen didn't do the job exactly as I had imagined. My main problem is that even with multi-network clients I have to write the update and send it separately to each network. Why can't I write the text once and send it to all networks with just one click ? It can't be that difficult. Why don't we create such a client as a firefox extension (we are top engineers after all) ? So I discussed the idea with my friends, XUL and Javascript experts, Panagiotis and Dionysios (the best way to solve a problem is to find the people to solve it for you :-)) and here it is. It took us several weeks because we couldn't dedicate much time to the project but in the process we added friendfeed (instead of only twitter and facebook) and Panagiotis added the notification functionality (it 's a good thing to see what your friends are doing on twitter :-). So now we are waiting for your feedback and we are open to suggestions. We plan to add features like the unread notifications list and of course more networks like linkedin, del.icio.us, etc. Every network with a public API is a candidate. And don't forget to leave a (positive :-)) review here.

Thursday, August 14, 2008

What I read and liked on 2008-08-14

Interoperability Happens - From the "You Must Be Trolling for Hits" Department...

Experience vs Knowledge. They both matter. One of the arguments in the article is that applying in production, the brand new language that you just learned, needs acquiring some experience with it first. I have to add that even picking the next language to study will be greatly helped by experience, otherwise you might end up waisting time learning useless things

Interoperability Happens - More Thoughts on Architects and Architecture

Are you a software architect or a software engineer? Someone that
designs a software system takes into account restrictions like budget,
time schedules and dealines, available staff etc. In that sense his job
is not strictly technical but it also has an economics aspect.
Therefore the word "engineering" seems more appropriate. At least, in
my language (Greek) the word architect has an artistic essence while
the engineer is more technical-economics oriented.

Wednesday, July 16, 2008

What I read and liked on 2008-07-16

So You Say You Want to Kill XML....
An interesting and more cool-headed approach to the Protocol Buffers open-sourcing

Sunday, June 8, 2008

JHUG Java Tech Day 07-06-2008

I am too lazy to write a detailed report for the event. Anyway, Paris already did it and Dionysios will certainly write about it soon. I just want to once again declare my willingness to give Netbeans a try (and once again I won't find the time to do it :-)) after the Netbeans presentation by Mikhail Kondratyev. The javascript editor, Mercurial support and the project groups (I really miss them in Eclipse) are of particular interest to me.

I will keep one quote from Kirk Pepperdine 's talk and that is:
"Databases cannot scale"
His presentation was very interesting but I have various db issues so this particular quote got stuck in my mind.

The Jbossians gave very vivid and enjoyable talks. Jboss 5 is something that we 've been expecting for quite some time and another feature set presentation just made us even more anxious, so Jboss guys, get it out soon! The event finished with Jboss cache and despite the fact that I haven't used it before, Manik 's presentation managed to keep my interest.

Ok, now that I finally did my lazy man 's report I cannot close without saying a good word about the lunch break that was really great. Hungry developer cannot code (Slightly altered version of a Greek proverb).

What I read and liked on 2008-05-30

Thursday, May 29, 2008

Friday, May 23, 2008

On languages, life etc - Part #2

This post is actually a comment to the comments at my previous post, but it grew too big so it deserves to be a new post.
So in my previous post, past said:
"Agreed. But that is the wrong question. Very few of our clients ever asked for Java development either. All the client wants is working software that meets his needs. Certainly I, or anyone else that I know for that matter, never asked Facebook to use Erlang for its chat feature."
I 'm glad you agree and you give me the opportunity to explain that my reference to the client 's demand for a specific language had a slightly different meaning. I agree that the client usually does not ask for a particular technology, so if you choose Java or Scala is of little interest to her/him. Do you believe that there exists a language that will do the client 's job 100 times faster or otherwise better? I don't. If my choice of a new language over e.g. Java achieves a performance increase of 0.0001% neither the client will care nor I.

My post was a reaction to the chaos of thousands of programming languages and frameworks that have flooded our professional lives. I agree that the customer usually don't ask for a particular language or framework and it is our responsibility to choose the more suitable solution. Do you believe that in order to achieve that, we should constantly study and improve ourselfs ? I certainly do. Do you believe that ScumbagX#+ is an essential asset for a developer in Greece ? Ok, I again go with you. Do you beleive that we should spend our time deciding between ScumbagX#+, JScumbagX#+ and IronScumbagX#++ because the last one is 0.00001% faster? I certainly don't. What I mean is that every geek in this world dreams of creating his own language that would incorporate all the great concepts that he learned in the "programming languages" course at the university. Am I obliged to learn it ? If I am (and sometimes some new language deserves my time) then I will, but I don't have the illusion that in this life I will manage to learn all of them.

"If you can meet your customers' requirements and be competitive with what you already know, then by all means do so. Working as a developer in most software houses is not that demanding after all."

Everything in this life is a trade off. Our last web app was written in java for jboss. It is an internal application used by 50 users and the type of application that will never go on the public web. If we have written it in Erlang and could manage 50 gazillions requests per millisecond, do you think that the client would have paid us more ? Not in a million years! If we had to write an app that had to deal with 50 gazillions requests per millisecond then ok. Erlang might have been the right choice and the time investment to learn it would be justified.

"However, if you have any aspirations to ever work on a startup like facebook, twitter or friendfeed, or worse, start your own, then you might need to work a wee bit harder than that."

Everything in life is also a bet. If you want to start the new Facebook, you bet on some technologies and invest on them. You cannot do the same for every existing technology. The reason is simple. We won't live for 200 years.

I 'm closing with a clarification for synodinos:

"BTW are you this cautious about all new technologies, because I think you were (somewhat of) an early adopter for JPA?"
JPA was actually one of my early adoptions that caused me absolutely no trouble (I cannot say the same for struts 2 though), so this can be no reason for being cautious about new technologies. Actually, I have to clarify that I am not cautious about new languages. On the contrary, I trust them all. Completely. And I am convinced that each and every one of them was created with good intentions. But you cannot invest on all of them. You have to find a golden rule. I totally agree with those that support the opinion that a developer should know more than one language. On the other hand a developer can go far enough and know TOO many languages but be really good at none of them (I think I read that here :-)).




Thursday, May 22, 2008

On languages, life etc

In a previous post I implied that in Greece it is of no value for a developer to learn Scala. My good friend George commented:

"If your clients are located in Greece, investing in Scala might be totally premature.

(OTOH, this means that I must play with Scala:) )"

George and I and some more of my friends would study Scala just for the fun of it. But that 's all. Fun. I have the extremely strong feeling that no client of ours will ever demand development in Scala. Of course Scala is just an example. The same is true for Erlang, F#, Ruby or Duby or Scuby or any of their variations like JScuby, or Duby# or Scuby++ or DubyScript or Scala on Rails or on a bicycle. Give me a break here, will you ? I just have only one life! Even if I wanted to learn all of them there is not enough time in a person 's life. I don't believe that in this universe there are enough clients that would ask for development in JScubyDuby++##Script that would justify my time investment. Even if I had to leave my company and go to work anywhere else in Greece my knowledge of FRuby#FX wouldn't be much appreciated. But maybe I don't know what I 'm talking about.

What I read and liked on 2008-05-22

Java Architectural Knowledge for Job Interviews. Are we prepared?
If we have studied the principles and not the specific tools or frameworks then we are definitely prepared not only for the interviews but also for learning quickly and easily any tool or framework. Unfortunately, in Greece many types of schools produce developers that know one specific programming language on one specific IDE and then every problem looks like a nail.

What I read and liked on 2008-05-21

Groovy or JRuby?
For a developer in a small company in Greece how valuable may be the knowledge of e.g. Scala? I just wonder ...

JHUG Java Day sponsored by Sun Hellas - 7 Ιουνίου 2008.
I will certainly be there!

Tuesday, May 20, 2008

What I read and liked on 2008-05-19

Java haters, gtfo
I don't dislike scripting languages, however I like his way of presenting things

Friday, May 9, 2008

What I read and liked on 2008-05-08

JavaOne Day #1 Report: ROCKING!
Report from JavaOne by Dionysios. As always he manages to give us the atmosphere :-)

Thursday, April 24, 2008

What I read and liked on 2008-04-23

The power of links and the value of global knowledge
Lately I wonder more and more about the value and possible uses of the info stored in Facebook


New Features in EJB 3.1
Asynchronous invocations caught my eye.


Wednesday, April 23, 2008

What I read and liked on 2008-04-22

Developer paradise?
We all liked the images of Google offices in Zurich that flooded our e-mail lately. Here is a different approach
Amazon upgrades EC2 with Persistent Storage
I 'm a proud friend of the author

Tuesday, April 22, 2008

Non completeness

This statement is not provable.

Let 's call the above statement S. So what S says is that

S is not provable

If this statement is false (meaning S is false) then the opposite statement must be true. The opposite statement is

S is provable

and it must be true. But wait a minute. If S is provable, meaning that there exists a proof of its truth, then S is true. But wait a minute again. We started by assuming that S is false. A contradiction... This means that our initial assumption was wrong and therefore S is true. But what does this mean ? This means that what it says is true, S is actually not provable. So S is true but non-provable. This is non-completeness. Our inability to reach every existing truth. Simple, elegant and yet so deep.