CLI Design · interview question
Which move is the best default when runnable project shape becomes part of this workflow?
Multiple choiceHardchapter-6-curatedpremiumcli-designrunnable-project-shape
Answer and explanation
Correct answer
B. Keep install, invocation, and output paths consistent so the project is easy to teach, document, and automate.
Why
Keep install, invocation, and output paths consistent so the project is easy to teach, document, and automate. That is the stronger engineering move because mature tooling choices are part of interview prep because they show you think beyond local code snippets. If usage only makes sense to the original author, the project shape is still immature.
Test yourself on CLI Design
A free test with instant, explained results. No account needed.
More CLI Design questions
- Which response shows the healthiest evidence-first mindset around runnable project shape?
- Another engineer will maintain this code later. What choice helps the most around environment configuration?
- A teammate submits shaky runnable project shape code. Which review comment is the strongest?
- A senior interviewer asks for one tradeoff behind argparse and commands. What is the strongest follow-up?
- Another engineer will maintain this code later. What choice helps the most around runnable project shape?
- What assumption should be made explicit when working with runnable project shape?