Slashdot Mirror


'I Just Need a Programmer'

theodp writes "As head of the CS Department at the University of Northern Iowa, Eugene Wallingford often receives e-mail and phone calls from eager entrepreneurs with The Next Great Idea. They want to change the world, and they want Prof. Wallingford to help them. They just need a programmer. 'Many idea people,' observes Wallingford, 'tend to think most or all of the value [of a product] inheres to having the idea. Programmers are a commodity, pulled off the shelf to clean up the details. It's just a small matter of programming, right?' Wrong. 'Writing the program is the ingredient the idea people are missing,' he adds. 'They are doing the right thing to seek it out. I wonder what it would be like if more people could implement their own ideas.'"

11 of 735 comments (clear)

  1. As a programmer by Anrego · · Score: 5, Insightful

    I disagree. A terrible idea with a beautifully executed development goes no where. A great idea that is hacked together with shell scripts and kilometers of spaghetti code can make someone a fortune and (lame as it sounds) change the world.

    That said I think having solid developer(s) is a really good thing. It costs less, makes for a more reliable product, and enables you to say "yeah, we can add that" vs. "hah, you'd have to rewrite everything" when further great ideas come along.

    But saying that the importance of programming is on par with the idea.. it's not. Much as us programmers like to think we are _the_ critical component.. I really don't think we are in a lot of cases. The idea and the marketing are what makes the product successful. HR tends to think of programmers as production line workers.. and as much as I hate to admit it, there really is truth in that. We turn ideas into something tangible so they can be sold. If we produce better products or produce them more efficiently, we make the company more money.. but we arn't as important as the guy's who tell us what to make, or the guy's who get people to pay for it.

    As for idea people learning to program.. I don't buy it. Might work for some people, but I think programming/working with technology is either something you enjoy or you don't. Most good programers I know don't care about the end product as much as the code. The end product is a necessary evil.. a reason to justify their code poetry. Learning programming as a way of achieving and end goal sounds like some bad code about to happen. And I thought the whole "managers can write code thing" died with COBOL.

    1. Re:As a programmer by Ndkchk · · Score: 5, Insightful

      A great idea that is hacked together with shell scripts and kilometers of spaghetti code can make someone a fortune and (lame as it sounds) change the world.

      Not quite. A great idea that is hacked together will almost certainly be "borrowed" and better implemented by someone else, making them a fortune. The world still gets changed, I suppose.

    2. Re:As a programmer by drsquare · · Score: 5, Insightful

      Ideas are ten a penny, it's the implementation that matters.

    3. Re:As a programmer by arth1 · · Score: 5, Insightful

      I have replaced quite a few C++ and Java programs with just shell scripts, where it was expedient. Because having the guts to kill your babies whenever needed can be damn effective.

      Like instead of elegantly reduce an expensive database lookup loop by 10% execution time, you ditch it and push a diff to a local hash table instead.

      Or instead of reducing the sort across a table by 5% by choosing the most efficient algorithm, you do a Schwartzian transform and only sort the parts you need, saving 95% time even if you now do it in a script.

      Programmers often stare themselves blind at the problem at hand, not seeing the bigger picture and how the best solution is not doing what they do as well as it can be done, but doing something entirely different. Which quite often can be done just as well with a script.

      As for spaghetti code, sometimes that's warranted to. Instead of rolling back through 300 levels of recursion to return, it just might be expedient to chop the Gordic knot with a well-placed goto.

      (And no, 300 is not an exaggeration. I knew a programmer who made a web site with multiple entrances and breadcrumbs. Someone browsing the site for a few hours or days could have a linked list longer than you'd think, and clicking "go home" caused it to roll back each layer one by one, until hitting the entry page of that particular user. Which could take 5-10 seconds of unnecessary waiting. I suggested storing the entry page as a global session variable and simply Go There, and was looked at like I had grown two extra heads.)

  2. It's bologna by drumcat · · Score: 5, Insightful

    If someone says that, "they just need a programmer", they haven't vetted the idea. If they really knew what they wanted, they wouldn't need a programmer - they'd need a contract fulfilled for a specific task. If you say that crap, you're just a bullshit marketing guy.

  3. summary makes a good point but nothing new by epyT-R · · Score: 5, Insightful

    idea people often take the form of upper management. they always assume their ideas are workable, and if their employees are having trouble rewriting reality to make them happen, then it's due to the employees' ignorance and not their own. classic ivory tower syndrome.

  4. "Just" by KingFrog · · Score: 5, Insightful

    Really, I am already re-thinking my earlier reply. The issue here is summed up in one word - "Just". You think you need "Just" a programmer, or "Just" a marketing guy, or "Just" a salesman? You have already told me that you don't really value their contribution to the effort, and additionally that you don't really understand fully what goes in to the work they're doing. Yeah, you have a genius idea. You don't want "Just" a programmer. You want a genius programmer, preferably either with a passion for your cause, or a resume of working in coding similar things. Otherwise, your operating system is being written by "just" a database programmer, and while you will have great search times, you may find other areas coming up short.

  5. Not the only side of the problem by Bruce+Perens · · Score: 5, Insightful

    I've met people who have excellent working software, and have had it for years, and simply aren't able to make a business out of it. They think I just need an investor! And this when it would take them hundreds of dollars to actually start their business, after which they'd have a lot more value to an investor, if they decided they still need one.

  6. Ideas are cheap... by nine932038 · · Score: 5, Insightful

    Implementation is something else. What so-called 'idea people' don't realize is that without implementation, ideas are worthless. And you know what? Implementation is hard.

    Starting a business is hard work!

    The intangible benefits are pretty great, of course - freedom to set your own hours (clients permitting), freedom to set your own priorities, that sort of thing. That's all great. But the costs are pretty hefty. It's not just the money - though the money is a big problem too!

    It's about the stress of getting a business off the ground. It's about taking half pay, living expenses, or no pay whatsoever while the business gets off the ground. It's about hiring someone new and wondering if they're actually a fuckup who's going to pull you down. It takes grit! And after the first year, you end up wondering if you did the right thing - if working for someone else might not seem so bad after all.

    I used to guard my ideas jealously, but these days I don't even care. Go ahead, 'steal' my ideas. Then, whether you fail or succeed, I'll watch what you did. And if I have the opportunity... I'll give it my best shot to do it better.

  7. "Just" Ice 4 all by Yergle143 · · Score: 5, Insightful

    "Just" quit smoking. "Just" exercise and lose weight. "Just" balance the budget. "Just" get off foreign oil. "Just" win baby.
    "Just" is the word that betrays the orders of magnitude energetic difference between the running of the mouth and the actual doing of something.

     

  8. As an example by Sycraft-fu · · Score: 5, Insightful

    I "had an idea" for Kinect over a decade ago. Having toyed with VR stuff and motion capture and the like I though "Man, it'd be really awesome to have a device that does visual and shape capture at the same time, to be able to get a full 3D capture of a world in to an editor." I personally was thinking something along the lines of an IR laser rapidly scanning a scene (like a laser shape capture device but larger).

    Wow! Amazing! I so thought of it years before MS! I should be rich!!

    Well... No.

    All I did was think it was a neat idea. I had no fucking clue how to make it work. I just thought such a device would be great and would be doable, and had maybe a vague idea of what you might try. That is in no way shape or form something you could start development from or really anything unique. I'm sure tons of other people had the idea. What makes Kinect unique is that they got a team together, had engineers sit down and figure out how you might build such a thing, and do it cheaply, and now other people have figured out how to use data from it to reconstruct 3D scene data on a computer. The idea is not the hard part, the implementation is.

    Even in purely idea fields, having a vague idea isn't amazing or worth anything, showing its worth is. Feynman didn't win the Nobel prize because he had an idea about how the spin of particles might relate to larger phenomena (such as the spin of plates, as he talks about in his book). He won it because he turned that idea, that spark, in to a theory of quantum electrodynamics that is detailed in its construction and makes extremely accurate predictions. Had he just said "Huh, it is interesting that the amount a plate wobbles when tossed is an integer ratio to how much it spins. Maybe that has something to do with the way particles work," well then nothing would have come of it. His work was all ideas, but the important part of the idea work was developing it in to a complete, useful, theory.