Skip to main content

Why who you are may define what you Hear

Twenty-thousand Hertz just had a spectacular episode - Sonic Illusions. I encourage everyone to listen to it and perhaps more importantly the underlying message.

It starts off referring to the whole Yanni Laurel thing which has been explained in a number of places but one of the psychologists, Diana Deutsch, noted that the idea of sonic illusions could also be explained by dialect. She noted an instance where a two tone sound was heard one way by students in Southern California and another way by herself. While the story was about a specific type of sound, it also noted that this might account not just for sounds but also for understanding words.

But this isn't about trying to help your New England aunt understand their Bronx-born Jewish New Yorker or how North Englanders talk with a different lazy accent than their Yorkshire counterparts. If the way you hear sounds is different, it may also be affecting the way you hear words and the way you react to conversations.

When someone who says "you should do this", what is your impression? Are they telling you what to do or suggesting an action? We are often told it's the tone that tells the actual request, but it may simply be their dialect and where they are from. Just as importantly, when you say "you should do this", how it is interpreted may not simply be on using your "as-nicely-as-possible" voice, but also who you're saying it to (obviously, you should always be nice when telling people what to do).

I may be overreaching here but I'm interested to keep this in mind in future meetings. I recall back in 2006, I was at a Southwest Fox conference and met Craig Boyd for the first time. Later in the evening, he looked at me and said "whoa, you're really intense." Granted I was at a developer conference and, yes, I'm a developer and I get enthusiastic, but that comment has stuck with me. The 20K podcast episode has made me try and take not just my words but my audience into consideration.

Comments

Popular posts from this blog

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

Who Wants To Be Logical? I Do! I Don't! (with Claude)

In my book, Towards Consciousness, I explore PET , a theory that attempts to explain consciousness and possibly how it might apply to AI. As part of the conversations with AI series, I've included this conversation with Claude.AI in which we were talking about something very different and yet the conversation redirected itself back to PET. For the record, there is no such thing as "Colfsity". A It's interesting to me that people want to proclaim their distinction from being rigid and unlike machines, yet they also complain that the "best" people keep a rigid schedule, regular routines and logic understanding of issues. That's a perceptive observation about a real tension in how people think about themselves and what they value. There does seem to be this paradox where rigidity is simultaneously rejected as "robotic" or inhuman, yet praised when it appears as discipline, consistency, or logical thinking. I think part of what's happening is t...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...