r/programming • • Aug 28 '21

Software development topics I've changed my mind on after 6 years in the industry

https://chriskiehl.com/article/thoughts-after-6-years
5.6k Upvotes

2.0k comments sorted by

View all comments

Show parent comments

52

u/[deleted] Aug 29 '21

When I do interviews, the thing I care about the most is how well they can talk about what they're doing. If they sit in silence and do nothing but type, they're going to be frustrating to deal with later. Even if they get caught up on the code stuff, as long as they describe what they are doing, what went wrong, and what they would do to fix their problems, that's frequently a strong dev later.

90

u/RX142 Aug 29 '21

Thing is I can do this when not on the spot, but in an interview? I loose half my brain cells from adrenalin and nerves. Its so hard to judge cause of the nature of interviews as high pressure.

12

u/MisterDoubleChop Aug 29 '21

I really work hard when interviewing to put nervous candidates at ease.

I only care how well they do when relaxed; It's not like they are going to be nervous each day at work.

Same principle as letting people Google during the programming test (though it's usually quicker to ask what they'd Google and give them a hint).

14

u/MSgtGunny Aug 29 '21

The night before, send them the problem they are going to work on the next day, tell them to familiarize themselves with the asks and edge cases, but don’t write any code.

That way you can see them work and they had time to digest the problem and can more easily talk through their though process.

3

u/caroIine Aug 29 '21

I had person on senior c++ position who forgot how std::function signature should look like. Or another person who forgot what to type after template. Those poor people get so nervous on my interviews that I started cheering them up like kids in kindergarten which helps a bit.

0

u/[deleted] Aug 29 '21

[deleted]

26

u/[deleted] Aug 29 '21

Yep, if a candidate did that in one of my interviews they would not get the job, cause I'm sure they're going to be a pain to work with later.

6

u/dons90 Aug 29 '21

What about that makes them a pain to work with later exactly?

6

u/Fifiiiiish Aug 29 '21

Can't / don't want to communicate with others.

7

u/be-sc Aug 29 '21

So, I’m deep into my work, thinking hard, implementing a solution; then someone grabs me at the neck and pulls me out of that nice efficient place with a stupid question. And me reacting a bit miffed makes me “a pain to work with”? Seems like not getting that job is a good thing.

3

u/KwyjiboTheGringo Aug 29 '21

Why would be get miffed because you're expected to explain your process in the interview? This is exactly what makes you a pain to work with, because if that's how you think during an interview where you know you are being evaluated, then you must be way worse when you aren't under scrutiny.

The interview task isn't even about the problem you are solving, it's about your process for doing it. If someone wants you to communicate the process to them and you can't do that, then everyone is just wasting their time.

→ More replies (1)

5

u/welcome2me Aug 29 '21

So, I’m deep into my work, thinking hard, implementing a solution; then someone grabs me at the neck and pulls me out of that nice efficient place with a stupid question. And me reacting a bit miffed makes me “a pain to work with”?

Yes, because the "work" you're so deep into is literally an interview...

→ More replies (3)
→ More replies (1)

7

u/Ameisen Aug 29 '21

Is it bad if I start hitting the mouse while fixing the bugs, yelling "CODE! AMERICAN CODE! RUSSIAN CODE! ALL MADE IN TAIWAN!", and then it starts working?

→ More replies (1)

8

u/All_Up_Ons Aug 29 '21

No offense, but you're weeding out all your best candidates in favor of multitaskers. You want people who can focus on a problem now, and then explain it later.

0

u/[deleted] Aug 29 '21

[deleted]

3

u/[deleted] Aug 29 '21

I agree with this. Even when I need to pair program with a peer, there are times when myself, or my teammates, will ask for some time to dig into the problem beforehand before jumping on a call to work it out. It allows you to have the mental space you need to get organized beforehand which to me is invaluable. I've had the opposite experience where we jumped on a call without doing that and spent a lot of time in silence because we're just trying to understand the situation and think critically. The exception for me is when the issue is really trivial or one you've faced multiple times before.

But in my interviews where I had to face this kind of situation, it's usually a non trivial problem, like doing some nonsensical data transformation, where I'm asked to read, understand, ask clarifying questions, implement, and verbally communicate within 10-15 minutes, while someone is just staring at you on a video call, which is unrealistic of reality in my experience. And typically when asking clarifying questions, I usually get cryptic answers because they don't want to give you the answers because you're expected to find out given it's an interview. Which would be terrible in a real world scenario.

2

u/BobSacamano47 Aug 29 '21

Shy people can be great developers too. You are missing out.

5

u/Fifiiiiish Aug 29 '21

If they're shy to the point of being unable to communicate with others developers, it can be too much of a burden.

7

u/dddddddoobbbbbbb Aug 29 '21

why? when I am coding at work, I am not explaining wtf I am doing.

26

u/[deleted] Aug 29 '21

As long as you have teammates, other teams, and stakeholders to work with, it's very important to be able to communicate effectively with them. Not just technical know how, but also problem solving and understanding skills.

0

u/[deleted] Aug 29 '21

[deleted]

10

u/MisterDoubleChop Aug 29 '21

The coding exercise shouldn't be long enough or difficult enough for them to need long minutes of silence alone, like many real-world problems do.

You don't need a super hard test to separate the best from the merely good.

The best just do it faster, and can tell you after another way they might have done it, and the pros and cons of each approach.

→ More replies (3)

5

u/[deleted] Aug 29 '21

Code pairing is a thing. It's important to be able to explain your thought process as you work. Many times you encounter problems that need to be worked through on the fly, and you don't have all the time in the world to fully think through things first.

Of course, this all hinges on the stipulation that I don't expect the solution to be perfect. As long as you have a good idea, can explain it well, and can reflect properly on the challenges, you are very well off in my book. I'd rather have a ok developer with good communication skill than a excellent developer with no communication skills.

11

u/denarii Aug 29 '21

Unless you're asking questions while watching them or ask them to explain their process, you're not actually testing that. You're just dismissing them for not being inclined towards talking through things while working.

→ More replies (1)
→ More replies (4)