Ask HN: where do you draw the patent research line?
When you've got an idea you like and believe in, how much time should you dedicate to patent research before getting into proper planning, coding and all the rest of the fun stuff?
a) Lots, be exhaustive
b) Some [any estimates of how much?]
c) None, just get it out there
I ask because a couple of years ago, for a startup that didn't make it to market (for a reason totally unconnected with patents), I spent the best part of two soul-destroying months poring over lots and lots of chunky patent documents, looking for things that might block what we were trying to do.
After all that time, an IP lawyer friend of mine said (in more or less these words) 'Just get it out there and see if anyone complains, then deal with it'. I'm operating in the UK, too, which seems to have a more favourable (for me) view of the ridiculousness of [edit] some [/edit] software patents, too, in the sense that they're harder to enforce over here, I gather. So in the end, we just went ahead (but then got sunk by another issue, but that's a different story, dammit.)
So, I was just wondering what the HN community thinks about it all. Did you spend ages poring over patents before cutting any code, too?