4 ms·

It's a horrible product

by dagurp 10y ago

cyberferret 10y ago
Sharepoint should have been a great product for small to medium businesses, as well as government departments but yeah, it had horrible, horrible implementation and deployment issues. How I wish it had less .Net centricity and more adaptability to build or consume services in other languages and protocols - it could have been a killer business platform...
- bigger_cheese 10y ago
  I work for a pretty large organisation (multiple office sites, multiple countries etc). Our intranet runs on sharepoint and every time I've had to edit a page or create a new page etc I find it frustrating as hell and don't get me started on permissions problems. From the users perspective it is pretty handy. There are a heap of non technical people (HR, accountants, operators etc.) Being able to drag and drop spreadsheets from a Windows desktop into a sharepoint library is almost a killer feature makes it very easy for non technical people to collaborate on documents across multiple sites (provided the aforementioned permissions problems do not occur). Our plant operators use it to upload overtime spreadsheets and share them between shifts, people use it to share powerpoint slide decks for meetings and upload the minutes afterwards etc. I'm from the generation before we had Sharepoint back then we used Mapped network shares to move documents around (or emails - but we had 50mb limit imposed by exchange) - permissions issue were even worse. We recently started using Facebook's "Workplace" which is basically a private facebook instance for our organisation. People are starting to use that instead of sharepoint - from what I've seen anyone can make a "group" in workplace and it is so much easier then setting up a sharepoint page. Adoption is pretty slow but some teams are starting to use workplace groups rather than sharepoint for recurring meetings etc. So I'm hoping it will finally kill Sharepoint here.
  - nol13 10y ago
    "don't get me started on permissions problems" was good fun when we found the sharepoint document with results to personal surveys showing up when you search for peoples names on the intranet
- flukus 10y ago
  Even when you know .net it still feels alien. When it comes to custom development it's much easier to create an app from scratch than it is to integrate with sharepoint.
  - doggydogs94 10y ago
    Unfortunately, when you move on to another job, your "much easier" app becomes an orphan. I have seem this happen multiple times. The hot shot developer creates his own thing because it is too much of a hassle to do in SharePoint. Then the developer moves on. And the "much easier" app slides into a slow decline and one day dies because nobody know how to fix it.
    - flukus 10y ago
      I'm not talking radical new technologies, just a basic MVC site that the replacement should be able to deal with.

It's a horrible product

by dagurp 10y ago

It's a horrible product

Sharepoint should have been a great product for small to medium businesses, as well as government departments but yeah, it had horrible, horrible implementation and deployment issues. How I wish it had less .Net centricity and more adaptability to build or consume services in other languages and protocols - it could have been a killer business platform...

bigger_cheese 10y ago
I work for a pretty large organisation (multiple office sites, multiple countries etc). Our intranet runs on sharepoint and every time I've had to edit a page or create a new page etc I find it frustrating as hell and don't get me started on permissions problems. From the users perspective it is pretty handy. There are a heap of non technical people (HR, accountants, operators etc.) Being able to drag and drop spreadsheets from a Windows desktop into a sharepoint library is almost a killer feature makes it very easy for non technical people to collaborate on documents across multiple sites (provided the aforementioned permissions problems do not occur). Our plant operators use it to upload overtime spreadsheets and share them between shifts, people use it to share powerpoint slide decks for meetings and upload the minutes afterwards etc. I'm from the generation before we had Sharepoint back then we used Mapped network shares to move documents around (or emails - but we had 50mb limit imposed by exchange) - permissions issue were even worse. We recently started using Facebook's "Workplace" which is basically a private facebook instance for our organisation. People are starting to use that instead of sharepoint - from what I've seen anyone can make a "group" in workplace and it is so much easier then setting up a sharepoint page. Adoption is pretty slow but some teams are starting to use workplace groups rather than sharepoint for recurring meetings etc. So I'm hoping it will finally kill Sharepoint here.
- nol13 10y ago
  "don't get me started on permissions problems" was good fun when we found the sharepoint document with results to personal surveys showing up when you search for peoples names on the intranet
flukus 10y ago
Even when you know .net it still feels alien. When it comes to custom development it's much easier to create an app from scratch than it is to integrate with sharepoint.
- doggydogs94 10y ago
  Unfortunately, when you move on to another job, your "much easier" app becomes an orphan. I have seem this happen multiple times. The hot shot developer creates his own thing because it is too much of a hassle to do in SharePoint. Then the developer moves on. And the "much easier" app slides into a slow decline and one day dies because nobody know how to fix it.
  - flukus 10y ago
    I'm not talking radical new technologies, just a basic MVC site that the replacement should be able to deal with.