Music Tempo and Coding Performance

ISEF Category: Behavioral and Social Sciences

Subcategory: Cognitive Psychology  ·  Difficulty: Intermediate  ·  Setup: School Lab  ·  Time: 1 to 2 Months

The Hook

A fast beat can feel like a push, but it can also split your attention. That matters when you are fixing bugs or writing code from scratch, because those two jobs do not use your brain in the same way. You can test whether tempo helps one task and hurts the other by logging what students type, not just how they feel.

What Is It?

Ambient background music tempo means the speed of the music, usually measured in beats per minute. Think of tempo like the pace of a metronome in the room. A slow track can feel steady, while a fast one can feel like a tap on your shoulder that keeps returning. Your project asks whether that background pace changes coding performance.

Debugging and writing new code are different mental jobs. Debugging is like detective work, because you hunt for a small clue. Writing new code is closer to building from a sketch, because you turn an idea into working steps. If tempo changes speed, error counts, or pause patterns, you may see the effect most clearly when you compare those two tasks side by side.

Why This Is a Good Topic

You can change one thing, music tempo, and compare two task types with clear outcomes such as time to finish, error counts, backspaces, and pause patterns. The topic connects to focus, distraction, and how students work in noisy spaces. You can learn study design, measurement, and basic stats without needing a university lab.

Research Questions

• How does background music tempo affect time to finish a debugging task?
• What is the effect of background music tempo on the number of syntax and logic errors during new code writing?
• Does background music tempo change keystroke-level pause time more during debugging than during new code writing?
• To what extent does background music tempo affect code completion rate for students with similar programming experience?
• Which tempo range produces the fewest backspaces and undo actions during coding tasks?
• How does background music tempo affect self-reported focus after debugging versus after new code writing?

Basic Materials

• Laptop or desktop computer with the same code editor on every device.
• Over-ear headphones or earbuds with one fixed volume setting.
• Three instrumental playlists matched for volume but different in tempo.
• A timer or screen-recording app that can mark start and finish times.
• Keystroke-logging software or an editor that exports key presses, pauses, and backspaces.
• A set of matched debugging tasks and new-code prompts in one programming language.
• A spreadsheet or CSV template for recording task scores and participant details.

Advanced Materials

• Research computer running PsychoPy, E-Prime, or a custom logging script.
• Noise-controlled room or testing booth.
• Calibrated headphones and a sound level meter.
• Keystroke-dynamics export tools with timestamped logs.
• IRB-approved consent and assent forms.
• Statistical software such as R, Python, or JASP.
• Optional eye-tracking setup if your lab already has one.

Software & Tools

• Python: Cleans keystroke logs and calculates pause, backspace, and completion metrics.
• R: Runs the statistical tests and graphs tempo effects across task types.
• JASP: Lets you compare conditions with t-tests, ANOVA, and effect sizes.
• Google Sheets: Tracks participants, conditions, and raw scores before analysis.
• PsychoPy: Presents tasks and records responses if you build the study as a computer-based experiment.

Experiment Steps

1. Define the two coding tasks so debugging and new code writing are matched for language and rough difficulty.
2. Choose the tempo conditions and keep volume, playlist style, and device setup constant.
3. Build a measurement plan that includes completion time, errors, backspaces, and pause patterns.
4. Counterbalance task order and music order so practice effects do not masquerade as a tempo effect.
5. Decide how you will clean the logs, score each task, and compare the two task types before you collect data.

Common Pitfalls

• Letting song volume change between playlists, which turns loudness into a hidden variable.
• Comparing a harder debugging task with an easier writing task, which mixes task difficulty with music effects.
• Using too few participants, which makes one strong or weak coder swing the results too much.
• Measuring only completion time, which misses error patterns and pause behavior.
• Reusing the same task order for every student, which lets practice effects look like a tempo effect.

What Makes This Competitive

A stronger version of this project does more than ask whether music helps. It separates debugging from new code writing, measures speed and error behavior, and controls for coding skill, playlist familiarity, and task order. You can push it further by testing whether tempo changes pause patterns or error recovery, not just final completion time. Clear effect sizes and a careful counterbalanced design would make the project much stronger.

Project Variations

• Compare instrumental music with lyric-heavy music at the same tempo to see whether words in the music matter more than speed.
• Test whether Python debugging responds differently than JavaScript debugging, since syntax and editor habits can change the pattern of errors.
• Analyze whether students with more coding experience show smaller tempo effects than beginners.

Learn More

• PubMed: Search review articles on music tempo, attention, cognitive load, and programming performance.
• NCBI Bookshelf: Read free chapters on attention, memory, and experimental design in psychology.
• OpenStax Psychology 2e: Review free chapters on cognition, attention, and research methods.
• MIT OpenCourseWare: Find lecture notes on experimental design and statistics in psychology or computer science research.
• Frontiers in Psychology: Search open-access studies on background music, focus, and task performance.
• PLOS ONE: Search open-access papers on keystroke dynamics and cognitive performance.