From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git User's Survey 2009 partial summary, part 2 - from first 10
Date: Tue, 18 Aug 2009 17:54:52 +0200 [thread overview]
Message-ID: <20090818155452.GA12938@vidovic> (raw)
In-Reply-To: <200908171224.44686.jnareb@gmail.com>
The 17/08/09, Jakub Narebski wrote:
> Git User's Survey 2009 partial summary, part 2 - git difficulty,
> proficiency, uses, install, OS, editors.
Thanks for these partial summaries.
> 3) Have you found Git easy to learn?
> 4) Have you found Git easy to use?
> (Choice - Single answer)
>
> ================================================
> Answer | to learn [%] | to use [%]
> ------------------------------------------------
> Very easy | 4% | 9%
> Easy | 20% | 36%
> Reasonably easy | 55% | 45%
> Hard | 19% | 8%
> Very hard | 2% | 1%
> ------------------------------------------------
> Total respondents | 2942 | 2959
> ================================================
<...>
> What's interesting is comparing (percentage) results for questions
> 3. and 4.; how hard is git to learn versus how hard is to use. It
> seems like Git is reasonably easy to learn, and reasonably easy to
> easy to use. So it looks like Git just have somewhat steep learning
> curve, and the difficulty to learn pays in being more powerful to
> use.
I believe it would be interesting to know who (from the question 6.)
think what later. We may expect that people of the grade 4 and 5 ("can
offer advice" and "know it very well") underestimate the difficulty to
learn Git.
Also (and as you said), this "Git's users" survey won't have answers
from unsatisfied users who left Git. We can't rate the number of users
who left Git because they found it too much hard to learn.
> 6) Rate your own proficiency with Git:
> (Choice - Single answer)
>
> You can think of it as 1-5 numerical grade of your proficiency in Git.
>
> ================================================
> Proficiency | resp [%] | resp [n]
> ------------------------------------------------
> 1. novice | 4% | 114
> 2. casual, needs advice | 17% | 520
> 3. everyday use | 38% | 1138
> 4. can offer advice | 34% | 1020
> 5. know it very well | 6% | 192
> --------------------------+---------------------
> Total respondents | 2984
> Skipped this question | 105
> ================================================
--
Nicolas Sebrecht
next prev parent reply other threads:[~2009-08-18 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 10:24 Git User's Survey 2009 partial summary, part 2 - from first 10 Jakub Narebski
2009-08-17 10:44 ` Johan Herland
2009-08-17 21:39 ` Jakub Narebski
2009-08-18 15:54 ` Nicolas Sebrecht [this message]
2009-08-18 17:00 ` Jakub Narebski
2009-08-18 19:55 ` learning curve (aka Git User's Survey 2009 partial summary, part 2 - from first 10) Nicolas Sebrecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090818155452.GA12938@vidovic \
--to=nicolas.s.dev@gmx.fr \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).