Slashdot Mirror
Financial Companies Ask IM Companies To Work Together
sammy.lost-angel.com writes "From
this
CNET article: "Two weeks ago, six top financial institutions met privately with AOL Time Warner, Microsoft, IBM and other leading corporate instant messaging providers and urged them to build communications networks that interoperate." The article even talks about Jabber."
We use Jabber for a distributed (multi-state) group of developers. Perhaps I should just knuckle under and pay for long distance? (I'm sure telecom stockholders would appreciate my efforts). I think you lack an understanding of how IM is used by professional developers - we don't sit all day chatting about the weather, how 3l33t we are or throwing MP3s to each other; we get quick answers to questions that would otherwise hold up programming a module.
Additionally, I love it when people use this to communicate outside the building - rather that than the Cell going off during a meeting because the wife needs some fixings for dinner on the way home.
The reality is it depends on the maturity of your team. All of my team members are mature enough to use IM as a tool. Those who were not mature enough were fired after a warning. This applies to ANY communication tool, any violation of company codes.
Sig under construction since 1998.
"There has to be a business model where Microsoft and Yahoo and AOL get paid,"
I disagree. There doesn't have to be and there shouldn't be. The article mentions that IM should be like E-Mail. Well, Microsoft and Yahoo don't get paid just because some guy using a yahoo e-mail account e-mails someone using a hotmail account.
My advice to these "finanical" guys seeking standards - ignore it. The problem will solve itself in a matter of time. IM is too big of a thing to be contained within proprietary networks. As these all in one messenger programs like Trillian become the de-facto standard, companies like Microsoft, AOL, and Yahoo will have to give up their futile efforts of hording all their IM customers to themselves. Or better yet, if (when?) Jabber becomes the real standard, the corporations wont even have to worry about Microsoft or AOL anymore.
Yeah, just like they get paid for hosting all of our web pages, email, and ft.... Wait a second, we run our own servers for those things! Why the heck can't we have an IM system that's the same way? Run our own darned IM gateways/server, and just include it as part of your address (whoops - screen name, can't have anything technical sounding). User@server has worked well enough for email, heck with an LDAP3 directory backing it, email your address could easily be mapped to the IM presence on your server/gateway. If you really wanted to get fancy, add an IM record type to DNS.
Thinking like this is just plain stupid - there's no possible reason why this couldn't work without relying on MS/AOL/Yahoo to run our servers for us... Except they beat us to it. So how do we convince those planning to spend $$ to do it in a responsible fashion?
Think outside the... Hey, where'd the friggin' box go?
The reality is it depends on the maturity of your team. All of my team members are mature enough to use IM as a tool. Those who were not mature enough were fired after a warning. This applies to ANY communication tool, any violation of company codes.
Any company that fires based upon the use of a communication tool deserves what will ultimately become of it, which is failure (apart from the criminal or sexually harrasing, of course). If someone is producing good quality whatever in good quantities, then it should be absolutely irrelevant if they are playing computer chess while chatting with their buddies about D&D. If, on the other hand, someone isn't producing, then it shouldn't matter that they put in 60 hour weeks (as is usually the case with non-producers: Martyrdom through incompetence), and that they sit starting hardcore at code from 8am until 6pm every day, they should be moved to a different job, or ultimately fired.
The way I manage is entirely output based, and no amount of ass kissing or excuse making can make me ignore a lack of contribution to the project, but on the flip side I don't care if someone works 12 hours a week and has slashdot on auto-reload: If the output is there, then how can they be faulted? Too many people bring a factory line mentality to software development, and unfortunately such a mentality is often based on envy: You have to keep everyone beaten down to the same level to ensure that the lowly doesn't feel green with envy.