Skip to main content

If You're An "Ideas Guy", You're Doing It Wrong

There's a disturbing trend that I'm seeing more and more of lately in Silicon Valley, and it's the commoditization of engineering talent in the minds of non-engineers. I'm not sure what they're teaching in business schools these days, but I keep meeting freshly-minted MBAs who "have a great idea and just need some devs to implement it". So lemme just throw this out there:

If you're an "ideas guy", and "just need a couple of engineers" to build your company, YOU'RE DOING IT WRONG.

See, for instance, this recent TechCrunch article which blithely implies that engineers are "coding themselves into irrelevance", and before long, "the business founder [will have] the advantage that today's technical founders enjoy." Huh? Guess what - in healthy companies, it's not such an adversarial relationship. If it is, then you're doing something wrong.

There is no greater turn-off to a prospective tech co-founder or engineering hire than insinuating that they are nothing more than a replaceable tool. Last fall, I even flew to Korea to tell an auditorium full of engineering students that they are not tools, but instead are the engines of innovation for their future companies. Ideas are a dime a dozen - if you can't execute on them, then you are the replaceable part, not the devs you're looking to hire. A good experiment for any company is to switch roles for a day and see who is more productive - the "business guy" given a codebase and a problem to solve, or the "engineer" given a full day of "product strategy review" meetings. I'll leave that as an exercise to the reader.

Lest I be misconstrued, I'd like to point out that some of my best and most respected friends in the Valley and elsewhere are "business guys" (and girls), but what sets them apart is that they know their shortcomings (the same holds true for good engineers), they're willing and excited to learn about the tech world they do business in, and they treat engineers as partners rather than pawns. As a result, their teams are stronger than the sum of their parts. They have fostered an environment of mutual respect, where ideas can flourish and roles are not necessarily so artificially constrained. If you're a "business guy" that's just starting out, or you've been struggling to find good engineers, maybe it's time to reflect on your approach rather than decrying "how hard it is to find talent".

Remember: Engineers are people, not tools or commodities. Treat them well, and together you will build something great.




Comments

  1. I'm sorry Darren, but I couldn't disagree more. Engineering is a marketable and commoditized trait. I can pay $X for Y engineering hours. Different engineers have different skill levels, but engineering work is something you can buy and this is completely independent from the ability to discover and execute on good ideas. There are as many bad ideas that come from engineers as from non engineers and if you look back at the most prominent founders of the last three or four decades you will find that they never finished an engineering degree at all and/or most of the engineering work was not done by them at all.

    I don't know where this myth of "only engineers can come up with good ideas for anything that requires engineering work" came from, perhaps Google, but it's very silly. Maybe brick layers believe they are the only ones who have good idea for "successful" buildings?

    ReplyDelete
  2. I almost completely agree with "Unknown".

    ReplyDelete

Post a Comment

Popular posts from this blog

Why Korean Is Hard For Native English Speakers

A couple of days ago, as an experiment, I wrote my first blog post ever in a non-English language. It was an attempt to explain some of the reasons that Korean is hard to learn for native English speakers, so I figured I might as well try to write it in Korean. Those of you who actually read Korean can see how awkward the attempt was =).

In any case, the post came from an email conversation I had with The Korean from Ask a Korean, a fantastically well-written blog about all things Korea from the perspective of a Korean who moved to the United States during high school. Since I tend to geek out on language things, I figured I might as well post part of that conversation. An edited version follows.

---------

Out of the languages that I've attempted to learn so far, Korean has been the hardest. I've done a lot of meta thinking about learning Korean, and I think there are a number of reasons it's difficult for non-Koreans (and especially Westerners) to learn:

1) Obviously, the…

Stuttering in Korea

I had given up on English. It's my native language, but I figured after 30 some-odd years of disfluent speech, it was time to try something else. So I signed up for language classes in Korean, rationalizing that if I was going to try to teach myself how to speak, I might as well learn a new language along the way.

This might seem completely insane, but when the prevailing theme of your conscious thoughts for multiple decades is some variant of "Why can't I say what I want to say?", you come up with lots of crazy ideas.

For background, I've been a person who stutters for my entire life. I wrote about it on this blog a few years ago, so I think it's time for a followup. I've learned a lot since then, about myself and about stuttering, but in this post I simply want to give some insight into what it's actually like to stutter, and how my speech has changed over time.

After the last stuttering post, the predominant reaction I got from friends was either &…

The King's Speech (and me)

Tonight, I finally gathered the courage to watch The King's Speech. Why did I need courage to watch a movie, you might ask? The reason is both simple and intricately complex:

I'm a stutterer (Edit: person who stutters; "stutterer" is not who I am, but something that I do from time to time), and I have been for as long as I remember.

Well, there it is - I've said it. To be fair, I actually don't remember stuttering when I was little. My first very distinct memory of stuttering was sometime in seventh grade, when I had trouble saying "nosotros" (we/us) in Spanish class. But I also remember knowing I was going to have trouble saying it, because we were going around the room, and I counted ahead to see what I was going to have to say. Which means by that point I was already stuttering. When did it start? That's a question for another day.

So why am I publicizing this fact now? First, I'm in the midst of a lifelong attempt to "cure" my …