5

//long rant ahead!

I need to plan a Wiki with SharePoint for not connected Sites.
Im now in dispute with my CoWorker since 3 Months, this is how the conversation goes. My two bosses are involved in this and also unhappy about SharePoint.

[C refers to CoWorker, M for me]
C: Hey, we finished SharePoint with Selfservice Storage Rooms. They even have a Wiki.

M: Okay cool, will check it out

C: Well we need to also plan the Wiki inside, I already asked our Department Head and he agreed, that you will be the one.

M: Okkkkaaayy, normaly it's your job to do such things, but welp, I will look into it, if we can work with it.

(2 Weeks pass)
M: I checked SharePoint out and tested everything. The Wiki is a Nogo, we need a other solution or programm for ourself a Wiki Integration/Engine. Did you maybe check out Confluence? It has also a SharePoint integration plugin.

C: We wont do Confluence, too expensive (already overspent the budget for SharePoint in six digits 🤬). Also we wont add to SharePoint Custom Code, it needs to stay standard.

M: Thats impossible, SharePoint Wiki is shit and also handels sites just like documents, no brain behind! Also you overspent the Budget and now it's my Problem?!

C: You need to do the best out of it.

(3 weeks passes and we get a meeting with the department heads)

M: Alright I made a UseCase and documented where the essential flaws are in SharePoint Wiki and why we cant use it.

Boss: Ok if it's impossible to use, then we will stay on our Fileserver for Documents and wont use SharePoint.

M: Thats not my Point, my statement is, as status today, SharePoint Wiki is not the right solution, code or buy software to it.

Boss: We will do a Prove of Concept, if it doesnt work then we will aboard it.

M: Well it is only some missing essentials, like hierarchy and Groups for the Pages, Example Confluence has this. If we could built in this features in SharePoint, everything would work out.

C: (angry) I told you that we wont use Confluence!

M: (calm) I said we need Features, not Confluence. Please mind the consent.

(3 weeks passes, and one more meating with bosses)

M: alright here again is a analyses, why already in Theory the current SharePoint Wiki wont work. It's already flawed in the core.

Boss: Yea SharePoint is crap, I checked out confluence and thats a real Wiki.

C: Well I dont know anything about Confluence and never looked at it. But if SharePoint is a fail we need the Proof of Concept.

M: Why do we need to do a Proof of Concept, when it already doesnt work in Theory! Thats nonsence and unlogical.

Next meeting will be in 4 weeks and I will give him the FUCKING PROOF OF CONCEPT. I will be a Bastard and build behind CoWorkers back a Confluence Wiki to show the Departmentheads how to built it right.

I hate CoWorker now, he makes a part of my loved Job a hell, I will goddamn cuk Coworker to space, that fucking Cukatron of lazyness and shit 🤬. I provide the Solutions and you just say no, how dafuq will the project advance, if you always say NO! Are you so unflexible and fixed on your Castle of Ignorancy!

Comments
  • 2
    So in short, dickhead co-worker checked one type of solution, was adamant about using it and didn't bother to check alternatives even if asked so?

    Damn. Nice rant, tho
  • 4
    Sharepoint is a shit enviroment needs to be deleted
  • 4
    I know that anger in the stomach but as a fellow dev I suggest you to chillex.

    There is no point in getting angry because in the end you have a bad time.

    I'm too working currently with morons but I just keep it cool
  • 1
    @Asbetha We are on DevRant.
  • 0
    @psukys yep, thats also something I thought. He saw Wiki in SharePoint and didnt test it out.
Add Comment