# Third Language Project

Part of the Programming Merit Badge Digital Resource Guide: [Introduction & Overview](https://merit-badge.university/merit-badges/programming/guide/index.md)

*5. Building Programs*

> **5c.** In the third language and environment, write or modify a program, debug and demonstrate, and explain as above.

By the time you reach this third project, you are no longer just trying to prove that you can get a program to run. You are showing that the big ideas of programming transfer across tools. Input, decisions, computations, output, and debugging are still the core — even when the language or environment changes.

## Stretch a little farther

A good third project often adds a new twist. Maybe your first project was text-based and your second was web-based. Your third could involve block coding, a simple game engine, physical computing, or a different style of interface. The point is not to make the most difficult project possible. The point is to show range.

Good third-project directions might include:

- a small game with score tracking and win/lose logic
- a sensor or button program in a physical-computing environment
- a web page that reacts to user input
- a useful tool that sorts, counts, or transforms data

[Codedex / Start Your Coding Adventure (website)](https://www.codedex.io/): Codedex offers interactive practice that can help you explore another language and build the confidence to complete a third project.

## Show what transfers between languages

This is a great place to notice that languages may look different, but the thinking often stays the same.

- variables still store information
- conditionals still guide decisions
- loops still repeat tasks
- debugging still depends on careful testing

If your counselor asks what you learned from using three languages, a strong answer might be: **the syntax changed, but the problem-solving process stayed familiar**.

> **Be Prepared! You want to choose a flashy project that is too big**
>
> Choose a version you can actually finish.
>
> - **Cut the feature list**: Keep only the parts that prove input, logic, and output.
> - **Build one success path first**: Make the simplest version work.
> - **Add one improvement at a time**: Extra features only help if they do not break the whole demo.
> - **Leave time to explain it**: A smaller project you understand beats a larger one you cannot describe.

**What to compare across all three projects** — Use this when you discuss the full set with your counselor

- [ ] Which language felt most readable?
- [ ] Which development environment made debugging easiest?
- [ ] Which project gave the clearest output?
- [ ] Which language would you choose for another similar task?
- [ ] What programming ideas stayed the same across all three?

> **Tip**
>
> If you are not sure what to say during your final demonstration, compare one exact feature across the three projects — such as input handling, if/else logic, or output formatting. That makes your explanation concrete.

![A Scout reviewing three finished programming projects with notes comparing language, environment, debugging, and output](https://ik.imagekit.io/doulacoop/tr:w-800/mbu-assets/merit-badges/programming/guide/three-project-summary-board?v=4ad8c532)

After three projects, you have done something real: you have written code in multiple contexts and learned how to talk about it clearly. The next requirement asks what you might do with that knowledge beyond the badge.

---

- Previous: [Second Language Project](https://merit-badge.university/merit-badges/programming/guide/req5b/index.md)
- Next: [Careers or Coding for Life](https://merit-badge.university/merit-badges/programming/guide/req6/index.md)