Thanks David! You inspired me to create a table of code phonology <https://github.com/Carpentries-ES/board/blob/96e94a023e52e4213775101e624004dc6e35c228/Convenciones_Traduccion.md#fonolog%C3%ADa-del-c%C3%B3digo---c%C3%B3mo-leerlo-en-voz-alta> for the Spanish Unix and GIt lessons!
I got most of the data from this ASCII site <http://www.elcodigoascii.com.ar/> and from the translated lessons themselves. I agree with Madeleine that it would be interesting to see what words our instructors from around the world use. Rayna Rayna Harris @raynamharris <https://twitter.com/raynamharris> http://raynamharris.github.io/ On Fri, Mar 16, 2018 at 6:41 PM, David Martin (Staff) < d.m.a.mar...@dundee.ac.uk> wrote: > > > From an ENglish point of view.. > > On Mon, Mar 12, 2018 at 12:14 PM, Kevin Vilbig <kvil...@gmail.com> wrote: > > This issue has been on my mind since teaching my first few classes. > > Here is a quick lexicon beyond what you mentioned. > > { } can also be called curly braces > curly brackets, braces > () parentheses, round brackets > [] brackets, square brackets > ! can be called bang or exclamation point > exclamation mark, pling > # can be called crunch, sha, pound, or hash > Typically hash > \ backslash or backwhack > / slack or whack > forward slash or divide > * star or wildcard or asterisk > ~ tilde or that wiggly line next to the one key > squiggle (next to RETURN, ENTER in UK) > _ underline, underscore > - dash, hyphen > . full stop, dot > ` backtick, no not quote, the other one. > > > And that's only for single characters! What about compound character > operators? Perl 6 can even take some unicode symbols as arithmetic > operators! > > On Mon, Mar 12, 2018 at 10:40 AM, Amy E. Hodge <amyho...@stanford.edu> > wrote: > > I found this very interesting. I also find that mixtures of cultural > backgrounds in the class – or a difference between myself and the learners > – can sometimes lead to confusion in the different ways people describe the > symbols in particular. > > > > I spent the first half day leading a week-long training (not for coding, > but for something internal to the company I was working for where there was > an internal “language” to be learned) before I realized that while I was > describing them as “braces,” “square brackets,” and “parentheses,” my > learners described these as “flower brackets,” “square brackets,” and > “round brackets,” and the three together under the umbrella of “brackets,” > which I only used in reference to the square ones. Learning got much faster > after we got that squared away! > > > > ~ Amy > > > > Amy E. Hodge, PhD > *Science Data Librarian* > > amyho...@stanford.edu > > 650.556.5194 <(650)%20556-5194> > > orcid.org/0000-0002-5902-3077 > > > > Data Management Services > Branner Earth Sciences Library, 212 Mitchell > 397 Panama Mall; MC 2211 > Stanford University > Stanford, CA 94305 > > > > *From: *Discuss <discuss-boun...@lists.software-carpentry.org> on behalf > of Lex Nederbragt <lex.nederbr...@ibv.uio.no> > *Date: *Monday, March 12, 2018 at 2:48 AM > *To: *Software Carpentry Discussion <discuss@lists.software-carpentry.org> > *Subject: *[Discuss] Code Phonology - on reading code aloud > > > > Hi, > > > > Felienne Hermans has a really interesting blog post and accompanying paper > on Code Phonology, i.e. on reading code aloud: http://www.felienne.com > /archives/5947. > > > > This is relevant for teaching through ‘live follow-along coding’: are we > aware what vocabulary we use and what effect that has on our learners (e.g. > cognitive load)? Do we use consistent vocabulary across lessons and between > workshops? > > > > Food for thought... > > > > Lex > > > > _______________________________________________ > Discuss mailing list > Discuss@lists.software-carpentry.org > http://lists.software-carpentry.org/listinfo/discuss > > > > > -- > Kevin Vilbig > > _______________________________________________ > Discuss mailing list > Discuss@lists.software-carpentry.org > http://lists.software-carpentry.org/listinfo/discuss > > > > The University of Dundee is a registered Scottish Charity, No: SC015096 > > _______________________________________________ > Discuss mailing list > Discuss@lists.software-carpentry.org > http://lists.software-carpentry.org/listinfo/discuss >
_______________________________________________ Discuss mailing list Discuss@lists.software-carpentry.org http://lists.software-carpentry.org/listinfo/discuss
