Thank you! And please, any clarifications / nitpicks corrected would be a huge favor, feel free to post here and I'll pin the comment (if I can figure out how :))
In software, we typically reduce to practice before we patent. It doesn't have to be released software, but it should be a running prototype. Take a look at the overall structure of the system you're building, the communications between components, and the key decision engines / state engines that help it to work correctly and effectively. Figure out whether your software is doing something that has value. If it has value, and if you're doing non-trivial things for some of the areas above, consider for a patent. Also, we typically had a contact in our organizations who would review patent ideas for value, and they could tell you whether it was worth writing up.
When it's as developed as possible but before any public disclosure. It sucks having to update your patent submission because the design you submitted won't work and you've revised it to one that will
The only risk I'm aware of is that if you do related work, they can claim you're doing it in a way that infringes the patent, and sue you for damages. Of course, they have to be able to prove it...
@@TheDeliberateEngineer Or you read the patents then join another company that doing the same thing. It happens to me. I love reading patents til I joined this company for medical devices that has the same patent that I was reading before. Then the other company find that out that they will able to sue the company where I am in.
To clarify, it's not *you* but your company. The issue is that if the other company can prove that someone, anyone, at your company had knowledge of the patent, then they can leverage that knowledge into an argument that the infringement was *wilful*, in which case, the damages calculation can be tripled.
![เปิดบ้าน พี่ตูน Bodyslam หลังใหม่คนแรก ที่ภูเก็ต l [Nickynachat]](http://i.ytimg.com/vi/flFwcmyDQSk/mqdefault.jpg)
Patent attorney here and you did a great job explaining things. I'd have a few nitpicks and clarifications, but overall this was very well done!
Thank you! And please, any clarifications / nitpicks corrected would be a huge favor, feel free to post here and I'll pin the comment (if I can figure out how :))
Thank you so much for sharing!! ❤
Great insights
thanks for watching!
U need to do prior art searches BEFORE filing a software patent. Google Patents and Patentscope are best...
There's no requirement for that. And if that's to be done, it should be left to the attorneys, not the inventors.
How much do u pay in patent maintenance fees? 👀
How do we identify the areas in which we can get an idea to file a patent? How do we know that’s the Eureka moment?
In software, we typically reduce to practice before we patent. It doesn't have to be released software, but it should be a running prototype. Take a look at the overall structure of the system you're building, the communications between components, and the key decision engines / state engines that help it to work correctly and effectively. Figure out whether your software is doing something that has value. If it has value, and if you're doing non-trivial things for some of the areas above, consider for a patent. Also, we typically had a contact in our organizations who would review patent ideas for value, and they could tell you whether it was worth writing up.
Thank you!
When is it a good time to get a patent? After the pro typos done or before?
When it's as developed as possible but before any public disclosure. It sucks having to update your patent submission because the design you submitted won't work and you've revised it to one that will
USA is a “first to file” system, not “first to invent.”
As software engineer don't look into any of these patents. Companies can sue you over this.
The only risk I'm aware of is that if you do related work, they can claim you're doing it in a way that infringes the patent, and sue you for damages. Of course, they have to be able to prove it...
@@TheDeliberateEngineer Or you read the patents then join another company that doing the same thing. It happens to me. I love reading patents til I joined this company for medical devices that has the same patent that I was reading before. Then the other company find that out that they will able to sue the company where I am in.
What do you mean by "don't look into"?
Literally just don't read them? Or don't make patents? Or don't copy inventions?
@@raxn2673 Just don't read them or don't have any knowledge of existing patents that you are currently developing.
To clarify, it's not *you* but your company. The issue is that if the other company can prove that someone, anyone, at your company had knowledge of the patent, then they can leverage that knowledge into an argument that the infringement was *wilful*, in which case, the damages calculation can be tripled.
Any USPTO patent over 20 pages will incur a fee.
MicroSoft SUX
False. Information disclosure sheet! Worst advice EVER!