A developer must discuss any change that affects cost, speed, data integrity, or reputation with the user before making the change. This rule has no exceptions. It applies to all projects and situations.
By Pawan Nayar · from the LLOS AI Learning record
A developer must discuss any change that affects cost, speed, data integrity, or reputation with the user before making the change.
This rule has no exceptions. It applies to all projects and situations.
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. It also includes changing how an AI model works or adding new network connections. Asking first takes little time. Fixing a bad change takes much more time. If a developer is not sure if a change will have an effect, the developer should ask the user.
A developer adds five previous AI outputs to each new prompt without asking the manager. This makes the AI model much slower. It also increases the cost of using the AI model a lot. The manager then has to spend hours fixing this problem.
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 always discuss changes that affect cost, speed, data integrity, or reputation. This discussion happens before the changes are put into action.
A developer should add comments to code changes. These comments explain the reason for the change.
A developer should include a version number and date. The developer must define the scope of the work.
A complete design specification provides all necessary details. It lists changes to the user interface.
A developer must discuss any change that affects cost, speed, data integrity, or reputation with the user before making the change. This rule has no exceptions. It applies to all projects and situations.