Hacker News new | past | comments | ask | show | jobs | submit | conventionalmem's comments login

But there may be a larger market to hire people who know how to use the tools they design.


The caveat is that in the long term, ML systems are generalized systems that function independently and won't necessarily always remain in the form of an "API tool" that traditional programmers will interface with.


I thought about that as well. I think it may be defensiveness and anger - rather than a logical statement. Those feelings are natural, so I don't fault him - but at the same time, rejection is a part of startups at every turn and I think we have to get over it, and figure out how to use criticism constructively.

YC has always valued persistence - so I'm sad that he applied and wrote that, since he might have been able to get in the next time, and I think YC likely would have helped his ability to recruit and valuation, especially given the changing markets. But regardless, I always have respect for startup founders (esp after 3 years of hard work) - so we should all wish his team luck.


This guy not only tells people not to YC after he applied and got rejected, but also publicly bashes someone (the LA accelerator) who did their best to help him (Doesn't matter if it didn't work out. They did their best to help their portfolio companies and this guy says it was a "gimmick") I wouldn't like to work with this guy


Hard to use that to say he's not a great person to work with. The LA accelerator might have been egregious, and he may be doing a service to other entrepreneurs by publicizing it (there are a lot of incubators today, and entrepreneurs should beware). I do hope in the LA incubator's case that he gave actionable feedback privately long ago.

I totally agree on the cognitive dissonance with bashing YC and saying to never to do it, after getting rejected recently. But I can realize how it might not be a fully rational perspective (he'd probably argue that he's more educated now, and that's why he's changed his mind since applying - my gut is there's some emotions involved, since I can't see a ton of benefit to him to write this so publicly).


Posted this on his comment form:

Karthik, disclosure, I was a YC founder.

It doesn’t seem very thoughtful to say never pay more than 3%, full stop. If you get more than 3% value out of the incubator, it’s often a good idea to pay more than 3%. You should make the decision after talking to many people who’ve chosen the incubator, and there are many companies that will say they got much more than 7% benefit out of YC – and also companies that didn’t.

It’d be great if every incubator charges much less than they do today, but I’m doubtful it’s a perfectly competitive market, with stickiness in things like alumni networks and reputation (it does seem like it has some similarities to the education market). Entrepreneurs would obviously benefit from more competition amongst incubators – and maybe you’re right that change is at hand.

I’m sorry that you didn’t get in to YC specifically (and maybe it wasn’t the right idea to apply, if you felt so strongly about how incubators provided so little value) – but I hope you won’t let your disappointment and anger get in the way of thoughtful business decisions, including in cases like future customer rejections.

Anyway, back to building our businesses – good luck with your own!


Agreed, it's crazy that there are engineers in this world that can make blanket statements like this, especially on a site like HN.

There are a lot of great languages/frameworks, and it depends on the needs you have and your team.

(I'm so fatigued by this view I hear so regularly expressed in web dev that "X is the solution to everything" - no, it's very rarely the case)


I'm more fatigued by the constant "use the right tool for the job" - impossible to argue with, and utterly useless advice for actually making decisions. Some tools really are better than others, and there is a lot of value in standardizing on a single platform. http://www.teamten.com/lawrence/writings/java-for-everything...


Sure, but let's have that debate, and set down a philosophy around that. What you're arguing is not that Java is everything - but that a polyglot stack has dangers, that certain tools are often unobjectably better than others, and that we shouldn't sugar coat that. I agree, as would many of our friends in the space.

But if you're saying that everyone who is in Javascript, Ruby, Python, Go, PHP (and others) should all refactor into Java because it's the one and only ideal web backend in 2016 (or design new apps exclusively in Java) - I could pick a 1000 holes in that argument. The original comment I reacted to was:

> If you're not picking the JVM in 2016 to build your core services and web applications then you're making a mistake

My apologies if this comes across negatively (which I don't intend, as this is a respectful debate among people who care deeply about their craft) - but I'm just not convinced that you're really a full supporter of the original commenter. Your blog seems to show a fair degree of pragmatism (you consider other languages/frameworks, might use them, are ok if your friends are not using Java). I'm totally fine with "I think the majority of people should use Java" (I don't fully agree with that, but in a world where many people knew that ecosystem, I think it's a great choice) - but the commenter went much further. If s/he is looking to start a debate, then I'm fine; if that person would join any company and religiously uphold that viewpoint, I don't think they'd be the right person for many companies.

P.S. If I'm wrong, and if Java is the ecosystem that for the next few years the rules them all, I really want to make a Lord of the Rings-inspired meme about it


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: