PROFESSIONAL PRACTICE AND COLLABORATION

COMMUNICATING UNCERTAINTY Language models are probabilistic, which means they give a range of possible answers instead of exactly one. That makes honest communication harder than in many other kinds of engineering. Avoid saying "the agent is accurate" without a number and a description of what was tested. Prefer statements such as "the agent passed forty-six of fifty test cases, and the four failures all involved scanned documents." When you are asked to promise perfect behavior, explain that the right goal is a known, acceptable rate of failure together with safe handling of the failures that remain. This habit builds trust, because people learn that your numbers mean something. BEING ON CALL Production systems sometimes break outside office hours, so many teams keep an on-call rota, a schedule in which engineers take turns being reachable to respond to urgent problems. Being on call is easier when the system is well prepared. A clear alert tells you what is wrong, how serious it is, and which runbook to open first. A rollback button, meaning a way to return to the previous working version, lets you stop the damage before you understand the cause. After the incident, write the postmortem while memories are fresh, and turn each lesson into a test, an alert, or a limit. Share the on-call load fairly, and speak up if the load becomes unsustainable, because tired engineers make more mistakes.