You are asking “how to market a product, ” or maybe more specifically “how to launch a product.” It’s a big question: -) But to simplify I’d* post a “please review my project” on Hacker News and developers.org.ua forum* advertise on AdWords/Yandex* hire a PR company and/or learn everything about doing PR yourself. Google "how to launch a product"Realistically, you goal is just to get some users who can give you initial feedback. Do it by any means, it will get you to the next step.
These 3 I mentioned in the interview. They are mandatory business reading in Acunote: * Claude C Hopkins “Scientific Advertising” (en.wikipedia.org/...ki/Scientific_Advertising) and “My Live in Advertising”* Perry Marshall “The Definitive Guide to Google Adwords” (www.perrymarshall.com/adwords/) * Steve Blank “The Four Steps to the Epiphany” (www.amazon.com/...teven-Blank/dp/0976470705) CS textbooks I kept after college: * K& R “C Programming Language (2nd Edition) ” (www.amazon.com/...n-Kernighan/dp/0131103628/) * Al Aho and Jeff Ullman “Foundations of Computer Science” (infolab.stanford.edu/~ullman/focs.html). Now free. We used this for first 2 CS theory classes.* Stuart Russell and Peter Norvig “Artificial Intelligence: A Modern Approach” (www.amazon.com/...pproach-3rd/dp/0136042597) My current favorite fiction: * John Ringo “Ghost” series (www.amazon.com/...dows-Book-1/dp/1416520872/) Large engineering projects classics: * Fred Brooks “The Mythical Man-Month” (http://www.amazon.com/Mythical...) * Pascal G. Zachary “Showstopper! ” (http://www.amazon.com/Showstop.../)
No, on my list now. It does remind me that “Founders at Work” is excellent.
This is a great post. I’ll add http://cs.stanford.edu/courses/. Also, Stanford has been recording their CS classes for ages, and selling them to Silicon Valley companies. Meaning, you need to login to get to them and they won’t get you watch them for free: — (But all the other course materials can be easily found.
motus: 6.001 looks super cool. MIT is known for their emphasis on LISP and that’s a good thing. Teaching first CS class in LISP takes balls: -) Talk about a weed-out class. I really wish they’d had us do more LISP/Scheme in Stanford.roddyb: I couldn’t agree more that the CS education should result in practical trade knowledge in addition to solid theoretical foundation. Fortuntely, the two are complimentary, and for introductory classes should be taught at the same time. Relational database class is a great example, see: http://infolab.stanford.edu/~w.../It’s not even a hard class — you learn a bit of relational algebra, solve some problems, write the same problems in SQL, repeat. It shouldn’t be hard, there are no big programming assignments, just some toy projects and theoretical exercises. The main point of the class is to train the student to think in relational terms, and give him a good overview of all the various things related to the field so he’ll know that this information exists and will be able to find it when he needs it later.
roddyb: I think what you are looking for are project classes. Let me explain. Some CS classes require you to do massive amount of coding, and grades for the programming projects are a major part of your grade for the class. They are known as “project classes”. The coding workload probably averages out to about 20 hours/week, but it’s not evenly split, so many weeks you’ll spend 40 (or much more) hours on it. It’s foolish to take more than one of these during the same quarter (I’ve tried: -).Stanford’s “official OOP” class is cs108: http://www.stanford.edu/class/.../ It’s basically about writing tons of code for GUI apps. Back in my days we used C++ on Macs, these days it’s, appropriately, Java. Students usually take this class their second year. There are a few things that happened in this class: * I wrote tons of code, and got a better in C++ coding* I got a general idea of writing UI code* We did the final project as group (3 people). I learned that getting together the night before the assignment to try to integrate 3 weeks of 3 person’s coding is not a good idea. The final project was called Bunny World, it’s still a bit painful to remember: -) * Oh, and we got a good feel for that whole OOP thingThe theoretical part of the class was pretty simple — OOP is not exactly a science, there is not that much theory to teach there. But whatever theory we did learn, we got to immediately apply while writing code. That’s the way it should be.There is a subtle but important thing about these project classes. You are not working on real-life projects, instead you get stub code/hints/well-defined assignments etc. That actually lets you cover whole bunch of stuff in one class, rather than getting bogged down setting up Makefiles, creating test data, etc.
If you want to use this kind of code review yourself right now, you can try Acunote. See code inspection demo @ http://acunote.com/tour/code_i.... Acunote supports SVN (over http or https) and Perforce. You just point it to your repository, and voila you can do in-line inspections of all the changesets.
No period at the end: http://acunote.com/tour/code_i...
Another coined name generator: http://www.makewords.com/