Links for 2007-08-03
- Never Email Anyone Over 30 - I've seen many enterprises that think that Email + IM = collaboration needs met and I find it pleasantly surprising to see that IM as a collaboration tool is diminishing in the eyes of the younger generation of workers in favor of things like SMS, Wikis and Blogs (Twitter is probably just about in its own category). What that means however is that the enterprises who are just now getting IM in the Enterprise are still behind the curve... so what's your strategy for embracing the next generation of collaboration tools? Does an Enterprise vendor have to offer it before we'll buy it?
- Practical Enterprise Architecture - Some good tips on creating valuable Enterprise Architecture.
- What is Enterprise 2.0 - As much as I don't like the phrase, or "concept versioning" in any form, I like what the idea represents in terms of driving information access, interconnected applications and devices and collaborative and open work.
- SubSonic - This looks to be a very nice ASP.NET scaffolding framework that parallels much of the project start-up scripts that makes Ruby on Rails such a nice environment to work in. (via Ken Scott)
- Should people adapt to computers? - Agreed Scott. I think that people have adapted enough... it's time to set them free, and I don't mean by turning their coffee table into a computer either.
- Enterprise Architects versus Business Architects - While I certainly don't think that the role of EA is to create services within an Enterprise SOA, I do think that EA has a responsibility in handing valuable business process knowledge to an SOA team that then knows which services are needed. Otherwise, services end up being created to wrap whatever database entities a given project needs next. In any case, the key is that EA has a responsibility to be relevant to SOA efforts, not the other way around.
- Enterprise Architecture is like Herding Cats - Don't know what I could possibly add here...
- Is Serendipity the Heart of the WS-*/REST Debate? Serendipity is probably a large part of the discussion, but I think a key to Nick Gall's General Principle of Serendipity ("Just as generality of knowledge is the key to serendipitous discovery, generality of purpose is the key to serendipitous (re)use.") is that one can rarely (even in an enterprise) plan for explicit reuse of a service. As such, you plan for serendipity.
Technorati Tags: Collaboration, Twitter, Enterprise Architecture, EA, Architecture, Business Architecture, SOA, REST
0 Comments