core practice · system design prompt
Design exercise: Static & Dynamic Analysis
ASTs, control/data flow, abstract interpretation, symbolic execution, sanitizers, profiling, and runtime instrumentation. Implement designOutline() returning non-empty values for: programModel, analysisRule, runtimeEvidence. Each value must name a concrete mechanism or decision.
The mechanism
Static analysis reasons over possible executions; dynamic analysis observes actual executions. Combining them trades breadth for concrete evidence.
Expected evidence
A design outline with programModel, analysisRule, runtimeEvidence plus an explicit failure mode or trade-off.
Try this drill in the practice workspace →
Hints when you need them
- Name the failure mode before selecting the mechanism.