Naming scripts for people who inherit them

A script called fix2_final_v3.py tells an operations supervisor nothing. A script called monday_inventory_confirm.py at least points to the calendar ritual.

Prefer boring clarity

• Include the business event in the name
• Avoid initials only your project chat understands
• Match log file names to the script name

Comment the why

Comments should explain vendor quirks and shift constraints, not restate for loops. The reader at 2 a.m. is an operations person with limited patience for jargon.

This is small craft, but it is how Python automation consulting leaves something durable instead of a private dialect.