Data Cleanup · interview question
What is the healthiest performance judgment around normalization pipelines?
Multiple choiceMediumchapter-4-curatedpremiumdata-cleanupnormalization-pipelines
def normalize_row(row: dict[str, str]) -> dict[str, object]:
return {
"sku": row["sku"].strip(),
"quantity": int(row["quantity"]),
}Answer and explanation
Correct answer
B. Measure before optimizing, then change the part that actually dominates cost instead of guessing from style alone.
Why
Premature optimization is usually weaker than targeted optimization backed by measurement.
Test yourself on Data Cleanup
A free test with instant, explained results. No account needed.
More Data Cleanup questions
- A teammate submits shaky safe output writes code. Which review comment is the strongest?
- When is safe output writes being used in the wrong way?
- What is the clearest sign that code around safe output writes should be refactored?
- You cannot rewrite everything today. What is the best incremental improvement around normalization pipelines?
- Which move is the best default when normalization pipelines becomes part of this workflow?
- Which option describes the most likely pitfall around normalization pipelines?