In this Go lesson, we will study Control Flow through small executable cases. First we will make the normal result clear; then inspect data flow, ownership, failure behavior, and the caller contract before adding framework or infrastructure complexity.

Professional code is readable under change. A future developer should be able to identify which input is trusted, who may update state, where I/O happens, and how an expected error reaches a caller without reconstructing the whole application.

Five focused Go programs for Control Flow. Each has a visible result, an explicit contract, and a next change to test so the lesson becomes reusable knowledge rather than passive reading.

Let’s isolate one Go Fundamentals rule together. Run it, trace the inputs and output, then change one boundary value before reusing the pattern. Small observable programs turn syntax into a reliable engineering habit.

Keep contracts explicit: validate data before use, make ownership and mutation visible, and return a named result or failure a caller can test. Static types and a successful build help, but runtime boundaries still need intentional checks.

Go

package main
import "fmt"
func square(value int) int { return value * value }
func main() { fmt.Println(square(7)) }

49

Try next: make the nearest empty, invalid, missing, or boundary case observable instead of leaving behavior to an unchecked assumption.

Let’s isolate one Go Fundamentals rule together. Run it, trace the inputs and output, then change one boundary value before reusing the pattern. Small observable programs turn syntax into a reliable engineering habit.

Keep contracts explicit: validate data before use, make ownership and mutation visible, and return a named result or failure a caller can test. Static types and a successful build help, but runtime boundaries still need intentional checks.

Go

package main
import "fmt"
type Topic struct { ID string; Title string }
func main() { topic := Topic{ID: "g-1", Title: "Go"}; fmt.Println(topic.Title) }

Go

Try next: make the nearest empty, invalid, missing, or boundary case observable instead of leaving behavior to an unchecked assumption.

Let’s isolate one Go Fundamentals rule together. Run it, trace the inputs and output, then change one boundary value before reusing the pattern. Small observable programs turn syntax into a reliable engineering habit.

Keep contracts explicit: validate data before use, make ownership and mutation visible, and return a named result or failure a caller can test. Static types and a successful build help, but runtime boundaries still need intentional checks.

Go

package main
import ("errors"; "fmt")
func port(value int) (int, error) { if value < 1 { return 0, errors.New("invalid port") }; return value, nil }
func main() { value, err := port(443); fmt.Println(value, err) }

443 <nil>

Try next: make the nearest empty, invalid, missing, or boundary case observable instead of leaving behavior to an unchecked assumption.

Let’s isolate one Go Fundamentals rule together. Run it, trace the inputs and output, then change one boundary value before reusing the pattern. Small observable programs turn syntax into a reliable engineering habit.

Keep contracts explicit: validate data before use, make ownership and mutation visible, and return a named result or failure a caller can test. Static types and a successful build help, but runtime boundaries still need intentional checks.

Go

package main
import "fmt"
func main() { done := make(chan string, 1); go func() { done <- "ready" }(); fmt.Println(<-done) }

ready

Try next: make the nearest empty, invalid, missing, or boundary case observable instead of leaving behavior to an unchecked assumption.

Let’s isolate one Go Fundamentals rule together. Run it, trace the inputs and output, then change one boundary value before reusing the pattern. Small observable programs turn syntax into a reliable engineering habit.

Keep contracts explicit: validate data before use, make ownership and mutation visible, and return a named result or failure a caller can test. Static types and a successful build help, but runtime boundaries still need intentional checks.

Go

package sample
import "testing"
func TestSquare(t *testing.T) { if square(3) != 9 { t.Fatal("expected 9") } }
func square(value int) int { return value * value }

go test reports PASS

Try next: make the nearest empty, invalid, missing, or boundary case observable instead of leaving behavior to an unchecked assumption.

Start by naming the value the next line depends on. This keeps the lesson input explicit before we apply a transformation or call an external boundary. We are applying that habit while revisiting Go Fundamentals: Control Flow.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Go

package main

import (
    "fmt"
    "strings"
)

func main() {
    lesson := "Go Fundamentals Control Flow"
    fmt.Println(strings.ToUpper(lesson))
}

GO FUNDAMENTALS CONTROL FLOW

Try next: Replace the sample value with one from your own notes, predict the result, and then run it.

A small guard makes the allowed and rejected path visible. We want a caller to receive an intentional result instead of discovering an unexplained failure later. We are applying that habit while revisiting Go Fundamentals: Control Flow.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Go

package main

import (
    "fmt"
    "strings"
)

func main() {
    lesson := "Go Fundamentals Control Flow"
    fmt.Println(strings.ToUpper(lesson))
}

GO FUNDAMENTALS CONTROL FLOW

Try next: Try an empty value as well as the normal value and describe why the two outcomes differ.

This step returns a value instead of mixing the rule with display or storage work. That separation gives us a small unit we can run, test, and reuse. We are applying that habit while revisiting Go Fundamentals: Control Flow.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Go

