Sunday, November 25, 2012

Accounting 2.0

I've been working on this post for a while now, on and off, wanting to provide something that would be fairly comprehensive when it comes to evaluating the Accounting SaaS offerings for your needs.

The solutions reviewed here range from simplistic to very involved (almost ERP in traditional enterprise jargon) and I think span a wide range of approaches and needs.  I hope that the analysis and classification below will help you with decision-making. 




As usual, please let me know what you think

Monday, November 12, 2012

SharePoint 2012 Conference

I am among those who have not made it to SharePoint 2012 but very interested in SharePoint 2013 and more specifically what Microsoft's got in mind for the Yammer acquisition.

This keynote seems to do a competent job giving a good overview of the product and the strategy.  I skimmed through quickly and must say that so far I'm fairly impressed with the product evolution, but underwhelmed with Yammer strategy - seems like the acquisition was quick and loose and MS haven't got a clue in how to merge the 2 products together yet..

Here's a link to the keynote so you can form your own opinion:



(at first I posted the video in the original MS Silverlight format/player but while the quality was excellent, everything else made for an awkward experience - from messing up the blog editor, to lacking the video controls, to no way to turn the auto-play off; wonder if this is what's plaguing MS - while some pieces are good, there's no cohesion..)

P.S.  Just read something interesting - SharePoint 2013 was in development for 3 years.  This day and age 3 year development cycle is simply unacceptable as it's a guarantee that by the end of 3 years your requirements dramatically and market has moved in number of different directions.  My prediction - it's a dud and Yammer will replace SharePoint soon.

P.P.S  Microsoft literally wrote a book on Waterfall Software Development model.  It was a big book (over 700 page), a book that reflected the SW development culture at the time.  That world is gone, but I can see how this is probably hurting Microsoft in more ways than one, and it explains the 4 year OS cycles and 3 year product cycles (if they are lucky)