domain knowledge can certainly be helpful. whether the cs degree is useful depends on the domain. if you just need to put together a web application for a biome

domain knowledge can certainly be helpful. whether the cs degree is useful depends on the domain. if you just need to put together a web application for a biomedical device your building, or need to do some complicated matlab analysis, then independent study is all you need to get those skills. heck, i didn't learn about web technology until after i had my bachelors. if you're solving a science of computers problem, like algorithms or systems stuff, then maybe a computer science degree is mad helpful. sometimes the technology is the software. (eg, guided navigation ecommerce, airplane optimizing websites) sometimes i rail against college because "i didn't learn how to build anything until i graduated and started working on projects all the time." actually, though, college taught me a reach history behind the science and systems of computers, and how to think. it's like the difference between teaching yourself arithmetic to work at a checkout counter versus creating elegant proofs. there's a cap on how far the former will really get you. it took me a couple years after getting the bachelors to really master building stuff (more so i feel that i get better every month). but now that i feel leaps and bounds ahead of where other people level off. being a "good" programmer actually saves enormous amounts of time after the prototype hackery. there are other advantages, too, such as promoting collaboration and fun. the idea that an entrepreneur just needs a hacky program and that once they get funding they'll redo it doesn't make sense. more often one needs to make a real program (or site) and bootstrap things at least to show profitability and execution. i don't see twitter as the exception to this rule because scaling is not the only component of good programming. but even so, i'm sure exceptions exist (ebay?). my main point is that i feel like an entrepreneur in my soul and i love programming, but in a very definite science and systems way. a computer science degree was awesome. i also have a masters of engineering in computer science. it was a necessary step in my path to mastery (still ongoing). i don't love another domain so i can't really speak to how well the two-at-once or one-after-the-other thing works. most domain specific folks i know are way better off with a solid developer on their team. i love working with domain-specific folks who are passionate about the domain and charismatic enough to be the outreach and business side of the team. just trying to add another side to the picture. there's a place for all combinations of skills; i've filled quite a few as my skills change and develop over time.