Comment It isn't just in software (Score 2) 735
This is a common occurrence in many fields with a high technical bar. Usually, the person with the "plan" has a pretty high opinion of themselves, which may or may not be justified. I see a lot of "genius children" (labeled by their parents) with big ideas that just need "a few things" worked out to have their Invention built and make a ton of money for them and their parents.
To give an example from a nerd hobby forum, it's common in an amateur ROV group I frequent to get questions from new members, usually teenagers, saying something like the following: "I have a great ROV design that will dive to 5000 feet, be small enough for one person to carry and use, and will only cost $10,000. It can be used for (insert random phrase describing any "cool" ROV use here). I have the design almost done and I'm going to take it to various companies to get the manufacturing done (read as: try to get someone to buy my design and give me lots of royalties) and I just need details on a few things. First, can someone tell me how I can seal a motor against water getting in? Second, I plan on using outdoor extension cord cable with fiber optics inside for communications, can someone tell me where I can order this online? Third, I'm going to need a special caulk to seal the wires where they enter the hull of the ROV, where can I buy that in a small tube for under $10?"
Usually the person doing this has drawn up a couple pictures or mock-ups in a CAD program or even a modeler like Blender or Maya. They've usually picked a use for their ROV without understanding anything about how the use relates to design, specifications, or capabilities. If anything they've designed their model with superficial features that make it "work" for the use intended, like drawing in an arm with a sawblade on it "for cutting off damaged well heads". Note that I'm not talking about an actual design, they've just drawn a picture of a (possibly) cool looking ROV, spending as much time on the paint job as the shape.
The thing all the people that do this have in common is a very human attribute - they want to believe they are special, that they are geniuses, and that they will be able to make a living/get rich/get famous without having to do it the way "ordinary" people do, through education, luck, and hard work.
That's not a horrible fault, but usually they don't want to hear that the "great design" they have, no matter how detailed, is in fact the "easy" part of creating something like they want. They don't want to hear they're not a genius and that what they want isn't simple. They interpret you telling them that it isn't that simple the same way they'd interpret someone saying "I'm not smart enough to do what you're asking" or "We big industry guys don't like to listen to new ideas". Heaven help you if you try to actually produce a quote for the work they want you to do.
People like this are why the term "hubris" exists.
If it's a kid I try to encourage them to keep thinking great ideas, but to get some education in what they want to do. If they just won't listen, sometimes I just ignore them and let them find out on their own that they're dreaming.
The same thing works for non programmers designing software. They are great if they know they're designing a user interface or interaction, and that what they want may not be possible. That kind of perspective can really help a deep technical person produce a great product. If they're convinced they have a product ready to go and that all that needs to be done is write some code, it's the same Hubris. They probably won't listen. Just ignore them unless you have the patience to get them to understand (for example, if you're a social worker or a canonized saint).