SYSE.36:8 - Common Anti-Patterns and How to Avoid Them

Misuse	Repair
Use backend jobs as all user attempts.	Observe or bound failures at the user entry and explain remaining coverage.
Treat HTTP 200 as application correctness.	Observe the task’s actual accepted result or state the missing semantic check.
Set a percentage with no agreed consequence.	Agree the objective and response policy with the service’s users and providers, including the people authorized to make the relevant trade-offs.
Merge platform and application budgets.	Bind each measurement and policy to its own service and users.