The Devver Blog

A Boulder startup improving the way developers work.

The results of our Ruby development survey

A few weeks ago, we posted our Ruby development survey on the Devver blog. Dan and I wanted to give a big thanks to everyone who filled it out.

As of today, we have had 88 responses. While I’m sure the sample size and sample method were far from perfect, it did produce some numbers that we found interesting that we wanted to share.

Note that the following graphs don’t represent all of the data collected from our survey. This is due to the fact that I made the questionable choice of making all the answers text fields. While this allowed us to see a lot of interesting and unexpected responses that a simple set of checkboxes would not have yielded, it also meant that processing the data was a pretty labor-intensive task. If you are curious about the answers from other questions, email me and I’ll crunch the data and post a graph.

Ultimately, these answers only led to more questions. If you’d like to help us out, we have another (much shorter!) tools survey you can fill out. Thanks!

Note: for the next two questions, I have excluded projects that have no unit tests

This last table is a bit strange, but I still think it’s interesting. You need to look at the relative number of 1-person, 2-person, etc, teams above to really understand it in context. The table shows code coverage by team size. So, for instance, the top left cell says that “37% of 1-person teams have code coverage equal or greater than 10%” while the top right cell says “4% of 1-person teams have code coverage equal to or greater than 100%”. Hopefully that makes some sense.

code coverage %
10% 20% 30% 40% 50% 60% 70% 80% 90% 100%
team size 1 37% 31% 27% 27% 27% 27% 18% 18% 4% 4%
2 52% 47% 47% 47% 47% 43% 33% 19% 14% 0%
3 66% 66% 66% 66% 66% 58% 50% 41% 8% 8%
4 50% 37% 37% 37% 37% 37% 25% 25% 12% 12%
5 60% 60% 50% 40% 40% 40% 40% 40% 10% 0%

Written by Ben

June 30, 2008 at 7:57 pm

Posted in Devver

6 Responses

Subscribe to comments with RSS.

  1. […] Update: We have posted the results […]

  2. Great post, I will love to see this article but for Django!

    mauricio quiros

    July 1, 2008 at 11:38 am

  3. […] According to our survey, most Ruby developers run their unit tests using a command line tool called Rake, which (and this is key) prints out a dot every time a test is completed. Here is Rake running a very small test suite for Flexmock […]

  4. Thanks for the post


    August 2, 2008 at 5:17 pm

  5. […] to fill it out. We ended up with some interesting information about the Ruby development scene.…opment-survey/ Thanks again, Dan Dan Mayer wrote: > We are working on some online Ruby development tools, and […]

  6. […] Shared The results of our Ruby development survey – The Devver Blog […]

Comments are closed.

%d bloggers like this: