You know you've been around the block a few times...

[jducoeur]

... when your internal monologue goes something like this:

"A-ha!  Yes, that looks like the right solution to the problem."

(Smug.)  "Oh, I like that -- it's pretty innovative, and I think it's even a good user workflow."

(Dismay.)  "Oh, crap -- that means I probably have to write an effing patent..."

ETA: folks, I appreciate that you're trying to help with the comments, but you're not -- you're making an extremely difficult and painful decision much worse. I've been studying this question at *least* as long as any of you, I understand it quite deeply from all sides, and quite frankly, you're not in my shoes and don't understand the sheer number of issues I'm juggling here. Please stop.

Comments

[serakit.livejournal.com]

Because if you do something innovative and don't patent it someone else will steal it and patent it and make you not use it anymore?

[mindways]

...why? With public commits, proving prior art if someone else tries to patent it later ought to be trivial, I'd think?