Hacker News Reader

Comment by bobabob | Hacker News Reader

> I think it's time we accept that the person we are talking to is who they say they are on their resume.

Yea because we live in a place where everyone is super honest and no one is going to try and take advantage of that to make 500k a year.

IMO, it doesn't work. Talk is cheap.

I wouldn't have a job if I had to talk my way into any company, I'm an introvert, I suck at communicating orally. But I can solve problems and write really good code. You throw problems at me during an interview and I'll solve them. Ultimately your company's code is not going to write itself.

View on HN

>Yea because we live in a place where everyone is super honest and no one is going to try and take advantage of that to make 500k a year.

I would be THRILLED if I was put into some kind of a short probationary period, with limited access (and potentially restricted salary, with retroactive reimbursement) while I showed what I was worth. I personally have a hard time demonstrating that in short interviews, and it's only once I come in contact with the shape of the company's problems do I show my value. Imo it would lower the stress and paranoia on both sides over a candidate's fit.

That can work for some, but imagine you already have a job, and time commitments, and it takes 5-10 companies to find a fit.

Spending ~1-2 months is expensive.

If a company temporarily paid higher salary and covered your health insurance during this probationary period to account for the risk, I'd go for it. Otherwise, never.

> Yea because we live in a place where everyone is super honest and no one is going to try and take advantage of that to make 500k a year.

You are right that there is more risk with this approach. I honestly think that its a better, more humane way to do things though. Anecdotally, I've hired a couple _really_ solid developers via this methodology. At least in my case, it's been working out well. As always, you try stuff and iterate.

> I'm an introvert, I suck at communicating orally.

I get it. So am I. Its actually very hard for me to reply to these comments b/c of my general aversion to putting myself out there! I don't think there's a one size fits all solution. At my company at least, being able to communicate effectively both orally and written, is important. We do a lot of pairing and documentation etc. Thats not for everyone. YMMV.

Writing code is not everything. You're going to work with a team, deal with managers, go to meetings, discuss and brainstorm ideas.

Lack of communication skills is a bug not a feature.

Do all that without writing decent code and you still have nothing to show.

> Lack of communication skills is a bug not a feature.

A bug I'm willing to take in exchange of producing high quality code. Besides, we live in 2022 now, we can type. I just said I suck at talking not at communicating. There are multiples forms of communication which don't involve opening your mouth.

Reply on news.ycombinator.com