Comment by confusedbucket
16 hours ago
That confirms the recent spike of Claude calling everything I was recently working on a 'spike'. I still don't know what that term is supposed to represent (apparently).
16 hours ago
That confirms the recent spike of Claude calling everything I was recently working on a 'spike'. I still don't know what that term is supposed to represent (apparently).
In some software development methodologies, "spike" is a task whose goal is figuring something out instead of delivering shippable code. https://agiledictionary.com/209/spike/
TIL that agile has its own words for everything.
That was a thing in the early 2000's. You had to have a blog and invent words that describe regular things everyone did.
Why can't they call it a prototype or experiment? Sheesh.
Prototype is usually something working, while spike can be pure research (e.g. validate that APIs are feasible and enough, or that something satisfies requirements). Prototype is usually more polished/usable. Experiment in my mind is something which user-facing but not in stable yet.
So for me they are differentiated enough, but could be that I am just used to it.
1 reply →
A spike is an early prototype that you're supposed to throw away after having figured out the real design.
I think it was subtly dissing you.
I think you are subtly dissing me :)
I was half-joking, of course I could've just asked Claude, but the linked site shows there has been actual recent spikes in the use of the word 'spike'. The term does match what I was recently doing, but hacking around legacy ERP software, blackboxes and other enterprise abominations isn't that out of the ordinary for me.