5 ms·

My vote is for the learn to code approach.

AlexeyMK 15y ago
As a Computer Science TA (and author of this post), I'm just not sure learning to code is a one-size-fits-all approach. Some of my favorite founders (Evan Reas at LAL, Joe Cohen at Coursekit) are not technical, and it's just not their thing. It remains to be seen whether things like Codecademy are going to open the possibility of coding for more people, but still - to each their own.
- Hrothgar15 15y ago
  This is exactly right. People don't choose their passions; their passions choose them. Specialization is a Good Thing.
  - zsherman 15y ago
    Fair enough, Steve Jobs serves as a prime example for this. Wozniak was a far better engineer than Jobs. I guess I should have elaborated, you don't need to be a coding ninja to run a startup but I do honestly feel that a solid understanding of coding and computer systems is essential for any tech entrepreneur.
    - inuhj 15y ago
      Steve Jobs could code. He was a technical founder.
      - coderdude 15y ago
        Can you show me where that's written somewhere? I never heard Steve Jobs coded and his Wikipedia page doesn't seem to mention it.
        damoncali 15y ago
        Woz's book describes a fairly technically involved young Steve Jobs back in the day. I can't recall if it was code exactly, but deep into technology. Not your stereotypical "sales and marketing" guy.
        inuhj 15y ago
        Jobs had a hand in making event loops standard programming fare, and was there when Apple and NeXT pushed languages such as Objective-C and Dylan and various software frameworks, and decided to cease supporting others. - http://lambda-the-ultimate.org/node/4372 http://lambda-the-ultimate.org/node/4372 I can't find the link but I also read about Jobs going on a tirade to his employees about some aspect of Objective-C while at Apple. Another case supporting him as a technical cofounder(although not a programmer) is when he worked at Atari on 'Breakout'. From wikipedia: "The same year, Alcorn assigned Steve Jobs to design a prototype. Jobs was offered US$750, with an extra $100 each time a chip was eliminated from the prospected design. Jobs promised to complete a prototype within four days. Jobs noticed his friend Steve Wozniak—employee of Hewlett-Packard—was capable of producing designs with a small number of chips, and invited him to work on the hardware." Jobs may not have done the job himself but he was clearly working in a technical position at the time.
DanielRibeiro 15y ago
Founders new to coding write horrible code. And that is ok! At the beginning the biggest risk is not writting terrible code you will regreat having written, let alone give maintance. The biggest risk is making something nobody wants. From my experience, the biggest issue comes after you get enough traction/money/funding to hire a team. This is where things can get really bad, when the founder thinks he actually knows how to solve CS problems, and says things like: "This Machine Learning thing is not that hard: I wrote the landing page for the startup in 3 hours without any programming knowledge". Hubris is one dangerous trait that will get anyone in trouble. Founders, due to their natural Reality Distortion Field[1], can be a victim of it[2]. Kent Beck, creator the agile methodology XP, discussed some of this in his The Flight of a Startup[3] [1] http://www.startuplessonslearned.com/2010/09/visionarys-lament.html http://www.startuplessonslearned.com/2010/09/visionarys-lame... [2] http://blog.paulbiggar.com/archive/why-we-shut-newstilt-down/ http://blog.paulbiggar.com/archive/why-we-shut-newstilt-down... [3] http://www.threeriversinstitute.org/blog/?p=251 http://www.threeriversinstitute.org/blog/?p=251

As a Computer Science TA (and author of this post), I'm just not sure learning to code is a one-size-fits-all approach. Some of my favorite founders (Evan Reas at LAL, Joe Cohen at Coursekit) are not technical, and it's just not their thing. It remains to be seen whether things like Codecademy are going to open the possibility of coding for more people, but still - to each their own.

Hrothgar15 15y ago
This is exactly right. People don't choose their passions; their passions choose them. Specialization is a Good Thing.
- zsherman 15y ago
  Fair enough, Steve Jobs serves as a prime example for this. Wozniak was a far better engineer than Jobs. I guess I should have elaborated, you don't need to be a coding ninja to run a startup but I do honestly feel that a solid understanding of coding and computer systems is essential for any tech entrepreneur.
  - inuhj 15y ago
    Steve Jobs could code. He was a technical founder.
    - coderdude 15y ago
      Can you show me where that's written somewhere? I never heard Steve Jobs coded and his Wikipedia page doesn't seem to mention it.
      - damoncali 15y ago
        Woz's book describes a fairly technically involved young Steve Jobs back in the day. I can't recall if it was code exactly, but deep into technology. Not your stereotypical "sales and marketing" guy.
      - inuhj 15y ago
        Jobs had a hand in making event loops standard programming fare, and was there when Apple and NeXT pushed languages such as Objective-C and Dylan and various software frameworks, and decided to cease supporting others. - http://lambda-the-ultimate.org/node/4372 http://lambda-the-ultimate.org/node/4372 I can't find the link but I also read about Jobs going on a tirade to his employees about some aspect of Objective-C while at Apple. Another case supporting him as a technical cofounder(although not a programmer) is when he worked at Atari on 'Breakout'. From wikipedia: "The same year, Alcorn assigned Steve Jobs to design a prototype. Jobs was offered US$750, with an extra $100 each time a chip was eliminated from the prospected design. Jobs promised to complete a prototype within four days. Jobs noticed his friend Steve Wozniak—employee of Hewlett-Packard—was capable of producing designs with a small number of chips, and invited him to work on the hardware." Jobs may not have done the job himself but he was clearly working in a technical position at the time.

DanielRibeiro 15y ago

Founders new to coding write horrible code. And that is ok! At the beginning the biggest risk is not writting terrible code you will regreat having written, let alone give maintance. The biggest risk is making something nobody wants. From my experience, the biggest issue comes after you get enough traction/money/funding to hire a team. This is where things can get really bad, when the founder thinks he actually knows how to solve CS problems, and says things like: "This Machine Learning thing is not that hard: I wrote the landing page for the startup in 3 hours without any programming knowledge". Hubris is one dangerous trait that will get anyone in trouble. Founders, due to their natural Reality Distortion Field[1], can be a victim of it[2]. Kent Beck, creator the agile methodology XP, discussed some of this in his The Flight of a Startup[3] [1] http://www.startuplessonslearned.com/2010/09/visionarys-lament.html http://www.startuplessonslearned.com/2010/09/visionarys-lame... [2] http://blog.paulbiggar.com/archive/why-we-shut-newstilt-down/ http://blog.paulbiggar.com/archive/why-we-shut-newstilt-down... [3] http://www.threeriversinstitute.org/blog/?p=251 http://www.threeriversinstitute.org/blog/?p=251