package main

import (
    "fmt"
    "strings"
)

func main() {
    lesson := "Go Fundamentals Control Flow"
    fmt.Println(strings.ToUpper(lesson))
}

GO FUNDAMENTALS CONTROL FLOW

Try next: Call the same rule twice with different inputs and confirm that each result depends only on its input.

Use a named branch where the business rule changes. A future reader should be able to point at the condition and state the result for both sides. We are applying that habit while revisiting Go Fundamentals: Control Flow.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Go

package main

import (
    "fmt"
    "strings"
)

func main() {
    lesson := "Go Fundamentals Control Flow"
    fmt.Println(strings.ToUpper(lesson))
}

GO FUNDAMENTALS CONTROL FLOW

Try next: Change the boundary value by one and explain exactly which branch becomes active.

Collections become safer when we can see which value is read, which value is derived, and whether the original collection remains owned by the caller. We are applying that habit while revisiting Go Fundamentals: Control Flow.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Go

package main

import (
    "fmt"
    "strings"
)

func main() {
    lesson := "Go Fundamentals Control Flow"
    fmt.Println(strings.ToUpper(lesson))
}

GO FUNDAMENTALS CONTROL FLOW

Try next: Add one more item and predict the derived result before executing the code.

A named outcome is easier to test than an implied side effect. We can now distinguish a successful path from a rejected path without guessing from console noise. We are applying that habit while revisiting Go Fundamentals: Control Flow.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Go

package main

import (
    "fmt"
    "strings"
)

func main() {
    lesson := "Go Fundamentals Control Flow"
    fmt.Println(strings.ToUpper(lesson))
}

GO FUNDAMENTALS CONTROL FLOW

Try next: Rename the outcome in your own words while preserving the same success and failure rule.

Work through one value at a time. The point is not to memorize syntax; it is to see how the accumulator or output changes after each repeatable step. We are applying that habit while revisiting Go Fundamentals: Control Flow.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Go

package main

import (
    "fmt"
    "strings"
)

func main() {
    lesson := "Go Fundamentals Control Flow"
    fmt.Println(strings.ToUpper(lesson))
}

GO FUNDAMENTALS CONTROL FLOW

Try next: Use a shorter collection first, then add one value and trace the extra iteration aloud.

The core rule prepares a value, while the outer line decides how to show it. That keeps the result usable by a UI, test, API, or command-line caller. We are applying that habit while revisiting Go Fundamentals: Control Flow.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Go

package main

import (
    "fmt"
    "strings"
)

func main() {
    lesson := "Go Fundamentals Control Flow"
    fmt.Println(strings.ToUpper(lesson))
}

GO FUNDAMENTALS CONTROL FLOW

Try next: Change only the display text and verify that the underlying rule and result stay unchanged.

A useful example includes the nearest boundary, not only the happy path. We are making the behavior inspectable before a real caller relies on it. We are applying that habit while revisiting Go Fundamentals: Control Flow.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Go

package main

import (
    "fmt"
    "strings"
)

func main() {
    lesson := "Go Fundamentals Control Flow"
    fmt.Println(strings.ToUpper(lesson))
}

GO FUNDAMENTALS CONTROL FLOW

Try next: Try the lowest supported value and then one value just outside the accepted range.

A compact assertion turns the lesson into a repeatable promise. It helps us catch a changed rule before a larger program hides the source of the mistake. We are applying that habit while revisiting Go Fundamentals: Control Flow.

Keep the example small enough to trace. First predict the normal result; then change one input and explain the boundary result in your own words.

Go

package main

import (
    "fmt"
    "strings"
)

func main() {
    lesson := "Go Fundamentals Control Flow"
    fmt.Println(strings.ToUpper(lesson))
}

GO FUNDAMENTALS CONTROL FLOW

Try next: Deliberately change the expected value once, observe the failed check, and then restore the correct contract.

Review Go Fundamentals: Control Flow as a full trace: input, validation, calculation or side effect, output, and cleanup. State the normal result, then state the boundary behavior. If either is hard to explain, split the work into a smaller function with a narrower contract.

Keep secret values and privileged decisions outside display code. Authentication establishes an identity; authorization decides what that identity may do. Check both close to protected operations, and use intentional failure responses rather than leaking internal details or crashing generically.

• Run the normal input and record the exact result.
• Test an empty, malformed, or boundary input deliberately.
• Keep state, ownership, and side effects visible to the caller.
• Return a result or named failure that can be tested.
• Never log credentials, tokens, or sensitive input.

This discipline makes Go code easier to review, safer to change, and more useful in production than a collection of untested syntax fragments.

• Skipping input validation because a local example happened to work.
• Hiding mutation, ownership, or failure behavior inside a convenient shortcut.
• Using a client-side display rule as the only protection for sensitive work.
• Copying code without changing an input to prove its contract.