Ask HN: Start-up success as a non-technical?

<i>Would my money be better spent on a MBA or MSCS?</i><p>Neither.<p>1. Find someone who needs something.<p>2. Start building it.<p>3. Trust that when you need to learn something, you will.<p>The education you will receive this way will be way better than any formal education for multiple reasons. First, you will automatically triage your lessons; you will learn what you need, not what someone else (who probably doesn't know) thinks you need. Second, almost all the "data" you will need in this education is easily available and free. Third, for the education you need from other people, you will begin building a network you'll need anyway. And finally, this is exactly what you'll have to do <i>whether or not you get any more formal education</i>, so just skip the unnecessary step and get on with on. From your own self description, you already have way more formal education than you need.<p>This may not seem intuitive, but believe me, this is the way things get done in the real world of software development. At this point, the creme rises to the challenge regardless of education. Save your money for living expenses and start-up expenses. You'll probably need it. Best wishes!

I'm a civil engineering grad too (08). Started two companies, both are profitable and doing decently well (timesvr.com and gameventures.com). I don't write code myself (wish I could), but I've learnt a few things along the way. One of those things is that an MBA would be utterly useless.<p>I'm not good with long posts, and I'm sure you'll get plenty of solid advise here, but if you'd like to chat, email/IM me on alizaki (at) gmail.com

Note that my answer will be hugely biased, but then again so will everyone else's. ;)<p>Nonetheless, I'd say to go for the MSCS (or similar). You're looking for the networking potential of going back to school, and you want to start a start-up. In a technical master's program, you'll be around exactly the sort of people you need to meet for this to happen. In an MBA program, you'd network with a bunch of other business guys, many of whom wouldn't be interested in start-ups at all.<p>You'll obviously also gain a lot of truly valuable technical skills. You might not be able to single-handedly carry the technical side of a start-up by the end, but you'll definitely be able to make meaningful contributions and decisions about the technology. This helps your future partners as well, since they know you can contribute to the tech while working the business side.<p>If you're worried about missing out on the education side of the MBA, don't be. I think you could get a better version of an MBA education by just buying a pile of books [1] and starting a company. You'll learn everything you need about business along the way. And, as for the networking part of an MBA, you'll get way more interesting conversations out of "I'm running a start-up" vs. "I'm working on my business degree."<p>[1] Possibly a topic for another thread, but here's an example of such a reading list: <a href="http://personalmba.com/best-business-books/" rel="nofollow">http://personalmba.com/best-business-books/</a>

Take your money and move to the Valley. Network, join meetups, and tap into the community. Try to get into a startup that is founded by someone who has been successful in startups before. You will have to convince the founder you will do anything asked and then bust your ass. Don't expect a lot of money from a startup especially if you don't have the skills they need. If you are hungry and stay focused you will gain experience, knowledge, and the connections needed to do something on your own one day. My advice for you on going technical is only go this route if you truly enjoy technology, coding, etc. because you will be spending a lot of time on it. You can become a startup founder without technical skills but if your product\service is web based then find a technical partner.

I'm non-technical and co-founded a startup. I would never do it again without a technical co-founder or learning to code myself. So I'm learning Ruby. You can do a full-on MSCS from Stanford, or you can just teach yourself how to code, but that's the path I'd take - <i>and I'm going to business school to get an MBA in the fall</i>: <a href="http://www.sachinagarwal.com/why-this-startup-guy-is-going-back-to-busines" rel="nofollow">http://www.sachinagarwal.com/why-this-startup-guy-is-going-b...</a>

I think it matter on what interests you more... the business side, or technical side? Whatever is more interesting, start investing in it right now by learning and taking some risks.

It's not what you know, it's who you know. Invest in your network and everything else will fall into place.

I highly suggest going the technical route. Ask yourself this: would you prefer to be a software developer in a start-up (including your own), or a manager in a more established firm? If the only sort of management you see yourself doing is in <i>your own company</i>, I don't see an MBA as being very useful to you. You need to be some self-sufficient, meaning you should know how to code and not <i>just</i> how to manage. It's easier to bring in outside managerial talent to a purely technical firm rather than vice versa (I personally would <i>never</i> be the first programmer in someone else's company, many other hackers are similar).<p>You already have a strong background in a quantitative discipline (CEng). It means you'll have an easy time picking up either. Don't forget the advantage that this gives you. That means you'll have an easier time with statistics, mathematics and numerical analysis: this opens up a whole new world for you that's closed to many programmers who are only good at programming.<p>That being said, there's a lot you still have to learn. Start with learning C (you might not develop your application it, but a) you need to understand how physical memory works in order to be a programmer b) C is the lingua franca of programming languages which means you'll have no problems learning whatever <i>other</i> language is better for the task at hand), then learn algorithms and data structures and at least three of (compilers, operating systems, databases, computer networking). Then specialize: machine learning/NLP/IR (given your "real engineering" background, you might have an easier time here than most programmers), further into systems, further into databases, etc...<p>That's a multi-year project and you have to be ready for it. Don't under-estimate the value of experience (by experience I mean working in firms whose product is software i.e., <i>not</i> consulting or internal IT development) in doing a start-up: it's possible to start without "having done it before", but several years of work experience (alongside people much smarter and more experienced than you) is extremely useful. Experienced developers have a huge role to play in a start-up: partly by making it possible for apt junior developers to be recruited (they want to work alongside "hard core" hackers) and mentored.<p>If you join a start-up, it's also a chance to be exposed to the "business side" as well -- although certain types of established firms (in my experience, those who build software for other developers) will give you exposure to customers and sales/support cycle as a developer too.<p>If you prefer a more structured environment in which to learn (as do I -- there is absolutely nothing wrong with that), an MSCS will serve you well. It's also a chance to meet hackers, show your "worth" to them (they'll have collaborated on lab projects with you) and make connections without looking like a "shmoozer". It will also give you credentials for employment (getting initial experience), although I'd have zero hesitation in hiring a self-taught hacker with a degree in Civil Eng (software development is really an engineering discipline rather than a science).

My strong bias is towards getting the technical background.<p>If you have that, partnering with more technical people is a lot more likely to work, otherwise the only possible posture that works is blind trust, which most people aren't capable of.<p>However this is coming from the son of a businessman who started reading his <i>Wall Street Journal</i> in 3rd grade, so I've found partnering with business people to be easy (amusingly, in many of the startups I've worked for I've helped the point man procuring office space, since unless you have a background in that area you e.g. have no idea how slow the real estate clock cycle is).<p>To finish, when you think of the historical hardware and software long term superstars many if not most were founded and lead by at least one person with serious technical chops, perhaps even uber-salesman Larry Ellison of Oracle.<p>Obvious examples are Bill Gates, Jeff Bezos of Amazon, the founders of Google and the Chairman/CEO they picked, Ken Olsen of DEC, H&#38;P of HP and I'm sure I'm forgetting many others.<p>Tom Watson, Jr., who saved IBM with his massively successful push into computers, is the most famous exception to this pattern ... but seeing that he grew up in the predecessor punched card industry and undoubtedly absorbed a lot of technical stuff including most especially attitudes he's got to be a special case.<p>As you probably know, the list of technical companies ruined by non-techie leaders is nearly infinite, but it's balanced at least in part by techies not getting the business side of things. Can any of you think of major counterexamples of complete non-techies who massively succeeded over a long term, including retaining their initial key technical people?<p>Steve Jobs is the only one I can think of off the top of my head (and he fails the retention test, e.g. he burned out the Macintosh development team, didn't he?) but he clearly has unique relevant design talents that make him a special case.