Last week a user couldn't find a document in sharepoint. Typed (what he thought) was the exact file name in the search -> no results.

I know how to get 'under the hood', so I looked where I thought the file was, found it, and it was exactly as he searched for it. What the hell? Wasn't a new file, it wasn't moved/renamed, no reason why it couldn't be found.
I 'touched' the file. Waited 5 minutes and searched again, found it. What the frack Microsoft!

With millions of convoluted abstraction layers upon a simple concept like document storage, not even MS themselves know what the fuck is going on there.

maybe you don’t pay enough bucks so they evict search index when you’re reaching certain capacity

@vane > "maybe you don’t pay enough bucks"

We're using SharePoint 2016 on-prem.

It's happened before, some file/list 'thing' hasn't been updated/viewed in X years and no amount of searching will find it. Then when it's viewed/updated, all of a sudden it shows up.

I care zero when an accountant wants some random spreadsheet they haven't seen in 5 years (just to see if some column still has a 7).

My blood boils when someone says "I would have fixed the error, if PaperTrail would have documented the process. We searched the intranet and it's not there." and *I know* I wrote the document.

I search, nope not found. I then I poke around our folders and find the doc. I re-search with the same string...then it shows up.

TL;DR, I've contacted support and their response is/was the equivalent of "Have you rebooted the machine?"

@PaperTrail xD This is 8 years old software. I can compare that with asking 80 years old man how he’s doing and if he shit his pants again.

@vane > "This is 8 years old software"

It was 'cutting edge' at the time, the last on-prem version of SharePoint Microsoft was going to offer.

We are licensed for SharePoint Online and confident 90% of our content would "just work", but it's the remaining 10% that wouldn't work and the company is falling back to "Oh well. If it ain't broke..".

The company is using M365 with Sharepoint on Cloud, after I did the migration from some other solution.
Wow, I thought Sharepoint was bad, I never imagined it was this bad.

@PaperTrail why don’t you switch to the opensource solutions then, I fucking don’t understand those companies - like they’re paying millions for SASS and that would cost fraction to hire developer that would wrap couple of opensource solutions with authentication and deploy them on k8.

Clearly management still thinks you need to buy things because we used to do it in the old days. That’s the whole problem of IT, people don’t understand where all of current software comes from but they use it.

As I see how opensource is beating those multibillion dollars products I have a good laugh.

@vane > "why don’t you switch to the opensource solutions"

Outside my pay scale. Like a lot of companies of any size, there is a lot of internal politics involved. Going to opensource may solve one problem, then introduce 10 new ones.

The book "The Unicorn Project" illustrates this perfectly.

@PaperTrail obviously we won’t change it now or in any possible future, it’s just part of human nature.

The lack of cooperation and agreement is what defines humanity after all.

@vane > "As I see how opensource is beating those multibillion dollars products I have a good laugh"

Just found out we (upper mgmt) are seriously considering replacing/migrating a highly customized (embedded JS, CSS styles, XSL styles, etc) business critical SharePoint list (manages all the company's projects) to Jira. My boss has already written an app to port the SharePoint data to Jira.

May the Lord have mercy on our souls.

@PaperTrail jira is actually nice software you can spin up docker and write a plugin in a week without problem, compared to azure jira is ferrari

@vane > "jira is actually nice software"

My boss is pushing the system replacement to be developed in-house because "we can".

He's a level 10 intellect capable of building rube-goldberg machines Rube-Goldberg would say "Whoa...stop...that's too complicated"

Came back from a meeting with upper-mgmt and I'm pretty sure he sold them developing it in-house would save us money.

@PaperTrail I think the biggest challenge with software migration is data migration so being able to build those kind of machines comes handy during migration time and building proof of concepts.

It's just how most of R&D in software works to be honest. You take two pieces and crap and you connect them together like obviously database and webserver and you suddenly are getting rest api and you can say that's nice but why we're sending those 20MB xml if we need key value objects or why we are sending those things synchronously if most of the time we spend waiting for data transmission.

Here we are 20 years later instead of wsdl sending json files, instead of thread pool applying async await pattern or as it was used to call 50 years ago actor model.