What are the pitfalls of command substitution?
Interviewer Expectations for this Question
01
Core Competency
Assesses fundamental understanding of Shell & Bash conventions, runtime behavior, and memory/performance considerations.
02
Evaluation Criteria
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Comprehensive Model Answer
Verified Solution
Command substitution captures the stdout of a command as a string. Use $(cmd) rather than backticks, which are deprecated and harder to nest.
today=$(date +%F)
count=$(wc -l < file)
files=$(find . -name '*.log')
Pitfalls to watch for:
- Unquoted substitution undergoes word splitting and globbing, so
rm $(cat list)breaks on filenames with spaces. Quoting helps only for a single value; for many values use a loop or an array. - Trailing newlines are stripped from the captured output.
- The exit status of the command is not captured in the assignment, so if you need it, run the command first and capture
$?immediately. - Command output used as a path or option must be validated, because it can be empty or contain unexpected characters.
while IFS= read -r line; do echo "$line"; done < list
mapfile -t lines < list # bash 4+, preserves lines
Prefer mapfile, NUL-delimited tools and explicit validation.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.