Ask HN: Would you employ a developer who talks to himself during work?

[mattjung]

I know this question might sound bizarre. I have never met someone in my career talking to himself in front of his computer until recently and puzzled myself about the reasons and the impact on his work...

[lee]

Is he doing some kind of rubber duck debugging? http://en.wikipedia.org/wiki/Rubber_duck_debugging

I don't talk to myself, but sometimes by simply talking aloud about my problems to my peers I can flesh out a solution to a hard problem.

I have seen other programmers talk to themselves to find a solution when they're stuck, and it seems to work quite well.

[brandnewlow]

What tends to happen with me is I'll hit a snag that I can't seem to figure out or debug myself. So I fire up gmail and write a note to one of the contractors who does odds and ends stuff for me.

I describe the problem in decent detail and ask when he/she is available to fix it. Send.

Then a few minutes later, the solution appears in my head, I go solve the problem myself, and send an apology note to my developer.

[asdfghjkjnmhb]

>The process is to meticulously explain code to an inanimate object

Isn't that what students are for?

[mattjung]

Nice link!

[marcusbooster]

At least I know he's focused on his work. As opposed to say writing an Ask HN about it.

[mhd]

Probably not, if he's doing that all the time, the office is shared, he does it in different voices and/or uses the Black Speech of Mordor.

Other than that, why not? When I'm behind closed doors, I sometimes to this myself, too. Giving thoughts proper form often helps to order them, so both writing and monologue are perfectly fine. That's what some people get out of pair programming.

[tzs]

We had an employee once who essentially narrated himself. For instance, if he was installing the latest build of our software to test the installer, he might say something like this:

    I'm putting the floppy in the drive. I see it on the
    desktop. I'm double clicking it. I see the new
    installer. Now I'm opening RegEdit. I'm finding the
    keys for $OurProduct, and deleting them to test a fresh
    install. Now I'm double clicking the installer. I see
    a dialog box. I'm typing in my product key, and hitting
    the install button...

If you had to do anything with him, he'd include you in the narration:

    OK, now I'm watching Bob make a new release for me to test.
    His compile finished, and he's copying to a floppy. He's
    giving me the floppy. I'm going to go test it...

This got real annoying real fast.

[runjake]

Wow, that's hilarious. Any chance he was taking voice notes to a device?

[varjag]

I would, since I do it myself. Infrequently actually, but a lot of it is swearing.

[jarek]

Do you accommodate other preferences of the developer? Do you let them adjust their chair or rearrange their desk? Do you let them come in at flex hours, as long as the work is done and they don't unduly inconvenience others (meetings, etc)? Do you let them wear headphones at work? Do you let them choose their preferred editor (again, as long as it doesn't inconvenience others) or perhaps even OS?

If so, why would you not accommodate someone who works slightly differently in this one way?

[SanjayUttam]

It depends. If they are talking and it is barely audible, sure...I do this, and with the exceptional expletive, it's more or less silent. Most of the developers here, myself included, wear headphones for the day unless we're talking to one another. I don't think anyone even notices I'm mouthing things to myself or reading "out-loud" (e.g., moving my mouth).

Not totally related, but I'm also bobbing my head to music all day (usually groovesalad on some.fm)

All that said...how would you know if you're going to hire someone who talks to themselves anyway, or is this just hypothetical?

[madhouse]

Yes, I would. Thinking out loud helps a lot in my experience - and that's what most people perceive as "talking to himself".

[Manolis]

Since the question refers to a developer (a special category of employees) the answer is a strong "Yes".

[ra]

Absolutely. I'm a developer who has hired 15-20 other developers in my time. "talks to himself" isn't a reason not to hire a nice, talented developer.

[jasonmcalacanis]

if they file clean code, solve problems, are positive in their nature and make the people around them great they can marry their their iPad.

some of the best people startup people, at least in my experience, are "unique."

Embrace the odd, create the future.

[retroafroman]

I wouldn't. At one job, the desks were arranged so that I sat at my computer with my back to my coworker (who talked to himself/no-one-in-particular/me throughout the day) and I could never tell when he was trying to talk to me or just vocalizing something. Also, I found it annoying. A small annoyance, sure, but if it bothers your other developer's, it's not a good idea.

[icefox]

Well if you were doing the hiring I am guessing you can also set the seating.

[sofuture]

I wouldn't consider it a factor in an employment decision unless it was exceptional in some way (i.e. it was non-stop, extremely loud, disruptive).

[mattjung]

In fact, I was wondering if someone who needs to talk out loud has a different approach of solving problems or if he has even has some shortcomings given that he is not able to keep things in his mind. When children learn reading at school, the first step is to read loud, then to understand what they read out loud. It takes considerably more efforts until a child is able to understand a text she is reading silently.

[smutticus]

Talking to yourself is fine. It's when you start responding to yourself that you should be worried.

[abyssknight]

This is funny, but I respond to my own questions all the time. Often out of sync with the timeline of events, too. I'll remember an answer and answer my question from 10 minutes ago all while discussing it with myself. ;)

[basicxman]

There's a difference between delusional psychosis, being socially awkward, and talking to yourself to debug computer problems. However, some might believe it to be a very thin line between psychosis and debugging computer problems aloud.

[niels_olson]

Depends. At the best, you're being paranoid. At the worst, he could be developing schizophrenia. Is he in his late teens or early twenties, does he sound agitated or paranoid? Is his thought process coherent? What is he talking about? A young, paranoid male talking gibberish to himself without regard for who's around would be concerning. If you want a great portrait of schizophrenia, watch "The Soloist": http://www.imdb.com/title/tt0821642/

But if he's not acting like that, then maybe he's just helping you expand your definition of normal.

[robgough]

If they were working from home, sure :P

I can't see it impacting on their work, but it might irritate others.

There is an obvious second question though, how would you know before you employed them. The question then becomes, would you fire an developer that talks to themselves at work.

In which case, No - I probably wouldn't. At least not without trying to find other ways of dealing with it, it is possible they don't even know they're doing it - and after making them aware you might find that they stop.

[agotterer]

Sometimes people with dislexia or other reading problems will read aloud. Sometimes, the only way they can process the content is by hearing it.

[jdietrich]

Will he get a private office?

[klaut]

I talk to myself during work most of the time (but usually it happens in the privacy of my head only). Or better, I talk to the monitor in front of me as if it would help debug something faster :) ... well sometimes it does, actually. But when i become very frustrated with the piece of code i am debugging, I usually say something out loud as well.... swearing mostly :D

[markbnine]

Sounds like the newest in agile techniques - pair programming for one. Write a book and start your consulting career now.