3 ms·

The way I've heard successful start up types describe this is issue is like so. Keeping your idea a secret is only going to hurt you and the project because it

by burrows 16y ago

The way I've heard successful start up types describe this is issue is like so. Keeping your idea a secret is only going to hurt you and the project because it doesn't have the opportunity to grow with the criticisms of potential users and people who think differently than yourself. So in general you should talk to people about your idea. That is unless, your 'secret sauce' is something on the order of Tungsten being the secret to light bulb filaments. That you would want to keep a secret. I tend to agree with this assessment.

curt 16y ago
When I invent something this is exactly what I do. I have no problem explaining everything up to the 'key' that no one else would be able to replicate without me explaining/showing them. Even then I have no problem telling them 'the secret sauce'... I just don't show them how it works or how to do it. Now you also have a type of secret sauce called operational knowledge. For example I know how to take an idea, prototype it, and produce it in days. I could explain to someone exactly how to do it and they would still fail because you need the experience and breath of knowledge. In those cases I rarely hold anything back, unless it involves a piece of equipment/technology I've designed that revolutionizes a process.
- burrows 16y ago
  Despite the fact that Operational Knowledge can be hard to replicate with the efficiency of someone who has more experience. I find talking to more senior engineers about their development process (or even just pair programming with them) to be very insightful. Even if it's just a matter of how they have their key bindings set, terminal aliases, window management, testing integrating, etc. Stuff like that is nice to pick off of people who have honed it over some time.
  - curt 16y ago
    Sorry, I was referring more to manufacturing,production, and logistics knowledge. Most of my experience revolves around combining software with physical products, working with partners around the world to get them to a stores shelves. Since there are only a hand full of people with the breath of knowledge to design, prototype, and manage every step combining both software and the physical I tend not to worry.

by burrows 16y ago

curt 16y ago

When I invent something this is exactly what I do. I have no problem explaining everything up to the 'key' that no one else would be able to replicate without me explaining/showing them. Even then I have no problem telling them 'the secret sauce'... I just don't show them how it works or how to do it. Now you also have a type of secret sauce called operational knowledge. For example I know how to take an idea, prototype it, and produce it in days. I could explain to someone exactly how to do it and they would still fail because you need the experience and breath of knowledge. In those cases I rarely hold anything back, unless it involves a piece of equipment/technology I've designed that revolutionizes a process.

burrows 16y ago
Despite the fact that Operational Knowledge can be hard to replicate with the efficiency of someone who has more experience. I find talking to more senior engineers about their development process (or even just pair programming with them) to be very insightful. Even if it's just a matter of how they have their key bindings set, terminal aliases, window management, testing integrating, etc. Stuff like that is nice to pick off of people who have honed it over some time.
- curt 16y ago
  Sorry, I was referring more to manufacturing,production, and logistics knowledge. Most of my experience revolves around combining software with physical products, working with partners around the world to get them to a stores shelves. Since there are only a hand full of people with the breath of knowledge to design, prototype, and manage every step combining both software and the physical I tend not to worry.