Developer Sounds

In our tool, each developer in a software project is represented by a different sound.

Sarah is represented by a harp:

Devin is represented by a choir:

Andrew is represented by a trombone:

Representing Commits

These sounds are combined into songs that represent programming projects' version control histories. When the sounds are combined, each measure of music represents a single version control commit.

For example, listen to this song:

As you listen to it, you will hear three measures of music:

1. The first measure of music is Sarah's harp, so Sarah made the first commit in the project.
2. Devin's choir represents the second commit.
3. Andrew's trombone represents the third commit.

Here is another example:

1. Devin's choir plays twice, indicating that she made the first two commits.
2. Then, Andrew's trombone plays twice, so he made the next two commits.

Day Separators

Multiple commits can be made in a single day. Day separators indicate when one day ends and another begins.

A day separator sounds like this:

For example:

• Andrew makes two commits.
• The day separator indicates that the day is over.
• Next, Andrew makes a third commit on the next day.

Conflicts

Conflict drums indicate when version control conflicts are introduced and resolved. For example:

• Andrew and Sarah make commits.
• Devin makes a third commit that introduces a conflict, as indicated by the drums.
• Devin and Sarah make the next two commits. Neither resolves the conflict.
• Devin makes one more commit. The conflict drums stop on this commit, indicating that the conflict was resolved.

Note that when the drums start playing, the commit that resolved the conflict is the one after the drums stop.

In some cases, a new conflict will be introduced before an old one is resolved. In this case, the conflict drums will become louder. For example:

• Andrew and Devin make commits.
• Devin makes a second commit that introduces a conflict.
• Sarah makes a commit.
• Andrew makes another commit. This one introduces a second conflict, so the conflict drums become louder.
• Andrew makes two more commits.
• Sarah makes a commit that resolves a conflict. There is one unresolved conflict left, so the conflict drums become quieter.
• Devin makes two more commits. The second one resolves the remaining conflict.

Which developer made the first commit in this sonification?

• Sarah
• Devin
• Andrew

How many conflicts are there in this sonification?

• 1
• 2
• 3 or more
• There are no conflicts in the sonification.

If there is at least one conflict in the sonification, who introduced the first conflict?

• Sarah
• Devin
• Andrew
• There are no conflicts in the sonification.

If there is at least one conflict in the sonification, who resolved the final conflict?

• Sarah
• Devin
• Andrew
• There are no conflicts in the sonification.

How many days altogether are portrayed in this sonification, counting the first and last days?

• 1
• 2
• 3 or more

You have answered questions correctly.

Since you understand how the Git Sonifier works, we will now ask you to complete some tasks using the sonifications. Click here to begin.

Please answer all of the questions correctly before continuing. If you need to, you can revisit the material above as much as you need to.

Finish