A developer can make a mistake one time. A developer must not repeat a known mistake. Repeating a known mistake shows negligence.
By Pawan Nayar · from the LLOS AI Learning record
A developer can make a mistake one time.
A developer must not repeat a known mistake. Repeating a known mistake shows negligence.
Making a mistake for the first time is part of learning. This is acceptable. Repeating a mistake that is already known to be bad is not acceptable. This shows a lack of care or attention. A developer must check past information before acting. This helps to avoid repeating errors. The goal is to learn from mistakes, not to make them again.
A developer writes code that causes an error. The error is new. The developer learns from this error and fixes the code. This is acceptable. Later, the developer writes new code. The new code uses the same bad pattern that caused the first error. The developer knew this pattern was bad. This is not acceptable. The developer repeated a known mistake.
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.
Before writing any external API code, a developer must read specific policy files. These files include rules for starting a session, handling retries, and using the central API coordinator.
When a developer's code fails, the developer must stop typing. The developer should take a short break, perhaps 30 seconds.
The Batch API is best for tasks with more than 50,000 calls. The cost savings must be worth a 24 to 48-hour wait time.
When a developer's code calls an external API, it should try only one time. The developer must not use loops to retry the call.
A developer can make a mistake one time. A developer must not repeat a known mistake. Repeating a known mistake shows negligence.