Skip to main content

Senslessness of software patents...

Why I don't support them:

1) Patents in software tend to be granted for trivial, non novel solutions that any competent engineer with a few minutes or hours to think about the problem will emerge.

2) Innovations in software and hardware engineering are much more difficult to reverse engineer making them more stable when subject to attempts to copy. Reverse engineering much of software code (algorithms) is rendered impossible depending on how the code is implemented or made available for end use. The innovation is in the secret of the algorithm(s) which is locked in the implementation, as long as that is kept away from prying eyes it is a *defacto patent*. Reverse engineering such tech. is either very hard or impossible (especially for web services) so again lessening the need for formal patents in the space.

3) Once granted a trivial patent is like a hammer that prevent others from right to apply trivial methods and forces money into licensing deals instead of paying for more *innovation* in the form of R&D on new products and services.

4) Once granted and later defended or used to defend, large bulks of money go to lawyers...who in no way contribute to building innovation which can change human lives, it's wasted *human* investment.

5) In industries were patents don't apply there is rampant innovation (take fashion) and no shortage of competition or players willing to invest time to create new ideas (in clothing) ...if something is copied fine, they just innovate some thing new for the next season. We need that type of rapacious innovation to take hold in technology, and eliminating patents in the space (to some ironically) would do that.


Ted talk on fashion and innovation by Johanna Blakely


Popular posts from this blog

On the idea of "world wide mush" resulting from "open" development models

A recent article posted in the Wall Street Journal posits that the collectivization of various types of goods or services created by the internet is long term a damaging trend for human societies.

I think that the author misses truths that have been in place that show that collectivization is not a process that started with the internet but has been with us since we started inventing things.

It seems that Mr. Lanier is not properly defining the contexts under which different problems can benefit or suffer from collectivization. He speaks in general terms of the loss of the potential for creators to extract profit from their work but misses that this is and was true of human civilization since we first picked up a rock to use as a crude hammer. New things make old things obsolete and people MUST adapt to what is displaced (be it a former human performance of that task or use of an older product) so as to main…

Highly targeted Cpg vaccine immunotherapy for a range of cancer


This will surely go down as a seminal advance in cancer therapy. It reads like magic:

So this new approach looks for the specific proteins that are associated with a given tumors resistance to attack by the body's T cells, it then adjusts those T cells to be hyper sensitive to the specific oncogenic proteins targeted. These cells become essentially The Terminator​ T cells in the specific tumor AND have the multiplied effect of traveling along the immune pathway of spreading that the cancer many have metastasized. This is huge squared because it means you can essentially use targeting one tumor to identify and eliminate distal tumors that you many not even realize exist.

This allows the therapy for treating cancer to, for the first time; end the "wack a mole" problem that has frustrated traditional shot gun methods of treatment involving radiation and chemotherapy ...which by their nature unfortunately damage parts of the body that are not cancer laden but …

Engineers versus Programmers

I have found as more non formally trained people enter the coding space, the quality of code that results varies in an interesting way.

The formalities of learning to code in a structured course at University involve often strong focus on "correctness" and efficiency in the form of big O representations for the algorithms created.

Much less focus tends to be placed on what I'll call practical programming, which is the type of code that engineers (note I didn't use "programmers" on purpose) must learn to write.

Programmers are what Universities create, students that can take a defined development environment and within in write an algorithm for computing some sequence or traversing a tree or encoding and decoding a string. Efficiency and invariant rules are guiding development missions. Execution time for creating the solution is often a week or more depending on the professor and their style of teaching code and giving out problems. This type of coding is devo…