Friday, February 27, 2015

House Words oh a Whim

In a moment of nerdiness, I took a goofy online quiz which would generate Game-of-Thrones-esque "House Words" for you. Some popular examples include:

        House Stark: Winter is Coming
        House Baratheon: Ours is the Fury
        House Martell: Unbowed, Unbent, Unbroken
        House Tully: Family, Duty, Honor
        House Greyjoy: We Do Not Sow
        House Frey: Our Cloaks are Reversible

Yes, I made that last one up. But it's fitting, no?

Anyway, I got a good laugh from the wise words the quiz appointed:

        House Allen: We Do Not Like How Much The Fourth Season Deviates From The Books

It's funny, and sad, because it's true. A bit odd considering I selected "Cryptic" from the choices of types of mottos, and that seems quite straightforward regardless. All the more fitting, come to think of it.

Now back to Hugh Laurie and my work! I'm nearly finished with my Provisional Patent App, to be submitted later today, at which point I'll be able to finish up that post and "lessons learned" and the like.

Saturday, February 14, 2015

The Patent Process: An Ambitious Adventure

Having come to a position of interesting balance between: A) a suspenseful excitement at nearing the point where I can make my project into a "real" business venture, gaining some legitimacy and support, and B) a paranoid anxiety that my dream will be realized by another individual or company before I can make it my own.... I'm finally starting the patent application process!

I figure this might be an excellent opportunity to document my steps, struggles, and lessons both as I go through them and in a retrospective summary. In the end, I could put together something of a straightforward guide to the bureaucratic maze for the layman. While I consider myself an intelligent person, I've never studied law and no little of intellectual property rights and the like. So I imagine I'll be able to capture the "typical new inventor" perspective, making it accessible to most prospective readers. Even more so given my youth, general life inexperience, and borderline naive optimism about the future fruits of my efforts.

Disclaimer: None of this post (or anything on this blog ever) should be considered as legal or financial advice. Consult the necessary professionals for official advice; don't take any action based on the content of this post or blog alone. Seriously, that would be moronic. I'm an amateur.

Attack of the Jargon!

The first few steps I'm taking are to: 
   [1] try and find a list of "steps" (i.e. which forms and in what order), 
   [2] exactly what documentation is required on my part (i.e. all the fancy diagrams with so many 
        labels & lines; one favorite here, and some classics made into posters), 
   [3] of course the associated fees, and
   [4] when do I even do this? From "neat idea" to "proof of concept" to "functioning prototype", at 
        what point is an invention far enough along to be patentable? 

The first roadblock I ran into was the language. As with much in government, the bastion of knowledge is defended by impenetrable walls of language, each stone an element of jargon mortared with unnecessarily formal phraseology making even the simplest of sentences a challenge to comprehend (Note that I typed that with a hint of irony... hard to convey via text!). 

So for starters, I'll collect a list of terms relevant to the patent application process, which should make official documentation and the like a bit easier. As I'm in the midst of work right now and just got distracted with the idea of writing this blog post, I'll probably edit it later with some more terms & definitions. But for starters:
  • Registered Practitioner: An individual certified/registered to practice patent law; i.e. a patent attorney or agent. 
    • Relevance: The first couple forms to file allow associating a registered practitioner. As I understand it: if a patent lawyer's helping you, s/he's your registered practitioner.
  • Pro Se Inventor: An inventor without representation/assistance from a registered practitioner. In other words, if you're doing this on your own, you're pro se. Like me. 
  • Small Entity: If the applicant is an individual or small business (< 500 employees, I think). Other circumstances apply as well (nonprofit, higher education, etc). 
    • Relevance: 50% reduction in patent fees! Hurray. 
    • I believe you don't necessarily need to provide "proof" or get approval of qualification as a "small entity" prior to filing the application. Micro, however, does prior approval.
  • Micro Entity: An individual (or multiple) who I) have low enough income and II) have less than four existing patents. 
    • I) Specifically less than 3x median income, which was about $155,000 last year. Or majority of income is from a higher-ed institutions ('s got helpful details).
    • For join inventors, each inventor has to individually qualify. 
    • Relevance: 75% reduction in patent fees! Double hurray. 
    • Requires prior approval/qualification, which is another form. 
  • Assignee vs Inventor: A corporation can't be an inventor, though often companies are who get the rights to patents. Thus the "Inventor" is one or more individuals while the "Assignee" is who ends up with the rights to the patent. If it's just you, however, then the inventor & assignee are the same person(s). 

Thursday, February 12, 2015

Gource: A Free (and Easy-to-Use) VCS Visualization

A friend shared this with me a while back, but I finally have a neat repo to test it on and a blog to show it off! Gource is a free tool that visualizes files & commits in a specific version control repo. The example below is a project I've been working on for a while. While the repo in the video is git, the author's page claims it also works with Mercurial, Bazaar, and SVN as well. 

 - Uploading directly to Blogger resulted in terrible resolution & quality in the version below. -  
(In case the video doesn't upload right, it's also on YouTube)

And it's pretty damn simple to use, too. Just running gource from a command line at the top level of a given repo runs it with its default settings, but it has a pretty extensive set of parameters if you want to change things (speed it up, specify date ranges, etc.).

In this example, there's really only one author (me), but I sometimes from a Raspberry Pi as well, which it currently just treats as a second user (named "pi", of course!), thus the second figure floating around.

My only wish is that it could somehow visualize the extent of the changes made to a given file, perhaps by color, or "flashing" that file's dot (varying brightness) temporarily, or maybe the changed file's dot grows in size for a second or something. That would make me feel better for those long hours and manny commits on a few particular files!

Anyway, really cool and free -- what can be better?