|
I'm still trying to find our what "Je ne sais quoi" means. No one I ask seems to know.
|
|
|
|
|
|
|
Hi All,
My current employer (for how long but that another issue!) is trying to move to having all 'stuff' online (well lets give them some credit!) GIT was used to track some files (not source code!) and now are we use Sharepoint, first thing is this right, I was fairly certain we shouldn't use GIT but is Sharepoint the right thing to use? 
Glenn
|
|
|
|
|
Kneejerk reaction:
They are going to make you redundant, so who cares if they are going to screw stuff up. You won't be there to endure the pain.
Real message:
Actually, I know nothing about Sharepoint except the fact that other parts of my company use it and I sometimes have to view a document linked via an email.
Seriously, it shows your character that even though they are letting you go, you care enough to worry about how they move forward.
|
|
|
|
|
Well it's my role, so they might find something else for me to do. In my experience trying to leave stuff your doing in a goodish shape can do you some good (I don't need no negative Karma, man!)
|
|
|
|
|
glennPattonWork wrote: Well it's my role,
...
In my experience trying to leave stuff your doing in a goodish shape
Karma aside... that's the difference between professionals and [fill the gap with your favourite word here, I just want to keep it respectful].
You don't do your work well for them, you do it for yourself. They pay you for it until the last day.
Ethics or fairness about the redundant job... that's another topic.
But I do respect your position here. 
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Well I have to admit, it's not my office thats caused it, it's the incompetance of those higher in the food chain, not knowing what or how we work. This has taught me a lesson though, take pride in what you personally do. I haven't been given the official chop yet, just notice. So the climate being what it is I am preparing for the worst. I think I would have left anyway, I wasn't really making use of the skills I have... Plus a comment from my employer saying I did shoddy work on my way out might not be nice!
|
|
|
|
|
My experience of SharePoint is that it is the storage equivalent of a Black Hole. Once a document has been saved, it passes some kind of Event Horizon and is lost for ever, I do not know how many hours I have spent looking for documents in it only to admit defeat and rewrite them from scratch.
|
|
|
|
|
@Mark-Wallace said something good about a product that you hate?! This has got to be one for the record books!
|
|
|
|
|
Well at least it wasn't Christian Graus - that would have required a universe reboot with a different operating system ... 
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Same here, it so secure even the depositer can't get it back!!! 
|
|
|
|
|
For non-source-code files, I have to admit that SP works well -- as long as you switch to "classic sharepoint view" every time you open it (otherwise you have to deal with all the time-consuming and energy-draining recent "improvements").
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
SharePoint seems like the right thing you are looking for:
This is a decent informational article:
What Is SharePoint? - dummies[^]
article said: SharePoint is most often used for the storing of version-controlled documents, such as Word documents and Excel worksheets. In many environments, email is used for passing documents back and forth between users. The potential for mixing up different versions of the same document is considerable. Also, storing multiple copies of the same document takes up a lot of disk space. Because SharePoint provides a single source for storing, viewing, and updating documents, many of these issues are eliminated.
|
|
|
|
|
I despise SharePoint (and GIT), but it is the right tool for some things. Mostly things which no one will ever want to read.
|
|
|
|
|
Has your employer switched to Office 365? If so, then SharePoint is definitely the right way to go. While you're at it, pull up Teams and start playing with it.
|
|
|
|
|
Oh have we ever, spent most of the day in Teams calls Q&A with the a suit etc. 
|
|
|
|
|
Yes and No.
GIT works quite well, I do still prefer the older SVN/CVS though, but personal preference and all that jazz, I use it most days and you get used to it.
Sharepoint, meh, marmite, you either love it or hate it, people use it for storage but I believe it was designed originally for document collaboration, I wouldn't go around replacing all of my NAS shares with it but for documents I guess it does what it says on the tin, as for organising I guess that depends how the people running the show are organising the folders, it *can* be made to be more intuitive than not, but you need someone who understands folder structures well enough to do it for you.
Having most things cloud based means you can work from home more efficiently (unless you need access to specialist equipment / hardware), though i'd have no problem working over a VPN to an actual NFS, again, if you have a network department that knows what they are doing. Most i've come across, small or large corps do not, someone's cousins son set it up etc or someone is still trying to figure out where they can plug their 10baseT coax into.
|
|
|
|
|
Sharepoint has changed much over the years. We hosted Sharepoint Server back in the 3.0 days or whatever it was (some 10 years ago). It turned out to be a solution to a problem we didn't have. When we tried to use it for collaboration on Word documents, people would check stuff out and not check it back in, put it in the wrong place, etc. We trashed it. A couple of years ago, we shut down the Exchange server and moved to O365. Sharepoint now has solutions we can use, again collaboration on sales quotes and other documents. Also hosts price lists and calendars and other corporate documents. The users files sync to the users computer, similar to One Drive. It does have decent search capabilities.
I think you have to be prepared to do some development to enhance it. I have created some stuff.
examples:
Created an Excel Add-in that allows users to use a Template for their quotes and publish to their folder in a Sharepoint quotes library. It syncs to the folder on Sharepoint. Perhaps some this can be better done with content types. All people who handle quotes have a folder and have access to the library (some read only).
Created a console program that downloads any new or changed quotes (including 5 layers of history) to the file server every night.
Created a desktop program that allows searching through the quotes stored on the file server, and creating reports ( ran too slow going up to Sharepoint).
Created a LookOut add-in to allow linking to a quote template from an email contact (still a work in progress).
To me, Sharepoint is somewhat like a database server. After you set your first one up, you realize where you screwed up and are ready to start over. For those of us in the slow group, it seems to be recursive.
I would suggest that you jump in with both feet, create some applications/add-ins and make yourself indispensable.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
I must admit, I haven't played with the new version the older version had a limit on file size, I think you to just under 1 floppy...
|
|
|
|
|
I've been told the SharePoint does some rather cools things, but I've never seen them, because, from my experience, 99.9% of places just use it was a fairly lame wiki.
Using Git to store files that aren't versioned text files, would seem pointless and counterproductive. A DropBox/OneDrive/GoogleDrive would seem better.
Truth,
James
|
|
|
|
|
The use of GIT caused people to ask 'why!' to which I had to give the lamest answer: 'I'm only obeying orders' GoogleDrive was rejected as not secure enough, OneDrive as too secure and to easy to delete & Dropbox was not as far as I am aware discussed. It's just with 365 Sharepoint is being used to store everything! I did as as 'it might be good if these thing' (images, png's which were derived from some PDF Documentation) 'could be stored in a directory' to which the reply was 'Meh!' using teams has not improved people skills.
|
|
|
|
|
late to the party, but ...
I was asked the same sort of question on my last contract - It would have been nice to be able to suggest Sharepoint - but the company wernt anywhere near where they needed to be skills-wise given we were just beginning to get them set up on O365
The top two thoughts I had, and I stipulate this very carefully, 'based on their requirements', were
GIT, with GIT LFS and SparkleShare
Umbraco CMS (or similar)
Since they had a lot of Azure going on, if I could have found a 'file manager' view suitable for management to use, over Azure File Storage, that would also have been a hot contender (I'm sure there are such products around, but being a start up $$ come into play)
|
|
|
|
|
Ah welcome to the MS family, with 365, SQL Server, VS, Teams and now sharepoint your organisation is truly part of the clan. Not a bad thing but you are now susceptible to all the different servers that they can foist on you. Once you get past the tipping point (and that was probably 365) there is n going back.
When the sales person says they all integrate and work together laugh in his face.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
Glenn,
First, good luck on your presumed job search.
It might depend. I'm not a fan of Sharepoint in the least, but I could see where it might be useful for storing documentation. More specifically, general docs like process documentation (here's how we branch & merge), HR docs, etc.
If by 'stuff', you mean 'technical stuff' like source code, then, no, that doesn't seem like a very good solution. Even project docs like requirements and design (to me) need to go in a change control system like jira or whatever.
Look at me, advocating using jira/whatever when (as my current employer already knows), email is a perfectly valid change control system.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
