You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
4I think you are judging them if you think they're only interested in facts with dollar figures. And they might want terse explanations because verbose explanation can trick them into something they don't understand. The best approach is perhaps giving out a list of good things that Git has but ClearCase does not. Nevertheless, I feel corporate environment executives don't trust open source software especially if there is a well established enterprise version.– InformedACommented Aug 6, 2014 at 4:42
-
8recommended reading: How do I explain ${something} to ${someone}?– gnatCommented Aug 6, 2014 at 4:48
-
2Demonstrate how much more using git makes you (and the other teams) effective in doing your duties. Do not volunteer replacing ClearCase without hearing the case for it, but show where the day to day benefits are. ClearCase may be required for build auditing or project wide issue tracking which Github is not strong in.– KevinCommented Aug 6, 2014 at 4:59
-
3If they're interested in dollars, show them the annual ClearCase licensing fees and the staff you have to pay to maintain it.– 17 of 26Commented Aug 6, 2014 at 13:41
-
3"put on hold as primarily opinion-based " I very much disagree with this. From my question "What I'm trying to find are concrete facts demonstrating developers work more effectively with Git." What is opinion based about that?– MikeCommented Aug 6, 2014 at 17:21
|
Show 8 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>
[example](https://example.com)
<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you