Make Code Easier to Change with Guard Clauses

When a function has several nested conditions, flip the checks into guard clauses. Instead of wrapping the useful work in multiple if blocks, return or throw as soon as invalid input is found. This keeps the main logic near the left margin and makes the expected path easier to follow.

Also, name each function for the action it performs and keep it focused on one job. If you need a comment explaining what a block does, consider renaming the code or extracting a small helper. The goal is not the shortest function—it is code whose intent remains obvious six months later.