Code spike
A code spike is a short, focused investigation or exploratory implementation undertaken to reduce uncertainty about a technical or product decision.
Test Driven: Practical TDD and Acceptance TDD for Java Developers
A spike solution is an exploratory prototype used to investigate a potential solution and estimate its feasibility or effort.
- How it is used
- Uses a short experiment to assess whether a potential solution works and is worth pursuing.
- How deep it goes
- Defines the experiment and walks through regex learning tests, while treating prototype code as disposable rather than production-ready.
- Examples
- Tests Java regex matches, their start and end indices, and whether capture groups affect matching.
- What you can do after
- Evaluate a potential solution by exploring an unfamiliar API and using the resulting knowledge to guide implementation.
Read how Test Driven: Practical TDD and Acceptance TDD for Java Developers explains code spike →
Grokking Software Architecture
A small, targeted technical experiment for resolving uncertainty before committing to an implementation path.
- How it is used
- Uses small experiments to investigate technical risks before the team commits to a path.
- How deep it goes
- Defines spikes as targeted experiments but gives no execution steps or evaluation criteria.
- Examples
- Checks whether a third-party library can handle scale or whether a cloud service is suitable.
- What you can do after
- Apply targeted experiments to resolve technical questions before committing to a risky path.
Read how Grokking Software Architecture explains code spike →
Also covered in
What to know first
- validationValidation is the process of checking data, behavior, or results against defined criteria to determine their correctness, acceptability, or suitability for a purpose.
Related concepts
- enabler storykind of · An enabler story is an Agile work item supporting exploration, architecture, infrastructure, compliance, or other activities needed to enable future functionality.
- risk scoutused by · A Risk Scout is an architectural role responsible for identifying and investigating technical risks before they impede development.
- test-driven developmentused by · Test-driven development is a software development practice in which tests specify expected behavior and guide incremental implementation, typically being written before the corresponding code.
- learning testuses · A learning test is an automated test that verifies assumptions about code and teaches how that code behaves.
- set-based designused by · An engineering approach that explores multiple design options in parallel, narrows them as evidence arrives, and delays commitment until further exploration is no longer worthwhile.
Questions about code spike
What is code spike?
A code spike is a short, focused investigation or exploratory implementation undertaken to reduce uncertainty about a technical or product decision.
Which Manning books explain code spike?
Test Driven: Practical TDD and Acceptance TDD for Java Developers and Grokking Software Architecture.
What should I know before learning code spike?
Manning books that teach code spike usually introduce validation first.
What is code spike a kind of?
Code spike is a kind of enabler story. An enabler story is an Agile work item supporting exploration, architecture, infrastructure, compliance, or other activities needed to enable future functionality.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

