|
Not much, really. 
|
|
|
|
|
Fernando A. Gomez F. wrote: since we sell SharePoint projects, we should use SharePoint internally.
For versioning source code?
/ravi
|
|
|
|
|
We sell SharePoint projects for other things but source-code versioning. But the big cheese decided that we should show customers how we're able to get the most out of SP, so...
I've been fighting this particular windmill for over a year now.
|
|
|
|
|
It's amazing that the CEO is making uninformed decisions that are bound to adversely impact developer productivity. With all due respect, he/she needs to get their head out of their posterior and focus on growing the business, not micromanaging in areas where they (obviously) have very little knowledge.
/ravi
|
|
|
|
|
I know. We were a small company, part of a larger group. He used to make all the calls. Now that we've grown, he has to share decisions with me (development management) and another girl (commercial/sales management), but still has the habit of nosing around things he shouldn't. The sales girl has it more difficult than I, as I usually get it my way (except on this and a couple of other things), but still...
The worst part is that, as he claims it, he used to be a software developer back in the 90s. 
|
|
|
|
|
I hear you.
The reluctance to delegate operational control is a common problem, especially with founders of small businesses. It takes maturity, confidence and a certain amount of courage to relinquish control to others. But the consequences of not doing this can be dire. I've seen well-intentioned (and smart) business owners almost bring their enterprise to a halt due to lack of confidence (unfounded, IMHO) in their managers.
/ravi
|
|
|
|
|
Would he know if you switch to something else? 
|
|
|
|
|
Hehe probably yes. Maybe not now, but one day for certain... 
|
|
|
|
|
Hopefully none of your customers understand development - that kind of solution may make them run a mile.
"We're using Sharepoint internally for source control"
"Ha, ha, ha... I think we'll look elsewhere as you evidently don't understand when Sharepoint is the best solution to a problem"
|
|
|
|
|
|
I did use PVCS, but way back in the mid 90's. It was mostly a command line interface back then.
Soren Madsen
|
|
|
|
|
Oh yes. I used it. I still wake up screaming.
|
|
|
|
|
No one else is coding, so I just dump everything into a winzip archive
|
|
|
|
|
|
Even when i do the coding all alone i tend to use git, this enables me to easily look back of what mistakes I made in the past (and repeat them  )
Cogito ergo sum
|
|
|
|
|
Nothing like repeating the same errors. Gotta love that. 
|
|
|
|
|
I too did this for years (at home) until I discovered how easy it was to set up VisualSVN[^] and the AnkhSVN[^] VS plugin (both free). Trust me, you'll never go back!
/ravi
|
|
|
|
|
Agreed, have used AnkhSVN for years and it's a very good product.
|
|
|
|
|
Yeah, I used all that stuff too in my last job. I found it hard to use and cumbersome and makes VS run slower.
|
|
|
|
|
I did that in the late 1990s however when my projects became more complex I moved to CVS then to SVN.
John
|
|
|
|
|
ed welch wrote: I just dump everything into a winzip archive
I just memorize everything...
|
|
|
|
|
I work with SVN, Git, TFS, and SourceSafe.
|
|
|
|
|
I use mostly subversion however public code is on github.
John
|
|
|
|
|
It was when I clicked on it ... so it must have been fixed. Just retry.
|
|
|
|
|
Er... maybe they fixed it but I just managed to tick SVN and GIT.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
