529 karma · joined July 5, 2007
I've seen a lot of discussion around asking users for their login credentials just for their email (see this recent YC posting for example: http://news.ycombinator.com/item?id=55660), and this is obviously more extreme than that.
Also, the stats could be useful. I never use it unless I specifically want to talk to someone, and that would be nice to know when I could expect to find them online.
I will hold you to that. I have a question for you right now actually. Are there any tech skills you wish you had learned, but so far have not?
But I don't think there is any karma whoring going on. I think PG articles come with a pretty safe bet of being a good read. Whereas you aren't sure what you are going to get with the others. Im assuming pretty much everyone reads the PG essays, and thus there is more discussion to be had. Whereas I would like to know the proportion of people who read all the other links submitted, as opposed to just their titles.
The whole time I was going to school I was super impatient to get done so I could actually get working on something real. I was really just after the piece of paper they give you at the end (though I never attended my graduation to get that paper, and the original was sent to the wrong house).
Once I graduated I started my own project so that I would have some work to show when applying for jobs. I found that that experience led to as much or more knowledge gained as my best year in school. And that is not a knock against the school I went to (I thought the staff there was awesome).
I am always reminded of a quote from some movie (cant think of the name of it now)... "You spent x thousands of dollars on an education you could have got for 2 dollars in library late fees"
"The great thing about surviving a storm is that you're much better prepared the next time the winds start kicking up. You recognize the early warnings. You stock up on essentials. And, most crucial, you go in knowing that no matter what happens, you can always rebuild.",
"Because I'd failed, I wasn't afraid of failing. And that enabled me to push a lot harder for what I believed in.",
"Given all these risks, why do it? Because even in failure, I knew I'd grow from it. ",
"It's just like weight training, really. You push yourself until your muscles fail. That's how you grow stronger."
A CMS is good to get you kick started, after all who wants to build another boring login script? But if you are serious about your app, I think you have to roll your own. Simply because with any set of code provided for general use, it will never fit perfectly to your needs. And I think it is that extra bit of perfection, the 'icing on the cake' that makes your app special and stand out. It is much harder to accomplish that using someone else's code than writing your own specifically for your own purposes.
Cal Henderson in his excellent book 'Building Scalable Websites' mentions writing his own file transfer protocol for a middle-ware file storage system. His reason was that it was custom made for Flickr's needs and thus was faster than anything available.
A quote I heard somewhere about Catering Fake, when asked what tools she recommended to build a web app, she responded 'PHP' (in other words, she suggested using no tools, and to build your own).
"How To Get Rich" by Felix Dennis is another good read related to what Godin is saying. He is in the magazine business, and recommends anyone looking to start something to start it in a growing industry not already entrenched with leaders. "Ride the wave" is his suggestion
A side note, the book Founders At Work is an awesome read!