Lesson 7: C# setup and .NET foundations: Performance perspective

Concept Explanation

This lesson introduces the idea that performance is not only about speed, but also about writing code that does not do extra work by accident. In C#, a beginner should learn to notice repeated allocations, unnecessary loops, and expensive operations placed in the wrong spot. You will work through a small example, measure what it does, then make one focused change and compare the result. The goal is to build the habit of asking simple questions: what runs often, what can be reused, and what should stay readable even after optimization.

Where to Put the Code

1. Define color and position variables at the top.
2. Create shape drawing or placement logic in the middle.
3. Render output (print, canvas, SVG, or styled block) at the end.

Command Reference

• Run the example once, then change the input list size and see how the elapsed time changes.
• Move any repeated work out of the loop if it does not need to happen on every iteration.
• Keep the method readable while you improve it; do not trade clarity for a tiny gain.
• Write down one sentence explaining why your change is faster or simpler.

Step-by-step Guide

1. Read the method and point out which part of the code runs for every item in the list.
2. Run the sample once and record the output before changing anything.
3. Make one small performance-minded improvement, such as removing repeated work or simplifying the loop body.
4. Run the updated version and compare the result with the original output.
5. Finish with a short note on whether the change improved speed, readability, or both.

Practice Exercises

• Create a second example that sums only the even values in a list and compare two implementations.
• Rewrite the sample using a different loop style and decide which version is easier to read.
• Add a larger input set and describe what changes when the method runs many more times.

Coding Challenges

• Implement two versions of the same calculation and explain which one you would keep in a real project.
• Design a case where a small inefficiency becomes noticeable because the code runs inside a repeated workflow.

Mini Practice Tasks

• Rename one variable so the intent of the calculation is obvious.
• Add one more input value and verify the total still makes sense.
• Write a one-line summary of what this example is measuring.