Why functions are needed in Go - Visual Breakdown

Concept Flow - Why functions are needed

Start Program

↓

Write code repeatedly?

Yes→Code is long and messy

↓

Hard to fix bugs

↓

Use functions

↓

Code is organized

↓

Easy to reuse and fix

↓

Program ends

This flow shows how using functions helps avoid repeating code, making programs easier to read, fix, and reuse.

Execution Sample

Go

package main
import "fmt"
func greet() {
    fmt.Println("Hello, friend!")
}
func main() {
    greet()
    greet()
}

This Go program defines a function greet and calls it twice to print a greeting message.

Execution Table

Step	Action	Function Called	Output
1	Program starts	none
2	Call greet()	greet	Hello, friend!
3	Call greet() again	greet	Hello, friend!
4	Program ends	none

💡 Program ends after calling greet() twice

Variable Tracker

Variable	Start	After greet() call 1	After greet() call 2	Final
No variables	none	none	none	none

Key Moments - 2 Insights

Why do we call the function greet() twice instead of writing the print statement twice?

Calling greet() twice reuses the same code, keeping the program shorter and easier to fix if the message changes, as shown in steps 2 and 3 of the execution_table.

What happens if we want to change the greeting message?

We only change it once inside the greet() function, and both calls print the new message, avoiding repeated edits.

Visual Quiz - 3 Questions

Look at the execution_table, what is printed when greet() is called the first time?

A Hi there!

B Hello, friend!

C Hello, world!

D No output

💡 Hint

Check the Output column at Step 2 in the execution_table

At which step does the program end according to the execution_table?

A Step 4

B Step 3

C Step 2

D Step 1

💡 Hint

Look at the Action column for the program ending step

If we did not use functions and wrote the print statement twice, what would happen?

A The program would be shorter

B The program would not run

C The program would be longer and harder to fix

D The output would change

💡 Hint

Refer to the concept_flow where repeated code leads to messy and hard to fix programs

Concept Snapshot

Functions help avoid repeating code.
They organize code into reusable blocks.
Call a function whenever you need its task done.
Change code in one place, it updates everywhere.
Makes programs shorter, clearer, and easier to fix.

Full Transcript

This example shows why functions are needed in programming. Without functions, you might write the same code many times, making your program long and hard to fix. Here, a function named greet prints a message. The main function calls greet twice, so the message prints twice without repeating code. This makes the program organized and easy to update. If you want to change the message, you only change it inside greet, and both calls show the new message. The execution table shows each step: starting the program, calling greet twice, and ending the program. Variables are not used here, so no changes tracked. Key moments explain why calling the function twice is better than repeating code. The quiz checks understanding of output, program end, and benefits of functions. Overall, functions keep code clean, reusable, and easy to maintain.