But if he's not acting like that, then maybe he's just helping you expand your definition of normal.
Ask HN: Would you employ a developer who talks to himself during work?
41–47 of 47 posts
Re: Ask HN: Would you employ a developer who talks to himself during work?
#42Talking to yourself is a symptom of stress. Because your working memory is too populated by stressors in order to keep the entire "conversation" inside your head, you externalize it. Think of it as paging out. The only inconvenience is that it can bother people. Well, maybe there are other inconveniences, too, but I'm not aware of any studies that suggest externalized verbal problem solving creates worse results than…
> Talking to yourself is a symptom of stress. 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
Re: Ask HN: Would you employ a developer who talks to himself during work?
#43I mean, as long as he isn't muttering about red staplers or burning the office down, what's the issue?
Re: Ask HN: Would you employ a developer who talks to himself during work?
#44We 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 click…
Re: Ask HN: Would you employ a developer who talks to himself during work?
#45Re: Ask HN: Would you employ a developer who talks to himself during work?
#46Is 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.
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.
The act of explaining it in enough detail so another person could understand the problem usually increases my understanding of the problem.