-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Working on a "Spike" #34
Labels
Comments
@iteles an older example of a "Spike" we did is: https://github.com/dwyl/meteor-search |
Basic definition added to: https://github.com/dwyl/technical-glossary#spike via dwyl/technical-glossary#41 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think this deserves a separate section as:
a) Less experienced developers don't tend to know what a spike is
b) It is, in my experience, something which has been treated with very little process and as a result, the information resulting from it is often not useable.
What?
A spike is a limited period of time (often between half a day and two days) during which you try a number of different methods to solve a problem, in order to determine what the best solution is. The code that you write during this time is not used directly in the project, but the lessons you learn are.
How to perform one?
The text was updated successfully, but these errors were encountered: