LOAD_FILE()()
Don’t start LOAD_FILE()() (str) with jargon. Start with a LOAD_FILE str dry-run. That is the whole point.
For LOAD_FILE()() (str), an index is in play. Don’t blame it until you have traced a LOAD_FILE str dry-run.
LOAD_FILE()() (str) exists so Kabir can keep a LOAD_FILE str dry-run correct in a first job task.
LOAD_FILE()() (str) shows up in a first job task. Name a LOAD_FILE str dry-run, not “a real-world scenario”.
Don’t do this with LOAD_FILE()() (str): skipping the failure case for LOAD_FILE str. Interviewers spot it in ten seconds.
LOAD_FILE()() (str) is not a lonely heading. Kabir ties it to a LOAD_FILE str dry-run.
Viva for LOAD_FILE()() (str): what it is → one LOAD_FILE str step Kabir can write from memory → the mistake (skipping the failure case for LOAD_FILE str).
Say LOAD_FILE()() (str) in one breath, then one LOAD_FILE str step Kabir can write from memory, then skipping the failure case for LOAD_FILE str.