Iranian SharePoint Blogger

Farvashan is a blogger from Iran, he recently started an English SharePoint blog on sharepointblogs.com. His English is a lot better than my Farsi, but still requires slow reading to get his meaning. However he's keeping up with the latest changes in Microsoft's SharePoint technologies and has an interesting POV operating within the economic and political restrictions in Iran.

“We have two big simultaneous issues, about developing software and designing IT systems, in my country.

One of them our main policy from the government about working based on the open source technologies, because unfortunately no direct contact with the US government.

The other is bad integration of open source technologies, with the other great Microsoft technologies, especially side of users and clients. As you know in the small to midrange business it’s almost impossible developing systems without using the Microsoft technologies.

We must always choose a trade off between them; I think for the small to midrange business needs we have no other choice but Microsoft technologies.”

SaaS is letting me down

I'm getting pretty pissed off with my SaaS suppliers at the moment. In the main, that is GMail, Salesforce.com and Blogger. My main issues are twofold:

1. Slow performance
Dave Stephens recently gave his commentary on a recent Aberdeen report on Procurement SaaS. A key comment caught my eye because it resonated with my own experience:

“The only real negative I could find was in one statistic: 88% of respondents said that in house software system response time & performance was equal or better than SaaS. This reinforces my SaaS = renting-an-apartment analogy. At peak times some customers’ showers are running out of hot water! But it’s a solvable problem - the SaaS providers need to design their on-demand systems for peak load, not average load. And hopefully they will start doing that.”

Start. Doing. That. Well, yes, could they please get off their backsides and take care of this!?

