Re: Advertising the Git User's Survey 2011

From: Ramkumar Ramachandra <artagnon@gmail.com>
Date: Oct 2, 2010, 06:20 UTC
Message-ID: <20101002062056.GB16626@kytes>
In-Reply-To: <AANLkTim1mLhQnJPT9KiinR4L3C=O9L=V9M3X9x7Cr+oC@mail.gmail.com>

Hi Jakub and Ævar,

Ævar Arnfjörð Bjarmason writes:

Show 6 quoted lines

> On Mon, Sep 20, 2010 at 13:38, Jakub Narebski <jnareb@gmail.com> wrote:
> 
> > Currenly the survey has more than 5000 responses (in a not whole month)
> 
> That seems somewhat low, but maybe people just aren't that interested
> in taking surveys.

Nice work on the survey! This is our best year by far. Some general observations:

Interesting statistic: 24508 people viewed it, 7821 people completed
it, but 0 people started filling out information and later decided not
to submit it. It could mean that many people clicked through and found
the survey, but probably left because it looked too long at a glance?
The average time spent on the survery is 34 minutes
- I think we can bring that down to 10~15 minutes if we design
questions to extract more information. Also, there's little incentive
for taking the survey: while many companies actually give out
discounts/ coupons for taking surveys, the least we can do is present
real-time results in the most interesting manner possible ie. survey
takers should see the "results so far" immediately after taking the
survey; some visualizations such as pie charts?

In questions 5, 10, 12, 13, 16, cut down out the options that have very few respondents and let them all go into "other". It probably doesn't actually save the survey taker any time, but I think seeing a long page with many options can be scary.

1. Country of residence: we can probably make this a nice click-on-map
   interface as opposed to freeform text. It'll be more useful to us,
   and more interesting to users when we advertise the results.
2. Age: Maybe we restrict the input to 2-digit integers and draw a
   graph with all these integers to show a mean, median etc?
11. Just change this to an optional sometimes/ often? Why should users
    spend time clicking on "never"?
17, 18: Merge perhaps?
24, 25: Merge into single question with options: "Yes, and my problems
        are solved more often than not", "Yes, but my problems often
        remain unresolved", "No, I don't go to others for help".
26, 27: Merge into "How do you talk to other people using Git, either
        for technical help or otherwise?"

Ofcourse, I understand that there must be some technical constraints due to which some things are not implementable (eg. survs doesn't provide the feature?), but I've not taken that into consideration.

-- Ram