Should I start a project I am hoping to recruit others to?

Question

I have an idea for a program that I think is a good one (Don't we all?). I am an amateur programmer and would like to recruit some more advanced programmers onto the project since there are some aspects that I am not skilled enough to do myself. Is it better to

a) Develop the software on my own as much as I can, even though it will be amateurish, and then show a demo to potential recruits

or

b) Try and recruit some more advanced programmers and seek their advice and guidance before I get started so that it is done correctly from the beginning?

I would especially love it if someone has any experience of being in a similar position, but sage speculation is welcome too.

Answer 1

Nobody should start to undertake a large project. You start with a small trivial project, and you should never expect it to get large. If you do, you'll just overdesign and generally think it's more important than it is likely at that stage. Or worse - you might be scared away by the sheer size of the work you envision. So start small, and think about the details. Don't think about some big picture and fancy design. It if doesn't solve some fairly immediate need, it's almost certantly over designed. And don't expect people to jump in and help you. That's not how it works. You need to get something half way first, and only then others will say "hey, that almost works for me", and get involved in the project.

— Linus Torvalds

pretty much sums it...

Answer 2

Ideas are cheap.

Nobody is going to care that you have a good idea (or at least think you do).

Unless you have money to throw around, you are not going to interest an advanced developer. From my perspective, I estimate the goodness of an idea as inversely related to how good its originator thinks it is.

If your skills aren't good enough, there is only one way to improve them. Use them! Reach for the stars and try and develop the software. Even if nothing comes of it, you will have made your skills much better.

Answer 3

If you don't start, it will never be done. Best case scenario for choice B? You'll find many "advanced" programmers who are fully on board, who would like to create a domain name for the project, logos, feature lists for version 2.0, ... everything but actual coding. They'll respect the concept so much, they won't want to blemish it with anything that might go wrong.

Actions are what count. If you have a really great idea, you'll be on your own for a while. You may have troubles communicating it, because you've internalized it so much, and it will seem that people are incapable of seeing your vision. They'll comment on trivial matters and miss the big picture. Until you have something concrete, that's how it's going to be. Only in working with it for a while will you be able to get your perfect elevator pitch for it.

At this point, since you explicitly mentioned you were looking for sage words: Have a growth mindset. Programming advanced things is how you become an advanced programmer. Where you are now doesn't matter. What matters is that you reach a new personal best.

Go with A. And good luck!

Answer 4

Do it yourself - a half baked, poorly coded, badly designed, dripping-from-all-sides, heavily bandaged version 0.1 for your software is far better than no software.

Also remember that you need to sell it to your customers, not your developers. If you find paying customers for software you can easily get developers to add to your team. And customers need to see SOMETHING. If you have some large customers lined up for v1 of your software whenever it is going to come out, I don't see why developers won't come onboard. Besides you are paying them aren't you?! ;)

And yeah this comes from experience. Customers can tell you much more about your product than other developers can. (not how to build, but what to build)

Answer 5

Can you explain why a skilled programmer would want to implement your idea for fun, when I am sure they have plenty of their own to implement?

I have been programming for around 25 years, ( I started early) but as I have explained to my employers over the years I do the programming for free. The reason why they pay me is to tell me what to program, to insist that I turn up to the office, to follow a certain dress code etc...

Now, if you put together the proof of concept demo, show it around, have someone approach you looking for an investment and then start looking for a technical architect - then you are able to pay someone to take your idea and turn it into a product.