The best resource is a PARTNER. Get a buddy, don't do it alone, mate.
And how did you guys find partners on your first projects?
21–30 of 39 posts
The best resource is a PARTNER. Get a buddy, don't do it alone, mate.
And how did you guys find partners on your first projects?
http://binarycake.com/
Binary Cake is probably a viable resource for the OP, so I'm unsure as to why you were modded down. Can anyone comment on the quality of these casts? They'd be good to point people at in the future if they are worth the money, especially if the founders are news.yc people :)
I won't tell you what to do, because I'm still quite inexperienced and other advice in this thread will likely be far more valuable, but what I've done is purchased a cheap slice @ slicehost.com. I taught myself to work with Unix, setup apache/nginx, php, mysql, perl, python, ruby and so forth, fiddle with the internal settings. Then you start learning how these things interact with each other.
I then suggest installing something like Kohana, which is a fantastic PHP framework. By working inside a framework you are forced into good habits.
PHP, HTML and CSS should come first, in my opinion. Once you have the basics of these there, start implementing some fun Jquery and making a small site that's database-driven. All of a sudden you're using 5+ technologies, and from hereon out you'll learn things as you go.
*Edit: feel free to drop me a line if you want to chat some more! woodsier at gmail
Our startups actually work in some of the area that you described (haven't launched yet).
But, i agree with other comments, research around ...most of the time, it won't be unique. But, you'll learn more and more as you do more iteration of releases.
http://binarycake.com/
Binary Cake is probably a viable resource for the OP, so I'm unsure as to why you were modded down. Can anyone comment on the quality of these casts? They'd be good to point people at in the future if they are worth the money, especially if the founders are news.yc people :)
"Usually I spend it reading all sorts of ebooks and papers and trying to learn new skills." I suggest you switch gears and spend your free-time coding :-). Pick some technology you think you want (you can change your mind later) and start doing side projects in it. Do up your personal home page. Make a google maps mashup. Some stuff to familiarize yourself with the technology. There have already been lots of good sug…
I made this mistake for about a year. Ordered/downloaded tons of books, read published papers, etc. I learned a fair bit, but honestly you don't really learn until you start doing. Your return per hour spent coding is on average far higher than your return from books and papers. You shouldn't stop reading, it just has to be limited.
1) Learn the syntax/guts of a tool by going through a book, tutorial and trying trivial examples.
2) Work until I run into a problem. (How do I make merb-auth work with a flash uploader?)
3) Find examples/read a book/look at API docs until I figure it out. (Ohhh, you write a Rake middleware to handle it!)
4) Goto 2.
So reading materials are important, but I usually use them to solve real problems. There's no part of this process that doesn't involve writing code.
Javascript: Start with Douglas Crockfords "Javascript: The Good Parts". Excellent, terse primer on safe Javascript development. Startups: Read content by people like Peter Graham, Joel Spolsky, Rob Walling, Guy Kawasaki, Bob Walsh, Andy Brice - just to mention a few of my personal faves. Skim around, there's lots of great free content out there on software startups!