|
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.
|
|
|
|
|
Thanks not easy at this time, get some agents phoning me to find out if I have any roles available (?), buy 'Stuff' I meant AVI video files, configuration data, docs & diagrams of how to connect widget A to Widget B with letting the magic smoke loose! The test are being converted by myself and another to JIRA via Zephyr (or whatever!) the Chief is a big 'Jira Ninija' and got upset by people trying to use Jira like a relational Database...
|
|
|
|
|
Also late to the party...long-winded too  And, good luck on your job search!
TL;DR - The single act of purchasing new tool is not going to solve an organization's problems. One must set up conventions and workflows for the tool to optimize team collaboration for the organization.
I have found in my "travels" that there is a misconception typically at the decision-making-level in organizations, that these types of tools (GIT, SVN, VisualSourceSafe, Sharepoint/Confluence, JIRA, Wikis, and bunches of others) and the features they provide, once purchased, make all your problems go away without any additional work. The flawed assumption is that the tool forces a specific workflow and thus forces team members to use the tool in just one way and by doing so, creates a single organizational structure for the data to be stored, which we all know is not correct - instead of the desired/assumed "file cabinet" for data (project docs, source, etc.), these tools become "junk drawers" (often referred to as the "wild west") where teams don't know what data is where, what is the latest version, identical doc's are stored in different locations/folders causing data coherency issues, nobody knows what is in the master/trunk branch (or tags or any of the other branches) - and it gets worse and worse as time goes by.
The key to team success is, once the tool is purchased, one or a few people build up a moderate level of expertise so they know best how to use the tool then create (and document) a structure (branch definition for source tools, folder structure for doc tools) and workflow that works best for all the organization's requirements, then get buy-in/agreement, and put in the constructs (like varying access rights per group) prior to its use, and police it's use (which can be time-consuming) during its use.
Mind you, for those that do contracting, you are often forced into the customer's source control/configuration mgt structure - sometimes a good thing, sometimes not.
In agreement with others on the post, using a source control tool like git/GitLAB/BitBucket/Subversion for documentation control is not a good idea - Subversion/Confluence tools are more appropriate. I find source control tools deal best with text-based files (like code), but not well with binaries (like MS docs, etc.) wrt version control.
Since I work for a small company, we have shied away from those complete solutions from Atlassian that are costly (JIRA/Confluence/BitBucket). We do use Atlassian JIRA for tasking/bug tracking, cloud-based Sharepoint for documentation, and internal GitLAB for source control. There is some use of Subversion, but find git more intuitive/logical although I have found the git paradigm is confusing when you first get started
|
|
|
|
|
Quote: you are often forced into the customer's source control/configuration mgt structure - sometimes a good thing, sometimes not.
Which how non source code was stored in GIT, because the other version of online storage we could use had no tracibility!
|
|
|
|
|
SharePoint or Team Foundation Server?
|
|
|
|
|
Teams Foundation Server, sounds interesting we use teams to miscommunicate with each other...
|
|
|
|
|
I think they were referring to TFS Team Foundation not Teams, Microsoft's source control offering rather than the chat app, built into Visual Studio, the old VB6 used to have one called Source Safe or something like that.
|
|
|
|
|
Sharepoint is a document management system and would not be very efficient for source\version control.
GIT on the other hand is for source\version control of your projects.
If your supervisor is trying to use Sharepoint for source\version control and there has been no enhanced additions or modules to support such features than this supervisor is an idiot...
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
Depends what you're using Sharepoint for. It sucks for use as a Wiki. That's the sum of my experience.
|
|
|
|
|
I wanted to make sure my SO woke up with a smile on her face this morning.
I'm not allowed to have Sharpies in the house anymore. 
I'm hiding from exercise...I'm in the fitness protection program.
JaxCoder.com
|
|
|
|
|
Mike Hankey wrote: I'm not allowed to have Sharpies in the house anymore.
It's lucky your hobby isn't storm watching.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: It's lucky your hobby isn't storm watching
I keep expecting a wh covid briefing with a sharpie adjusted chart! 
"Go forth into the source" - Neal Morse
|
|
|
|
|
You need a new plan. Back to the drawing board!
|
|
|
|
|
The backward generation killed little Helen’s pulse(11)
|
|
|
|
|
Millennials?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Yes,
Killed - slain
Little Helen - nell
Pulse - Im
And then put it all backwards
|
|
|
|
|
Bugger! I was making a joke ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
That means you must win tomorrow ( we all know you like winning Fridays ) so it better be good - with this lock down I haven't got much else to amuse myself with { evil grin }
"We can't stop here - this is bat country" - Hunter S Thompson - RIP
|
|
|
|
|
That's easy - there is nothing in the rules says I can't answer my own CCC ...
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
Did you hear about the confused and constipated mathematician? He worked it out with a pencil.
|
|
|
|
|
I've heard that the main character is a real pain in the butt! 
Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
Never argue with a fool. Onlookers may not be able to tell the difference.
Mark Twain
|
|
|
|
|
It was really crap anyway!
I'm hiding from exercise...I'm in the fitness protection program.
JaxCoder.com
|
|
|
|
|
ah, poop jokes. they never get old. lots of fun for all ages.
my kids and I were laughing and joking about diarrhea at the dinner table last night.
poop, farts, its all good wholesome fun.
|
|
|
|
|
It's the difference between growing old and growing up.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
