Totally agree with this. Feedback is the most important thing. I think the principle of this is simply to get out of your comfort zone, which may mean rejection (which may mean a learning opportunity).
Great point. It'd be interesting to be transparent about rings of people who frequently upvote on the same post. I'm sure they have that info. It might actually be interesting and open up some level of transparency -- whether among the YC companies (and the ability of their job posts to somehow make it to the top) or among other subsets of the coding community like node.js I have nothing against YC companies; I'm friends with lots. I have nothing against promoting a link you post on HN.
Totally agree. It is a great example of design. Design today is thrown around as something that looks almost Ikea-esque. But in actuality design is the user experience. Design is being thoughtful about the full process associated with a product. They thought of everything.
I tried to get their email addresses as well, but never found it... Hmm. I'll mention this to them. I know a couple of them have personal blogs with personal email addresses -- not necessarily connected to the firm.
family is definitely the most important thing... and without family support is is incredibly hard to start something. best of luck Marc -- you know I'm rooting for you and your love of starting something great
Ed... I don't know you, but as another hard working person, I can honestly say that your post has reminded me of what is important in life. It's those that love me who support my hard work and sometimes reclusiveness/introverted-ness.
Thank you for posting this. Your mother's story has had a compounded effect with your post. Her legacy lives on, and this is just one way: inspiring others on HN to cherish those who love them, which she obviously did with you.
Please vote, this is what I am doing after college. No real job :) http://markover.nodejitsu.com/
Contextual real time commentary that works on NYTimes and other news sites!
Interesting read especially for someone who is still in undergrad.
One thing strikes me though:
"though I suspect the brand cache of an MBA program will be longer lasting"
I disagree. This is the modern industrial age. This is the time when 20 years from now, history books will look back and talk about the Carnegie and Rockefellers of our time.
And when grade school kids are memorizing facts about important figures, Techstars and YC are going to be two of their vocabulary words. It will be the first time those schools of thought appear -- HBS will still always have a great reputation and its own prestige, but in the long term, the brand cache of TechStars and YC will leave a different, more unique mark in history.
#justsayin :)
Github is to coders what an online portfolio/web presence is for designers. Look at the design industry... corporate designers and grads and freelancers used to all have a hard copy, artfully crafted portfolio on sensual-to-touch paper stock.
That's gone. And no one cared if the corporate designers didn't have time to create a website. Even if you still have an amazing portfolio (which is the resume for the designer), you better have something online (whether they are personal projects done outside of work, or glimpses of projects done at work).
The paper resume is going away anyway. And then when HR finally gets up with the times, do you really think they are going to say, "Aww, it's ok, we understand you didn't get on Github because you were waiting for us..." No.
HR people hiring designers using their online portfolio is a lagging indicator. And the same will go for HR people hiring developers based on Github.
Right now, we don't even have a target audience :) hah. I agree about the issue with the enter/button.
We were going to have the marks load but be hidden in default and then users could change the setting to one or the other either universally or with each image.
We definitely will be limiting number of marks. Actually, in the long term the marks/feedback etc will be more curated based on latent semantic indexing of comments/content (once we move into text, etc) and a variable assigned to the commenter (or marker) based on number of similar projects having commented on. More here: http://kelseyfalter.posterous.com/stop-posting-start-reactin...
Ps. Thanks for your input! You really have no idea how much I appreciate it.
I agree... this may hurt/help Google group making. Either people will add non-contributors to a group and get bored with others' lack of contribution, and by extention Google circles. (To combat this, it'd be great if Google helped curate or edit circles, like with listservs. Non-content posters would be flagged for me and I could opt into auto-removing non-contributors or just being notified that they are diluting my circle.)
Or, it will result in better curated lists of people -- similar to twitter, where you really only want to follow someone (and up your following count) based on the quality of their content.
The Circles idea would be good if it auto generated people who should be included in Circles based on use patterns(mentioned here "It is a shame that there aren't any recommendations for people that ought to be grouped together automatically into a common Circle.")
It wouldn't be creepy if the interface picked up on behavior similar to how Gmail suggests people to cc on emails based on past email use patterns. People are ready for that.