Writing software often involves taking known patterns, combining and shaping them, and adding needed context or specialization related to the problem we’re trying to solve. Sometimes, that means writing something that’s effectively been written by someone else before. But sometimes, that means creating something new.
What should you do in a case where you’ve genuinely created something new? Perhaps more importantly, how do you know when you’re in that situation?
This month, we explore one of the best tools to help answer both questions: the patent process. Listen along with your fearless co-hosts and a member of Klaviyo’s legal team to learn about what a patent is, why getting them matters, and how to get your own novel work patented, along with:
Tips to keep in mind when applying for a patent
Knowing which software you should try to patent
How to get your organization to buy into patents
For the full show notes, including who's who, see the Medium writeup.
Podden och tillhörande omslagsbild på den här sidan tillhör
Klaviyo Data Science Team. Innehållet i podden är skapat av Klaviyo Data Science Team och inte av,
eller tillsammans med, Poddtoppen.