The Brief

Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

_V_ replied

27 May 2021, 16:33
Originally posted by vetran View Post

Yet for some reason every Fortune 500 has it somewhere important.

Oddly enough most places I've worked lately use Atlassian products such as Confluence and JIRA, SharePoint is nowhere to be seen (been decommissioned there) and the SharePoint team removed.
Leave a comment:
vetran replied

27 May 2021, 16:16
Originally posted by eek View Post

It's Sharepoint - a bodge of multiple things combined to destroy Lotus Notes...

If you think the front ends are a mess, the backend is way worse.

Yet for some reason every Fortune 500 has it somewhere important.
Leave a comment:
AtW replied

27 May 2021, 13:42
Inntresting…
Leave a comment:
eek replied

27 May 2021, 13:03
Originally posted by ladymuck View Post

Maybe back end it makes sense but the user side is a challenge and full of really annoying inconsistencies. Definitely developed by different teams with different coding standards.

It's Sharepoint - a bodge of multiple things combined to destroy Lotus Notes...

If you think the front ends are a mess, the backend is way worse.
Leave a comment:
Great Britten replied

27 May 2021, 13:00
Originally posted by ladymuck View Post

Maybe back end it makes sense but the user side is a challenge and full of really annoying inconsistencies. Definitely developed by different teams with different coding standards.

Yes, my post was from a front office perspective
Leave a comment:
ladymuck replied

27 May 2021, 12:38
Originally posted by vetran View Post

Sharepoint was Microsoft's response to Domino web server sharing databases. That and a few other DMSs.

It won because technically it was far superior. Having to restart the webserver for every change even in 2003 was ridiculous.

The back end is supposed to be secret and you use APIs. But if you look hard people do explain the secrets.

The back end has been similar since 2003 when I first met it. I managed to understand it when I needed to do things the APIs didn't do.

It is now a complete development environment for portals and collaboration.

I am a fan and have built a number of solutions based on it. It is one of the best ad hoc ways of getting low volume manually added data into SQL server because SP takes care of the interface and security easily.

Maybe back end it makes sense but the user side is a challenge and full of really annoying inconsistencies. Definitely developed by different teams with different coding standards.
Leave a comment:
vetran replied

27 May 2021, 10:37
Sharepoint was Microsoft's response to Domino web server sharing databases. That and a few other DMSs.

It won because technically it was far superior. Having to restart the webserver for every change even in 2003 was ridiculous.

The back end is supposed to be secret and you use APIs. But if you look hard people do explain the secrets.

The back end has been similar since 2003 when I first met it. I managed to understand it when I needed to do things the APIs didn't do.

It is now a complete development environment for portals and collaboration.

I am a fan and have built a number of solutions based on it. It is one of the best ad hoc ways of getting low volume manually added data into SQL server because SP takes care of the interface and security easily.
Leave a comment:
_V_ replied

27 May 2021, 09:51
Software development at big companies, has more in common with those guys and girls that deal with tulip covered fatburgs in sewers, than computer science or engineering....
Leave a comment:
_V_ replied

27 May 2021, 09:50
To write a <insert every tulip bit of software I seem to find at client companies> system full of nebulous concepts and terminology that's littered with undecipherable GUIDS that take a lifetime to cross reference in order to work out what you're actually looking at all backed up with a scant library of amibiguous documentation.
Leave a comment:
ladymuck replied

27 May 2021, 09:43
SharePoint is dire. Has been for a long time and all the plasters they keep sticking on it don't help.

Am discovering that certain features are restricted if you use SharePoint that's a Teams site vs SharePoint that's a Site Collection, and then you get different features depending on what "type" of Site Collection you make. Then there's the different syntax used in different places
Leave a comment:
Great Britten started a topic The Brief

27 May 2021, 09:37
The Brief

To write a document management system full of nebulous concepts and terminology that's littered with undecipherable GUIDS that take a lifetime to cross reference in order to work out what you're actually looking at all backed up with a scant library of amibiguous documentation.

Was that the brief for Sharepoint?

And don't even get me started on Power Apps and Flows.

(Current role is to migrate MS Power Apps/Flows -> React but keep the Sharepoint bits )
Tags: None