Live data from Hacker News

We Only Hire the Trendiest (2016)

danluu.com

51–60 of 420 posts

Re: We Only Hire the Trendiest (2016)

#51
post #7

I worked on a big C# system with hundreds of windows servers, developed on Visual Studio etc. It was an awesome project and everything worked like clockwork. However there are very few projects using that technology so when I wanted to move I had trouble getting interviews. I'm now working with a very fashionable tech stack, its horrible, infrastructure is regularly broken, people can't trace problems easily, our fun…

That's awesome - understand the game and play it...and make your money doing it. Stroked egos sign paychecks!

Re: We Only Hire the Trendiest (2016)

#52
post #3

>When I started programming, I heard a lot about how programmers are down to earth, not like those elitist folks who have uniforms involving suits and ties. You can even wear t-shirts to work! But if you think programmers aren't elitist, try wearing a suit and tie to an interview sometime. Indeed: http://web.archive.org/web/20140618142018/http://blog.42floo...

I hate the anti-suit thing in SV. Suits look great, you feel great wearing a good tailored suit, and honestly with so many engineers wearing the "unicorn uniform" of Supreme and Common Projects, it's not like they can't afford a suit anyways.

Re: We Only Hire the Trendiest (2016)

#53
post #3

>When I started programming, I heard a lot about how programmers are down to earth, not like those elitist folks who have uniforms involving suits and ties. You can even wear t-shirts to work! But if you think programmers aren't elitist, try wearing a suit and tie to an interview sometime. Indeed: http://web.archive.org/web/20140618142018/http://blog.42floo...

From your link: "go-out-for-a-beer test"

I am sure this is not a literal "going out for a beer", but still it bothers me that it exists and is called that way. I am 40yo (still junior though as I started learning to code at 37) and I don't drink.

I like to work on startups because I like to be generalist and solve problems that impact the fate of the company. So I always work with a lot of young people that like to go out. It is always a mismatch that I rarely go out with the team, and sad that this "go-out-for-q-beer test" is considered normal in some places.

Re: We Only Hire the Trendiest (2016)

#54
post #5

Earlier quoted context omitted.

My university's career coaching always told us to dress at the level of the workplace + 1. I think this is a good rule. You look good, but not awkwardly out of place. Perhaps it's an unfortunate social rule that we shouldn't have to follow, but I've learned to shrug my shoulder to a lot of such rules and just go with it.

My question for that is how to figure out what the workplace looks like before you interview.

Ask the recruiter. This is a common question. I've had them blow it off as dress nice but I usually ask them to tell me what the hiring manager is wearing (recruiting often dresses nicer)

Re: We Only Hire the Trendiest (2016)

#55
post #3

>When I started programming, I heard a lot about how programmers are down to earth, not like those elitist folks who have uniforms involving suits and ties. You can even wear t-shirts to work! But if you think programmers aren't elitist, try wearing a suit and tie to an interview sometime. Indeed: http://web.archive.org/web/20140618142018/http://blog.42floo...

A suit costs way more money than t shirt and jeans. And people will know if you only have one suit, and people can eyeball if you have a bad suit — it’s like an advertisement for how low class you are, and it is in fact embarrassing and reflects on your credibility for those who don’t know you. That’s not something you control. The casual look is as low a hurdle as you can make it. Complaining that you don’t walk in…

Honestly go to any large unicorn or many FANGs and those T-Shirt and jeans are often a $200 "hypebeast" style shirt, $200 raw denim jeans, and $400 sneakers. I mean, I'm guilty of owning more than one of those items but I think it's dumb to claim that wearing t-shirt and jeans is much better in this regard.

Re: We Only Hire the Trendiest (2016)

#56

I think this is spot on. When I started in the 90s hiring was more like “you are smart so you will be able to learn”. Now it seems you really have to chase the latest cool stuff all the time or you quickly are marked as outdated. What they don’t seem to understand is that if you are the cool hotshot that’s working on an important project for a while you are almost by definition outdated after a while because you will…

A lot of this is pretty specific to web development, I know it exists elsewhere too but I think it's most pronounced on the web and in the javascript community. To the point where javascript has inserted itself into more or less every domain and people look at you confused, asking why you'd bother writing your software in anything else.

Re: We Only Hire the Trendiest (2016)

#57
post #7

I worked on a big C# system with hundreds of windows servers, developed on Visual Studio etc. It was an awesome project and everything worked like clockwork. However there are very few projects using that technology so when I wanted to move I had trouble getting interviews. I'm now working with a very fashionable tech stack, its horrible, infrastructure is regularly broken, people can't trace problems easily, our fun…

I'm a C# developer at what I think is a really good dev environment. Tons of smart people here and we're highly productive. I like C# and I honestly feel boring software is better. I can't get behind chasing the latest trends.

Why should I learn Node instead? Does writing backend Javascript mean you're a better developer?

Re: We Only Hire the Trendiest (2016)

#58
post #5

Earlier quoted context omitted.

My university's career coaching always told us to dress at the level of the workplace + 1. I think this is a good rule. You look good, but not awkwardly out of place. Perhaps it's an unfortunate social rule that we shouldn't have to follow, but I've learned to shrug my shoulder to a lot of such rules and just go with it.

My question for that is how to figure out what the workplace looks like before you interview.

If its a software company then I'd guess the default is T-shirt and jeans. If its doing software or tech inside a larger business organization then it may be business casual (khakis, collared shirt). You may be able to check the companies website or social media accounts to find pictures of the workplace.

If all else fails or you still aren't sure just ask the recruiter.

Re: We Only Hire the Trendiest (2016)

#59
post #45

One frustration I've had recently is the number of companies encouraging or requiring code in the public sphere. They want to see open-source contributions or an active and impressive personal github page. If your employer is protective of their IP ( mine is ) and/or you are not willing to spend evenings and and weekends on pet projects, you are out of the running. Also >But if you think programmers aren't elitist, t…

>One frustration I've had recently is the number of companies encouraging or requiring code in the public sphere.

This unfortunately isn't just a trend on programming. I've run into the worrying trend of marketing roles or contracts requiring live walk throughs of running ad accounts of current clients so people can vett you...uh what? As if NDAs don't exist or you just plain don't feel comfortable sharing client data and marketing secrets you're suddenly unhireable.

Re: We Only Hire the Trendiest (2016)

#60
post #45

One frustration I've had recently is the number of companies encouraging or requiring code in the public sphere. They want to see open-source contributions or an active and impressive personal github page. If your employer is protective of their IP ( mine is ) and/or you are not willing to spend evenings and and weekends on pet projects, you are out of the running. Also >But if you think programmers aren't elitist, t…

As someone who uses Github and OSS contribution as a strong hiring signal, I'd like to offer an alternative perspective. People who do a lot of personal projects tend to be very good developers, especially when you can see a demonstrated ability to ship.

This is also helpful for people who haven't worked at big name companies or don't have degrees from elite universities. I'd happily hire someone with no experience and no degree if I can see multiple impressive projects they've built for themselves (I've done this, and it's worked out very well).

Yes, it works against people who don't like to code in their personal time, but it also removes a bunch of filters and in my experience works better than anything else for finding good candidates.

Post reply on HN