spec = specifications. This could be 1. requirements gathering (use case focussed in words of client) -> 2. functional specifications (use case focussed in terms of developer / exhaustive) -> 3. technical specifications (low level plan on how to implement). Often 3. and sometimes 2. aren't done explicitly, but are part of iterative / agile methodologies. 1. however, must still be done imho

Thanks. I did know that spec by itself is short for specifications - I'm a developer, and also have software engineering experience, so knew abut your points 1 to 3. My point was that spec work seemed like something else. Also see my other reply to a child comment to yours.

I think in this case, the parent meant working speculatively [0] which can be seen as risky for some, but also a way to get some reputation & awareness.

[0] http://www.nospec.com/what-is-spec

Thanks. Yes, I think this is what the original comment meant that I was asking about. Now I remember where I read the term "spec work" - it was some weeks ago on avc.com, Fred Wilson's blog. And someone gave the same answer there as you, IIRC.

It's not specifically a tech term, e.g. spec scripts in the entertainment business:

https://en.wikipedia.org/wiki/Spec_script