Just trying to make sense of things...

RE: The plague of new version notifications

Thursday, 14 August 2008 16:28 by jordan.terrell

This is a response to this blog post.

I'm in agreement with my friend David - it is most annoying when I launch a program and it immediately notifies me that a new version is available.  It is even more annoying when a program does so on the UI thread, thus causing the application to hang until it has determined if there is an update.

However, I have an alternative suggestion for a solution approach: create Software Updates service protocol.  The approach would be similar to RSS or the Web Service protocols; it would start out as a basic definition of Operation and Data contracts based on XSD and WSDL. Over time people could add extensions to improve it's capability.  You would have support for discovering update servers and enumerating available updates.  You could also potential give simple automatic update functionality to XCOPY deployed applications - as long as you could discover a service that provided you with metadata specifying the location of the latest binaries.  Eventually, popularity would drive major software vendors to include support for this protocol, and libraries for various development platforms would be written to make this simpler.

Anyone want to take on this challenge?

Categories:   Programming
Actions:   E-mail | | Permalink | Comments (1) | Comment RSSRSS comment feed

Mixed Experiences Using Twitter

Sunday, 10 August 2008 01:50 by jordan.terrell

I've been using Twitter for a little over a week - and as you can no doubt guess from the title of this post, I've had mixed experiences.

I've managed to pick up a handful of useful links to software development resources.  Plus, I like how many of the mainstream blogger's "Tweet" when they make a blog post - it's kind of like real-time RSS.

However, I have noticed a less than desirable signal-to-noise ratio.  Whereas most of the blogger I follow publish software development related content, following those same people on Twitter has thus far yielded dissimilar content, and out of context chatter.  For example, if you are following one person, and they "@reply" to another person you are NOT following, you only hear one side of the conversation - much like trying to overhear and understand a phone conversation that you can only hear one side of.  I've also noticed that since Twitter is closer to a near real-time communication medium, it tends to better enable heated debates, even outright textual fights - I've already had to "leave" (no longer follow) one person for this very reason, just to avoid this noise.

Having said all of this, I think there is much realized and future potential with this platform of communication.  I think Twitter would benefit from things such as tagging, being able to associate a Tweet with a URL (instead of having to include it in the body of the Tweet), increasing the permitted size of a Tweet to ~250 characters, and the ability to create, join and subscribe Tweet groups.  This would allow one to both publish(if a joined member) and subscribe to something like the "ALT.NET Tweet Group" or "Rhino Mocks Tweet Group".  Twitter etiquette would encourage people to stay on topic when posting to a group.

Perhaps my suggestions goes against the grain of what Twitter is all about (following people's daily on-goings), but if you think of RSS, it too came from humble beginnings as well - but now we tag, we TrackBack, and we Digg, Kick, etcetera.  This has created a very vibrant blog ecosystem, while still maintaining its grassroots heritage.

Regardless, I'm going to stay of Twitter for now - if I continue to see a degradation in the signal-to-noise ratio, I may just tune out...

Categories:   General
Actions:   E-mail | | Permalink | Comments (0) | Comment RSSRSS comment feed