7:41 PM EST :oooooh. LOOK at him scraaammbbbling to change terminology and entire sections in his post. I wish I could have saved the page from cache so people could really see the author's point in all this.
To those who missed the action: the author has gone from exclusively and falsely blaming one person from his team to taking a generic stance. Probably after reading all of this and realizing things don't make sense..
This is exactly the kind of stuff I had to put up for 5 months.
awesome. Anyway, that's enough of the drama. I'm out.
I wish I could but unfortunately- the author is very agile with his various BS NDA, Non-compete and what-the-hell-not forms. I'd rather move on to things in my life that don't waste 5 months of my time. Anyway, I just couldn't hold myself back from saying something when seeing the "leader" go on and publish his thoughts while suppressing mine and then misrepresenting a few things.
I'd rather end it here by saying I don't want to be a part of this new blame game and that the advice given is very sound and realistic. Tragically, the author has tried to apply his zero-technical background to very technical practices when trying to blow out his thoughts into relevant context provided by others. In the process, he has decided to dish out 50% of the problems, misrepresenting a few and then suppressing the other REAL 50% through NDA forms.
Lastly, so that it is clear- the author and his company paid 0 dollars for the patent- It all came out of my pocket and was the result of years of work.
In my opinion it is wise to file a provisional patent for an idea you think is worth it in all its uniqueness and by all measures, I (think I) did not commit a crime by trying to secure my invention/s.
Choose the people who you work for very, very carefully. Things like this (and probably worse) happen later.
hahaha. this is great- I tried to post my own experience with this start-up (and in my opinion, citing the REAL problems) and was told to take the post down (later, with legal text) and now I see this post, trying to parody the one I wrote with things like 5. and 8. - shame. I might want to add though, that the author does not have the technical expertise to figure out who wrote how much code along with other (many) misrepresentations- otherwise, 8, while very sound and correct advice, might differ in terminology and he might have a better idea fitting his take into existing context written by PG and others.
Nonetheless, most of the advice is realistic and useful in the sense that the points raised are practical and might help structure your startup.
To those who missed the action: the author has gone from exclusively and falsely blaming one person from his team to taking a generic stance. Probably after reading all of this and realizing things don't make sense..
This is exactly the kind of stuff I had to put up for 5 months.
awesome. Anyway, that's enough of the drama. I'm out.