[EDIT: Phil Jones rants more about Blogger on his Platform Wars blog. In the comments to his post, John from FreshBlog mentions the Blogger Hacks Wiki as a good place to find how others are 'hacking' Blogger. Heard about Phil from Dave Winer's Scripting News.]

GMail was wonderful when I first started using it, but in the last few months it has slowed to a crawl - even on a fast internet connection I find that simply labelling a post in my inbox takes 10-30 seconds. Salesforce.com has had some very public issues with its performance, which their main competitor, NetSuite, blames on their 'big iron' architecture. But the bigger issues for them are over-reliance on an old web interface paradigm, that in these heady days of AJAXified web apps seems a very inefficient way of forcing users to work with their data. Blogger has the least problems in this regard, because of its nice good UI design and their simple technical model (i.e. publishing your blog as static web pages to maximise cacheability and performance).

It's nice to know I'm not the only person getting annoyed at this.

2. Gluggy feature sets

“gluggy slow, sluggish - used to describe the operation of a computer”
Urban Dictionary

Blogger is the biggest culprit here. They've managed to add a handful of features to their blogging application in the last few years, and as a result now offer a far less satisyfing feature-set than many of their competitors. It is only thanks to the strength of the original design (pre-Google I might point out) and the great user-community, that people who want extra features (like categorisation) still hang around. The time must come soon though, when people start to move elsewhere, especially now that China, India, Pakistan and Ethiopia have taken to blocking access to blogger blogs.

Salesforce.com is bad in a different way, they have made me sluggish. Yes, AppExchange is a wonderful idea, but did we really need to get drowned with a thousand different applications? There is something to be said for having our choices restricted to a few truly great options, rather than the mess of good, bad and ugly that AppExchange really is. Once I wasted several hours looking at different applications, I realised that none of them would offer me anything I really needed or wanted on top of the basic Salesforce.com functionality (although I hear that one free one offers RSS feeds, that might be worth looking into). I could have better spent that time getting more use out of Salesforce.com's existing functionality rather than surfing the AppExchange Deadzone.

GMail has added some features, and steadfastly ignored others that users clamor for (like sorting by sender, or date, within a label or search view). The integration with Google Calendar is painful and half-baked. The fact is that my own use of it relies heavily on Greasemonkey, and so I find that using it from within IE (as I usually do outside of home) has become oddly stilted, as I reach for functions and options no longer available.

In Summary
I am a strong believer in the viability of the SaaS model. Removing maintenance headaches and installation gotchas are worth a lot, but the efficiences gained in being accessible anywhere and having economies of scale in the backend make it really appealing. I find myself agreeing with Jeff Kaplan on his identification of SaaS Myths, but in reality the applications on offer are still not fully ready for the enterprise. Many of them have not yet been tested on their performance, or security, or ability to keep up with technology changes. Market leaders like Salesforce.com, GMail and Blogger are showing signs of not handling things as well as they should, perhaps because the SaaS technical model is not yet fully mature, or simply because there is yet to be a realisation that they must handle peaks in demand, not just the average.

Technically speaking, SOA and advances in grid computing promise to deliver new levels of performance scalability, but applications must be built from the ground-up to full utilise these advantages. However, this sort of application programming can be pretty tricky (and yes, I know that threading <> grid computing, but it's got similar problems). However, there seems to be a recognition that this is an area of great opportunity, and some new vendors are planning to supply this next generation architecture.

From a security standpoint, enterprise IT departments have fundamental issues with hosting their data outside the corporate firewall. We have seen a recent rise in online storage providers, with ones like Amazon's S3 being aimed squarely at developers needing back-end data storage. Perhaps the next wave will provide data storage that is transparent to the SaaS application, but where hosting can either be outsourced or kept in-house. After all, SaaS providers usually have to promise not to access your data anyway, so why should they be bothered hosting it?

I think that the current depictions of SaaS 2.0 are missing the point if they think that better SLAs are all that is needed. Vital issues, such as performance, require both that the application be built differently from its very foundation upwards, and depend on the rollout of faster broadband access speeds across their marketplace.

For more on this subject see Dion Hinchcliffe's blog. But from my POV, the tipping point he's looking for ain't here yet.

del.icio.us tags:

• SaaS
• Web2.0

Wallabies 49 vs Springboks 0

The ARU Match Report says it all:

“The Wallabies have annihilated the Springboks 49-0 at Suncorp Stadium on Saturday night, running in six tries and keeping the South Africans scoreless for only the second time in the two teams' history.”

Blog Style Changes

I've made some minor edits to the way my blog looks. For a start I will be making long posts look smaller by hiding most of the post on the main page and only showing it on the specific post page.

I'm also going to try to make sure I use the del.icio.us tags on all my posts. It was easy when I could use Firefox and Greasemonky, but I also need it to work in IE.

Finally, I've reduced the screen real estate dedicated to my Cafepress products, and made just one area that rotates randomly through them.

[EDIT: Yes, there is a problem with the main page's structure as the area between the main box and the sidebar is incorrectly filled with white. I'll fix this at some stage (or just refresh the whole template).]

Dell's Got a Blog!

Well, well, it looks like Dell finally worked out that they ought to be using the web to talk to their users and have started a blog called One 2 One. Of course I only found it because Scoble's talking about it.

Hint for corporate marketing types - don't bother launching a blog if you can't get important bloggers in your industry to mention you. I guess the Hit mentality is still there in the blogging world.

Perhaps just as important, you must allow your staff to make mistakes whilst communicating with customers on the blog. They must be able to attempt to have open, honest and human communication with customers, otherwise it's just another one-way information pipe (oh yeah, Scoble talks about that too).

Death by Wikipedia

The Washington Post has an interesting article by Frank Ahrens called Death by Wikipedia: The Kenneth Lay Chronicles. Frank looks at the hot topic of how much we can trust Wikipedia given that it is entirely user-editable. He looks at the way Kenneth Lay's death was handled as the classic case of this and concludes:

That Wikipedia's greatest strength is its greatest weakness.

If the statement that "history is written by the winners" is too gross, it does speak to an underlying truth: All definitive encyclopedia authorship comes with the point of view of its times. It is unavoidable. As august and reliable as the Britannica is, one need only look back to 19th-century versions to see its Anglo-centric viewpoint and curious study of others that treated foreigners (say, Africans) as anthropological subjects rather than human equals.

An encyclopedia written from many points of view should, in theory, help eliminate that flaw. Further, as well-girded in research as encyclopedia authors are, there are countless experts on thousands of topics that know more than the Wikipedia authors; every topic has its fetishists, and thank goodness. If the goal is the ultimate compilation of truth-tested facts, Wikipedia could be a powerful tool.

...

But here's the dread fear with Wikipedia: It combines the global reach and authoritative bearing of an Internet encyclopedia with the worst elements of radicalized bloggers. You step into a blog, you know what you're getting. But if you search an encyclopedia, it's fair to expect something else. Actual facts, say. At its worst, Wikipedia is an active deception, a powerful piece of agitprop, not information.

(emphasis mine)

I think that's a fair call, there is some very questionable material there. Perhaps more importantly, the basic content of any Wikipedia article is dynamic. This can lead to people getting all sorts of ideas about the topic, or indeed about Wikipedia's accuracy, when the offending material might be reverted, edited or removed within moments of them leaving that web page.

For example Dave Winer mentioned on his blog that a friend had looked at the Wikipedia page about Dave and thought it pretty terrible stuff. Dave's critics on the Eye on Winer blog found this laughable as (to them) the article steers a fairly neutral course between the fairly polarised views on Dav'e contributions to blogging, RSS and podcasts.

However, a stroll through the History tab on his Wikipedia page shows a number of vandalism attempts that have been reverted (usually within a few hours), as well as some toning down of material deemed too "fanboy" by one or another named Wikipedia users. Usually vandalism is done by anonymous users, not registered Wikipedia users, a fact which helps Wikipedia editors identify vandalism more quickly (any edit by an anonymous user is worth checking out, especially on disputed articles).

If Dave's friend had seen the article at the wrong time, it might have looked very bad, and certainly this is the impression they got, whilst later viewers looking at it see nothing wrong with it (let's leave aside the two sets of viewers obvious bias). The ephemeral nature of Wikipedia edits is one of the main problems that I have with trusting it for anything other than fun research on hobby topics (like Vikings). Yet, increasingly, we see news websites referring people to Wikipedia for detailed information on a specialty topic (I've seen this at least twice myself from news.com.au).

I doubt that there's an easy answer to this issue, other than suggesting that people use more than one source for facts, and take anything they read with a grain of salt. This does speak to the issue of whether wikis are appropriate tools for the enterprise environment. Whilst they are great at capturing corporate knowledge, they are just as good at enshrining stupidity and promoting divisive views. But perhaps that is their real strength, the ability to lift the veil between people at work and reveal the real talent or lack thereof? To expose dramas and stresses that are hidden below normally civil exteriors?

Long Tail Wisdom

Chris Anderson's Wired article, The Rise and Fall of a Hit is an extract from his book The Long Tail that I've read a lot about, but not actually read myself. Coming after yesterday's post it is interesting how it highlights the way that the hit mentality is evident in the world outside of music/movies:

If it’s not a hit, then it’s a miss. It has failed the economic test and, therefore, never should have been made. This Hollywood mindset is now how we allocate space on store shelves, fill time slots on television, and build radio playlists. It’s all about allocating scarce resources to the most “deserving,” which is to say, the most popular.

Fred Wilson (the guy who coined the term Freemium) has this to say:

... I believe VC fund sizes have gotten very large requiring ever bigger winners to move the needle. When I started in the business 20 years ago, a $100mm exit, generating $20mm in value to our fund was always considered a big win. For many of the VC funds today, that would be a yawn. And that's a problem because for many entrepreneurs, a $100mm exit is plenty big, particularly if they can figure out how to hold on to 20+ perecent [sic] of the company before the exit happens. The $100mm exit moves the entrepreneur's needle but not the VC's. That's a problem.

It's a problem because it generates a chasm between entrepreneur and VC expectations, one that may well be leading good ideas to not find VC funding, and therefore get trapped in the “lifestyle” business stage more because there is a lack of VC vision, than it suits their business model. The VCs are still trapped in the Hits model, but the market has moved on from them.

This seems to be happening in many different areas, for example, makers of tabletop/pen-and-paper roleplaying games (RPG) are bemoaning the death of the industry as they know it. This is largely because the market has fragmented, and other than a handful of successful companies, the average RPG publisher is working on it as a hobby, a part-time, or at most marginally successful business.

Chris Anderson claims it has had broad impact; “Practically every other sector of mass media and entertainment has witnessed a similar shift away from hits.” He points to popular music, movies, TV and even best-selling novels as all exhibiting a move of consumers away from the mega-hits, to exploring more specific niche selections. If Web 2.0 companies are aiming their products/services at the consumer market, then this fragmentation is both good and bad news. Good news in that there is a place in the market for almost anyone, bad news in that it is becoming increasingly difficult to clearly capture enough of the market to justify the capital expenditure required to develop the products/services being offered.

I think that increasing numbers of entrepreneurs will have great ideas and launch them using their family/friends' capital, but fail to either attract enough of the market to continue to fund growth internally, or to promise to move the needle enough to attract VC investors. My answer for them is to look towards natural aggregators of users, and in one sense that is exactly what the large enterprises are. The Web 2.0 edge in that enterprise market must surely be that users can be attracted and looked after as individuals consumers first, and then second become evangelists for the Web 2.0 product within the enterprise itself. Leave it to IBM to employ a thousand salespeople to win over the CIO, Web 2.0 will win through guerilla tactics, winning the users heart and minds, and taking the IT department by surprise!