When a script beats an agent, the N+1 query problem and database transactions

Agents. Not everything needs to be an agent. Sometimes a good script with a solid SDK is just the smarter move.

Commit messages. Good standard to follow for commit messages across an org: conventionalcommits.org.

N+1 queries. Classic N+1 query problem: it happens when your code executes one initial database query to fetch a list of N items, and then runs N additional queries inside a loop to fetch related data for each individual item.
Transactions. By default, most databases operate in auto-commit mode. For example, as soon as an INSERT is run, it is saved permanently in milliseconds. Adding START TRANSACTION (hold, don’t save anything permanently now), COMMIT (everything worked, save it now) and ROLLBACK (there is an issue, undo everything we did) should be implemented as best practice.
Archify. Archify is a good skill for converting codebases to interactive HTML views for better visual understanding.