◆ AI Learning · Hard rule

How should a developer document code changes, file ownership, and feedback for a project?

Every code change needs a comment. Every file needs a copyright notice. Every chapter needs a feedback log.

By Pawan Nayar · from the LLOS AI Learning record

The rule

Every code change needs a comment.

Every file needs a copyright notice. Every chapter needs a feedback log.

A developer must add a comment for every code change. The comment explains what changed, why, and what might break if removed. If feedback caused the change, the comment should name the person who gave the feedback. Every file that ships in a chapter must have a copyright header. This header states the product, chapter, and copyright owner. It protects the original work. Each chapter needs a `FEEDBACK_LOG.md` file. This file records all feedback, the actions taken, and the status. It helps track decisions and prevents repeating past discussions.

A developer makes a change to a chapter's code. The developer adds a comment: `// [2026-04-26] Manager: 'Simplify the loading message' -> removed extra details.` The developer also ensures the file has the correct copyright header. Later, the manager gives new feedback. The developer adds this feedback to the `FEEDBACK_LOG.md` file for that chapter. This process ensures all changes and decisions are clear and traceable.

Words you'll need

Resolved from this lesson's own record — real definitions, not invented for this page.

Software Engineering

The practice of building software systems methodically and reliably

Configuration Management

Keeping track of what settings AI is using

Change Management

Helping people work with new AI tools and processes

Knowledge Management

Organizing what you know so you can find it again

Questions people ask

More from the same record, pulled by shared topic — not written new for this page.

How should a team record feedback and decisions for an AI project?

Record feedback in a log. Each entry needs a date.

How do I keep a record of all feedback received and the changes made?

Create an append-only log file. Each entry needs a date, a summary, the feedback itself, and the action taken.

How can a developer make sure a file edit is safe and correct?

Before editing, the developer must confirm the exact start and end points for the changes. The developer must only change text within these points.

When should a developer add comments to code?

A developer must add a comment for every code change. The comment must include the date of the change.