Functions: Giving Work a Clear Responsibility

As your store grows, the same reservation logic may be needed in several places. A function gives that behavior a name and a clear boundary.

• Define a Contract
  A useful function makes its expected inputs, result, and effects understandable. A reservation function might receive a quantity, report whether it succeeded, and update stock only on success.
• Separate Calculations from Side Effects
  Calculating how much stock would remain is different from updating the actual stock. Keeping that distinction clear makes behavior easier to reason about.
• Make Important Effects Visible
  A function that changes inventory should communicate that responsibility through its name and interface. Callers should understand what can change when they use it.

Invariants: Protecting What Must Stay True

Your store has a basic rule: available stock must never become negative. That rule is an invariant—a condition that valid state must satisfy.

• Begin with Valid State
  The reservation logic assumes the starting stock is zero or greater.
• Preserve the Rule During Every Update
  Accepting only positive quantities within the available stock keeps the resulting stock non-negative.
• Leave State Unchanged When a Request Fails
  An unsuccessful reservation should not reduce inventory. Failure behavior deserves as much attention as success behavior.

Putting the Ideas into Practice with C#

You can explore all five concepts with a small reservation method:

static bool TryReserve(ref int stock, int quantity)
{
    if (quantity <= 0 || quantity > stock)
        return false;

    stock -= quantity;
    return true;
}

Here, ref allows the method to update the caller’s stock variable.

Start with stock equal to three and reset it before each experiment:

• Request zero items: the reservation fails, and stock remains three.
• Request four items: the reservation fails, and stock remains three.
• Request two items: the reservation succeeds, and stock becomes one.

Before running each case, predict the result. Then explain which condition was evaluated, which statements executed, and whether state changed.

Bringing It All Together

A small reservation method contains ideas that appear throughout software development. State describes the current situation. Types shape how information is represented. Control flow selects what happens next. Functions organize responsibilities. Invariants protect the rules your application depends on.

As this store grows into a backend service, new challenges will appear: saving inventory, handling failures, and processing simultaneous purchases. Those challenges become easier to understand when you can already trace one request clearly.

Start with a small program, predict its behavior, and explain every change. That habit builds understanding you can carry into larger systems.