A developer must check specific points before, during, and after editing a file. These checks prevent errors and ensure the file works correctly. The developer must stop editing if checks fail repeatedly.
By Pawan Nayar · from the LLOS AI Learning record
A developer must check specific points before, during, and after editing a file.
These checks prevent errors and ensure the file works correctly. The developer must stop editing if checks fail repeatedly.
Before editing, the developer must confirm the exact start and end points for the changes. The developer must only change text within these points. The developer must not change other parts of the file. After editing, the developer must check if the number of items in a section is correct. For example, a glossary might need 25 terms. The developer must also check the file's code for errors. For HTML files, the developer must ensure the page loads without problems. The developer must check for specific page elements, like a footer or an open FAQ item. The developer must also ensure no broken emojis or sentences start with pronouns. If checks fail twice, the developer must stop and ask for help.
A developer needs to update a list of 10 frequently asked questions (FAQs) on a webpage. Before editing, the developer confirms the exact start and end tags for the FAQ section. The developer adds two new questions, making sure the total is now 12. After editing, the developer checks that the page loads correctly and that the second FAQ item still opens by default. If the page shows an error, the developer stops and fixes it before doing anything else.
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 a script, a developer must check several items. These checks depend on the type of script.
Before a developer makes the first edit in any work session, a backup copy of the file must be made. The backup file name should include the date.
A developer must add a comment for every code change. The comment explains what changed, why, and what might break if removed.
An AI model must state the full path every time it creates or changes a file. The AI model must list all full paths at the end of a conversation.
A developer must check specific points before, during, and after editing a file. These checks prevent errors and ensure the file works correctly. The developer must stop editing if checks fail repeatedly.