Software Engineering · Product & Engineering
A short, time-boxed technical investigation done to answer a specific question or reduce uncertainty — not to produce shippable code.
Example: Spending two days checking if an approach is technically possible before committing to it.
In practice: A spike is deliberately throwaway — code from a spike shouldn't ship as-is, since it skipped the design and testing rigor of real feature work.