Day 26: Demo Day — Show It Off

Hi Anish! 🎉 Day 26. You made it.

Take a moment. Look at what’s in front of you on the breadboard. A few weeks ago, you didn’t know what a pin was, what a variable was, what an LED polarity meant. Today you’ve built a gadget of your own design, with sensors and outputs and its own user interface, and it works.

You are an Arduino kid. Officially.

Today is Demo Day. We’re not going to learn anything new. Instead, we’re going to:

1. Prepare a short demo script
2. Show the project to your family
3. Celebrate
4. Think about what comes next

Step 1: Prepare your demo script

#

You don’t need a big presentation. Just a short, clear script — about 2-3 minutes total. Here’s a template:

Part A: Introduce (30 seconds)

#

“Hi! This is my final project for the 26-day Learn Coding with Arduino series. It’s called [your project name], and it [one-sentence description of what it does]. I built it over the last 4 days, after learning 22 days of coding and electronics basics.”

Part B: Show it working (1 minute)

#

Demonstrate one feature at a time. For each feature:

1. Say what you’re about to do: “Watch what happens when I cover the light sensor…”
2. Do the action.
3. Point at the result: "…the LCD now says ‘Dark’ and the LED turns on automatically."

Don’t rush. Let people see. Audiences love to see things happen.

Part C: Explain one cool thing (30 seconds)

#

Pick ONE interesting detail and explain it in simple words. Not the whole code — just one thing that you’re proud of or that was tricky.

“The trickiest part was making the buzzer only beep during the day but not at night. I did it by also reading a second sensor called an LDR, and adding an if statement so the buzzer code only runs when it’s bright enough.”

Part D: Wrap up (30 seconds)

#

“In total, I learned 26 concepts over 26 days — from blinking an LED on Day 1 to building this gadget today. The hardest day was [day] because [why]. The most fun was [day] because [why]. Thanks for watching!”

Step 2: Make a poster (optional but fun)

#

If you have 10 minutes to spare, grab a piece of paper and draw:

• The name of your project (big, at the top)
• A simple drawing or photo of your project
• What it does (1 sentence)
• What parts it uses (quick list)
• “My favorite part was…” (fill in the blank)

Tape it next to the project when you demo. It looks professional and helps people remember what they saw.

Step 3: Invite your audience

#

Grab whoever is around — mom, dad, siblings, grandparents, even the dog. A good demo has at least one person watching. Set up a spot on the dining table or your desk. Make sure the LCD is visible and the project has power.

Do a dry run first — just you, running through the demo once to make sure nothing is broken. Then call the audience in.

Step 4: Do the demo

#

Breathe. Smile. Speak slowly. People love watching kids present cool things they’ve built — nobody is judging you. Go.

A few demo tips

#

• Don’t apologize if something doesn’t work the first time. Just say “let me try that again” and go.
• Pause after each feature — give people a second to appreciate it.
• Invite questions at the end. You don’t have to know every answer — “I don’t know yet, maybe I’ll figure it out next” is a perfectly good answer.
• Enjoy it. This is your moment.

Step 5: Celebrate

#

You did something real. Celebrate the right way:

• Get a snack (you earned it)
• Take a photo of your finished project for your own memory
• Write 3 sentences in your notebook:
  1. “What I built was…”
  2. “What was the hardest part…”
  3. “What I’m proud of…”

Keep that notebook. One day you’ll want to show it to someone.

What you learned over 26 days

#

Look back at this journey. In 26 days, you learned:

Programming basics:

• Variables (int, bool, String, arrays)
• setup() and loop()
• if / else / else if
• for loops and while loops
• Custom functions
• == vs =, &&, ||, !
• const for fixed values
• Comments, semicolons, curly braces

Electronics basics:

• Circuits, voltage, current, GND vs power
• LEDs and resistors — polarity, current-limiting
• Breadboards and how columns/rails are wired
• Buttons, pull-down and pull-up resistors
• Potentiometers (analog knobs)
• Light sensors (LDRs and voltage dividers)
• Buzzers (passive and active)
• Servo motors
• DC motors + transistors + flyback diodes
• LCD screens via I2C
• IR remotes and wireless input
• Sound sensors

Embedded/Arduino-specific:

• pinMode, digitalRead, digitalWrite
• analogRead, analogWrite, PWM
• tone / noTone
• delay vs millis() (blocking vs non-blocking)
• Serial.begin, Serial.print, Serial.println
• Libraries and #include
• map() for rescaling
• State change detection
• Debouncing
• Integration patterns (tiny loop(), helper functions, single source of truth)

Engineering habits:

• Plan before building
• Break big problems into small modules
• Test each module alone before integrating
• Use the Serial Monitor to debug
• Measure real values, then pick thresholds
• Put tweakable settings at the top of the file
• Name things clearly (variables, functions, constants)
• Write Serial.println to see what your code is doing

That’s a real engineer’s toolbox. You have it.

What’s next?

#

Today is the end of this series — but it’s really just the beginning of what you can build. Here are some things you could try on your own:

Take an existing project further

#

• Add Bluetooth to your final project. A cheap HC-05 module lets you control Arduino from your phone.
• Add a web dashboard using a WiFi module (ESP8266 or ESP32). Your project goes on the Internet.
• Use a bigger screen like a 320×240 color TFT. Draw graphs of sensor data over time.
• Add a motion sensor (PIR). Only activate the project when someone walks in.

Try a new board

#

• The ESP32 is a more powerful board that has WiFi and Bluetooth built in. Everything you learned here still works.
• A Raspberry Pi Pico is another great next step — runs micro-python, which is easier than C for some people.

Build something that solves a real problem

#

• A water-level sensor for your parents’ water tank that alerts when it’s low
• A garden watering timer that turns on a pump every day at 6am for 5 minutes
• A pet feeder with a servo that opens a door at feeding time
• A medicine reminder with a buzzer and LCD

Projects are more fun when they solve a real thing you care about.

Keep a project journal

#

Every project you build, write a few pages:

• What were you trying to build?
• What parts did you use?
• What went wrong and how did you fix it?
• What would you do differently?

In a year, you’ll have a whole notebook full of things you made, and you’ll be amazed at how much you’ve grown.

A note from me

#

Anish, I am proud of you. Building things is hard. Sticking with it for 26 days is harder. What you’ve done in the last month is the same arc that professional engineers go through — from confused beginner to confident maker. You now know more about electronics and programming than most adults do.

Don’t let this be where you stop. Build something else. Break things. Get frustrated. Google answers. Fail, try again, succeed. Every time you do, you get a little better. That’s the secret. That’s the whole thing.

I can’t wait to see what you make next.

❤️ Dad

What you learned today

#

• How to give a clear, short demo of your project
• How to prepare a simple poster to explain your work
• Why celebrating finished things matters
• A huge list of ideas for what to build next

The end — or really, the beginning

#

Go make the next thing, Anish. The Arduino is waiting.

🎓🤖✨