This is the problem

[nelstrom]

Code and prose have more in common than you may realize: both are forms of language, which is a wonderful thing. Language lets us communicate. Communication let's us work together to get stuff done. Whereas miscommunication can lead to software bugs, or worse: people problems! Why is it that our intended meaning can be so easily garbled?

In this Eclair session, we'll look at examples of miscommunication in code and prose. We'll see how ambiguity can creep into our language, causing our intended meaning to be lost in translation. Ambiguity is hard to recognize, as it often falls into our linguistic blind spot, but just knowing that it's there can help us bring clarity to our use of language.

Want to know how? Vote for this Eclair session!

[tigrish]

Dude, there's no voting - you're in!

I'll add you to the lineup over the weekend :)

[nelstrom]

Nice one! I better purchase myself a La Conf ticket.

[kytrinyx]

Is there a video record of this eclair session? Because I was there in person, and I keep wanting to share it with other people.

[nelstrom]

Thanks @kytrinyx! There's a recording from when I gave the same talk at Rocky Mountain Ruby conference. I don't know if they have footage from La Conf?

[kytrinyx]

thanks!

[tigrish]

I loved this talk - so poetic!

However I don't think I have the recording :(

On 8 May 2015, at 04:18, Katrina Owen notifications@github.com wrote:

thanks!

—
Reply to this email directly or view it on GitHub.