Live data from Hacker News

YC startups that are hiring

triplebyte.com

61–70 of 78 posts

Re: YC startups that are hiring

#61

Earlier quoted context omitted.

How would you design an interview process ?

The evidence simply does not support present hiring methodologies as predictive of successful business outcomes. Therefore, you should hire and invest in people who need jobs. The reason the increasingly widely accepted status quo of interview processes continues is essentially due to confirmation bias: companies want you to feel like you are part of a special, select team. In reality, we are not that much different…

Where is the evidence that present hiring methodologies don't predict successful business outcomes? I recall seeing evidence re: resumes, but not on the overall process itself [1].

If this data is present (data showing that present hiring methodologies don't predict successful business outcomes), do you have data showing that hiring people who need jobs is any better? We /are/ different from each other -- as an example so obvious it borders on the ridiculous, people who have been programming for ten years will be much faster at it than people who haven't. At what point do you draw the line to state that people stop being different? If so, what data did you use to draw that line?

[1] http://blog.alinelerner.com/resumes-suck-heres-the-data/

Re: YC startups that are hiring

#62

Earlier quoted context omitted.

The evidence simply does not support present hiring methodologies as predictive of successful business outcomes. Therefore, you should hire and invest in people who need jobs. The reason the increasingly widely accepted status quo of interview processes continues is essentially due to confirmation bias: companies want you to feel like you are part of a special, select team. In reality, we are not that much different…

Where is the evidence that present hiring methodologies don't predict successful business outcomes? I recall seeing evidence re: resumes, but not on the overall process itself [1]. If this data is present (data showing that present hiring methodologies don't predict successful business outcomes), do you have data showing that hiring people who need jobs is any better? We /are/ different from each other -- as an examp…

Just one instance. https://twitter.com/mxcl/status/608682016205344768 , I've seen hundreds like this.

Re: YC startups that are hiring

#63

Earlier quoted context omitted.

The evidence simply does not support present hiring methodologies as predictive of successful business outcomes. Therefore, you should hire and invest in people who need jobs. The reason the increasingly widely accepted status quo of interview processes continues is essentially due to confirmation bias: companies want you to feel like you are part of a special, select team. In reality, we are not that much different…

Where is the evidence that present hiring methodologies don't predict successful business outcomes? I recall seeing evidence re: resumes, but not on the overall process itself [1]. If this data is present (data showing that present hiring methodologies don't predict successful business outcomes), do you have data showing that hiring people who need jobs is any better? We /are/ different from each other -- as an examp…

I understand the paradigm paralysis - we have been led to believe that having the best CS zombies in the world is what makes success, but it's just not true. Meanwhile, jobs aren't filled and the people who need them are suffering.

Re: YC startups that are hiring

#64
post #25

Earlier quoted context omitted.

I wrote C# for 8 years, but switched to Ruby after following an my boss to a new startup that is using Ruby. I advocated for years about how great .net is (and the tools still are the best), but if i'm being honest here. Ruby really is a lot quicker for prototyping. It's the perfect fit for startups.

Can you elaborate on the benefits of using ruby for prototyping? What's easier to do in ruby?

Getting runtime errors.

But seriously if you want something quicker than c# for prototyping just switch to F#. Ruby has only downsides.

Re: YC startups that are hiring

#65
post #47

Earlier quoted context omitted.

Microsoft's technology stack doesn't seem to be popular with startups and young technology companies, but I don't think that's because of .net itself, but rather because of the barriers presented by the rest of the Microsoft stack. Probably a major driver is the various virtualization and cloud-driven technologies not fitting real well with Microsoft's server environment. Startups want scalable architectures that all…

>If Microsoft did offer something in that arena, I'd expect the licensing costs to be obnoxious. Nope. First, both AWS and Azure offer Windows hosting. Second, licensing costs on AWS are around 30% markup on top of same Linux hardware. Hardly "obnoxious".

And .net runs on linux with mono or the new .net core plus its open source.

Re: YC startups that are hiring

#66

Earlier quoted context omitted.

Where is the evidence that present hiring methodologies don't predict successful business outcomes? I recall seeing evidence re: resumes, but not on the overall process itself [1]. If this data is present (data showing that present hiring methodologies don't predict successful business outcomes), do you have data showing that hiring people who need jobs is any better? We /are/ different from each other -- as an examp…

Just one instance. https://twitter.com/mxcl/status/608682016205344768 , I've seen hundreds like this.

Honestly, if you weren't in the room you can't tell what happened. It's just as likely that he wasn't a good culture fit.

Re: YC startups that are hiring

#67

Earlier quoted context omitted.

Just one instance. https://twitter.com/mxcl/status/608682016205344768 , I've seen hundreds like this.

Honestly, if you weren't in the room you can't tell what happened. It's just as likely that he wasn't a good culture fit.

"Cultural fit" - I forgot this term existed outside of the HBO television show "Silicon Valley".

Re: YC startups that are hiring

#68
post #12

Earlier quoted context omitted.

Licensing fees and tech made for large slow enterprise teams. I've seen the shops that have C# or Java as their backend and they move too slow to be a competitive threat. If their frontend is written in Ruby/Rails or Python/Django then maybe they have a chance against the competition but usually they'll be held back by the slow progress made on the backend. For some reason the big slow enterprise mindset gets transmi…

I work at a small company writing NLP R&D software. Our core in-house codebase is entirely Java. There is no "enterprise mindset" here; in fact, many of the engineers make fun of that mindset. Choice of language only affects your culture if you believe choice of language affects your culture and let it happen.

> Choice of language only affects your culture if you believe choice of language affects your culture and let it happen.

I would disagree with that. I just came from a startup on .NET. The develop/build/test/deploy cycles were really slow (mostly due to tooling/infra, not the language), which meant devs didn't ship frequently and didn't test their code much. That affected the culture quite a bit: no rapid experimentation means no hacker mentality.

It may be that you can develop rapidly with C# or Java (I just wouldn't know, I haven't ever used either in a highly-productive environment) but if they hold you back from shipping quickly, they hold you back from the hacker/startup mentality.

Re: YC startups that are hiring

#70
post #25
post #2

Not that it matters that much but I notice there's no .NET or C# on the "Technology Used" list. Is there really not a single YC company that uses the .NET stack? I'm not surprised that there's a strong bias toward open source technologies among these companies, but given how widely .NET used elsewhere in the enterprise world I find it pretty remarkable NONE of those companies decided to go with a MS stack.

I wrote C# for 8 years, but switched to Ruby after following an my boss to a new startup that is using Ruby. I advocated for years about how great .net is (and the tools still are the best), but if i'm being honest here. Ruby really is a lot quicker for prototyping. It's the perfect fit for startups.

OT: Do give Elixir a try. It's like am erlang with ruby syntax.
Post reply on HN