pizzaparty2

I'm specifically interested in C# and JavaScript if you require that distinction.

I have a novel invention that I am pretty sure at least some people will like. I haven't done a whole lot of market research except searching for similar products, a patent search, and just kind of knowing that the device would be useful for certain people.

I'm making the device now. I'm actually several iterations in but it's shaping up. I think I will be able to launch the Kickstarter in about four months.

I'll probably set the lowest possible number for "success". That would include remaining legal expenses I haven't paid like getting it UL listed, etc.

So say I set the Kickstarter goal to $20,000. I could put $2000 in myself and I think get another $2000-$3000 from local supporters. That's 25% funded which I think has a chance at providing the initial momentum the project will need.

Say I get to this point. I've had a successful $20,000 Kickstarter. I order ~500 boards and cases and assemble and ship them myself.

But then what? I'll have a successful POC and made a net profit of maybe a couple thousand bucks. How do I grow it from there into a bigger product? For example, I think the invention could be useful to a larger percent of the population than I will capture with just Kickstarter marketing.

I think I can do a successful Kickstarter but I don't know how to capitalize on that.

For example, say you code the same type of C# every day. Or worse, say you've found your way onto a team with developers who don't know the language and certainly don't know how to do anything but write in that very basic C++ style that you learn in programming 101. At that point there's no point for you to improve because it doesn't matter what you know.

Another example is how you often times have to spend all day working. After sitting still in a chair being torture forced to figure out someone elses astonishing code for 8 hours I don't want to go home and sit in a chair and code. I want to join the local fight club.

Another example is it's incredibly aggravating to me when I know all about a subject for some reason (perhaps learning about it off work or at a previous job). By chance this subject comes up at work and I try to steer the team the right way but quickly discover how little my expertise matters in a room full of ignorant decision makers.

Have you ever noticed that being employed as a programmer actually caused you to become a worse programmer? Do you have examples of your own?