Hacker News Reader

Comment by krmmalik | Hacker News Reader

I'm a big believer in not operating in so called "stealth mode" so i try to share as much as I can, but lately i've been working on two separate products, one of which is an MVP at the moment. For some reason - and rather irrationally - I started to get worried about it when discussing with other developers. I'm currently considering bring a second person on board to work on the code with me.

Can you re-assure me that most developers think like you do? I am genuinely nervous about it bringing someone else to work on the product for this reason alone. I realise how pathetic it may sound, but a little re-assurance would give me a big enough nudge to go ahead and do it.

Unless there are specific cases where this shouldn't be done?

View on HN

Speaking as a developer: I like to build things that are successful and I like building things for passionate people. I'm not a thief, I'm a developer. I love bringing ideas to reality.

The people who are out there making money are doing so because they executed their ideas or helped to execute ideas with someone else. They aren't just sitting around waiting for the next person to screw over, they have better things to do: like work on things. Of course: there are always malicious people out there, but I would be extremely surprised if they were in the majority in this particular example.

Of all of the startups that get featured here, even the multi-million dollar ones, how many times have you heard of someone genuinely "stealing" someone's idea? I mean to the point that someone was put into financial hardship without a way to reconcile? I can only think of a couple off the top of my head, and frankly: the events and legal BS surrounding them are so far above and beyond anything I'd ever want to do in my life. I have a feeling that I'm not alone in that sentiment amongst a profession of reasonably rational and intelligent individuals.

I'm going to stretch my definition of a startup and say Michael Arrington and FusionGarage.

I'm not up to date on whatever happened with it, but Arrington announced on TechCrunch the CrunchPad, kept everyone abreast with its development, and when it came time to launch FusionGarage decided to go it alone and cut him out (allegedly).

Also, you can stretch it even further and use Jonathan Coulton's latest spat with the producers of "Glee"

I think it happens, we just don't hear about it as much.

Great advice. Thank you.

> Can you re-assure me that most developers think like you do? I am genuinely nervous about it bringing someone else to work on the product for this reason alone.

Is the offer a full-ime living wage that is competitive in your area? If so make them sign the typical "Anything you do during company hours is owned by the company". Easy.

If you aren't then you'll need to bring something to the table otherwise you'll have scared away the right 2/3rds of the standard distribution of programmers.

If you're looking to hire cheap with no benefits the only people left interested will be people that just need the money... and you've just increased your chances of having your stuff stolen.

Understood. Thanks. There's a value exchange conversation currently taking place, where we're hoping to exchange services of value, but i acutely realise that value-exchange is sometimes a good idea, but not always.

Another thing to consider, if you can pull it off, would be to take whatever work you have find the bit that isn't directly related to your business and make them separate fully-functional-modules.

For example, Part of my application needs to extract zip files and search for the contents. This isn't the game changer part of the application but it is a necessary component.

This is where I've hired cheap India/China labor in the past, I've done the core work product and I've given them access to these submodules that if stolen wouldn't affect my application.

Eventually I'll be making these modules open source, and if any of them pick up traction I'll receive even more benefits for my application.

I was thinking the exact same thing just now. There are definitely parts of the application that can be worked on independently, and since it's going to be front-end stuff mostly (which is visible any way), i can ask for the code to be worked and separately and i can integrate it myself into the main app.

> I am genuinely nervous about it bringing someone else to work on the product for this reason alone.

You gotta risk it to get the biscuit.

It's just my opinion but I believe that sometimes the fear can cause more damage than the thing you are afraid of. Yes, be careful... but don't overdo it. Someone might steal your idea but if you get all paranoid you will focus on preventing the bad stuff instead of building something great. You can force everybody to sign NDAs and set up the whole bureaucracy protecting you from idea-stealers... which will probably drive the best people away and your great idea will go nowhere. Just my $0.02.

I agree. I don't normally think or behave like this, but you're right. I have to take the risk if i want to move forward.

I obviously can't take responsibility for every developer in the world, but most of them I know think in a similar fashion that me. :)

I think you need to consider your advantages and the fact that you are already ahead with your MVP. There is no need to disclose everything. Besides, even if your MVP is working as it is supposed to, there are miles till you actually make in in the market. Been there, done that.

Think about this: if the person has the skills / connections / opportunity to make execute this idea better than you, you should consider him / her a partner in the project.

Very valid points. Thank you for re-assuring me and helping me to think about things differently as well.

Reply on news.ycombinator.com