A developer must discuss changes with the user before making them. This applies to changes affecting cost, speed, data, or reputation. This rule has no exceptions.
By Pawan Nayar · from the LLOS AI Learning record
A developer must discuss changes with the user before making them.
This applies to changes affecting cost, speed, data, or reputation. This rule has no exceptions.
A developer must always discuss changes that affect cost, speed, data integrity, or reputation. This discussion happens before the changes are put into action. This rule is universal and applies to all projects. Examples of such changes include adding tokens to prompts or changing how data is stored. It also includes switching AI models or adding network calls. A quick discussion can prevent big problems. Asking 'Does this change affect cost, speed, or data?' takes only a few seconds. Fixing a bad decision can take many hours. If a developer is unsure, the developer should assume the change will have an effect and ask.
A developer adds a new feature to an AI model. This feature makes the model use more computing power. The developer does not discuss this with the manager. The manager later sees a large increase in project costs. This could have been avoided with a short discussion.
Resolved from this lesson's own record — real definitions, not invented for this page.
More from the same record, pulled by shared topic — not written new for this page.
A developer must discuss changes if they affect money spent, how fast something works, the correctness of information, or how people view the project. This includes adding words to AI prompts or changing how data is stored.
An AI model can use a special database to keep all its generated text. This database should allow fast searching.
A developer must learn and apply specific design rules. These rules guide the AI model's behavior.
A developer should list each major component of the AI system. For each component, the developer must describe its purpose.
A developer must discuss changes with the user before making them. This applies to changes affecting cost, speed, data, or reputation. This rule has no exceptions.