Lesson 8: Java setup and execution model: Security and reliability

Concept Explanation

This lesson focuses on making small Java programs safer and more predictable. Instead of assuming input is always valid, you will practice checking risky cases, responding to failures clearly, and keeping the code easy to follow. The goal is to see how reliability starts with small choices: validating data, handling exceptions on purpose, and writing code that another developer can trust without guessing what happens when something goes wrong.

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 program once with a valid age and once with invalid text to confirm both outcomes are handled cleanly.
• Create a tiny input list such as "18", "0", "-4", and "abc" and note which values should pass or fail.
• Refactor the parsing logic into a dedicated method so the validation rules live in one place.
• Write down one reliability rule you followed, such as failing fast or returning a clear error message.

Step-by-step Guide

1. Start with the baseline version and identify where invalid input can break the program.
2. Move the risky parsing work into a small helper method with a clear name.
3. Test one normal input and one failure case, then check that the output explains what happened.
4. Make one focused improvement, such as rejecting negative numbers or improving the error message.
5. Finish by noting why this version is safer than a direct parse in main.

Practice Exercises

• Change the example so it validates a quantity or price instead of an age.
• Add one more rule, such as a maximum allowed value, and explain why it matters.
• Write a short test plan showing at least three inputs and the expected result for each.

Coding Challenges

• Implement one version that throws exceptions and another that returns a success/failure result, then compare them.
• Design a small input-validation utility that could be reused by more than one class.

Mini Practice Tasks

• Add a guard that rejects blank input before parsing starts.
• Rename any vague variables so their purpose is obvious at a glance.
• Improve one message so a beginner user can understand the failure without reading the code.