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.
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.
The act of explaining it in enough detail so another person could understand the problem usually increases my understanding of the problem.
Isn't that what students are for?
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.
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.If so, why would you not accommodate someone who works slightly differently in this one way?
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?
some of the best people startup people, at least in my experience, are "unique."
Embrace the odd, create the future.
In theory anything you can do in a meeting, talking with others, can be done in email, but IMHO well run meetings are a very good way of bringing ideas together, solving problems etc. Talking to yourself is like having a meeting with yourself :-)
Not everyone thinks the same way. This isn't a bug.
But if he's not acting like that, then maybe he's just helping you expand your definition of normal.
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.
Sometimes if you're eager to say something to real people, you may talk to yourself (ADHD people do it). If you're standing right there and he's talking to himself, then he either doesn't know you're there, or it's just helping him think.
It's also quite a bit different than 2 people talking, or even someone talking on the phone.
I think a quiet workplace is very important for proper thinking.
I mean, as long as he isn't muttering about red staplers or burning the office down, what's the issue?
Not always. I talk to myself all the time whether I'm happy, sad, stressed, relaxed, whatever. I just seem to solve problems better when I explain them to myself out loud -- see "rubber ducking": http://c2.com/cgi/wiki?RubberDucking