I should write up my notes from talking to them. I explained that programming was like speaking a language computers understood and used Spanish and English as examples.
I defined code as the words computers understand.
I defined a program as a story made up of code that a computer knows how to read.
A couple of the great questions I got were "Do you like your job?" and "Do you like typing all day?"
My brother learned Cantonese fluently as a LDS Missionary. He then enlisted in the army after 9/11 and was given a battery of aptitude tests. I'm assuming this was one of them because he ended up at DLI learning Arabic and speaking that fluently as well.
DLI and being a Mormon missionary are about the two best places you can learn to speak a 2nd language fluently in a short amount of time.
> Before the participants took the half-day long tests they’d been sorted according to how well they knew a second language
Does doing well in the tests reflect how well someone will learn a second language, or does having already learnt a foreign language (e.g Cantonese) affect how well someone will learn another (e.g. Arabic) ? It could all be a mixup of causation and correlation!
Yup. You can use any SMS-enabled Twilio number (or voice-enabled number if you change some of the code to respond to dial-tones) - list can be found at https://www.twilio.com/international
It really shouldn't be. Struct packing is a purely technical skill, not really computer science at all; there's no general insight you gain from understanding it, and it's easy to look up and teach yourself if you need to learn it later. (Not that most programmers will ever need to do it; these days even many embedded systems have enough memory and cpu performance that this kind of microoptimization is a poor use of programmer time)
Not universally. None of my university's Java based curriculum or my brother's university's Python based curriculum mentioned this. My community college's C++ based curriculum mentioned it in passing.
I seem to remember it being mentioned in Bruce Eckel's excellent "Thinking in C++".
That said, I'm kinda curious how much this affects Objective C objects.
There is a distinction between the Startup Battlefield (companies that are launching) and the Hackathon (apps and hacks made in a constrained time period). His criticism seems to be leveled at the Battlefield judging.
I defined code as the words computers understand.
I defined a program as a story made up of code that a computer knows how to read.
A couple of the great questions I got were "Do you like your job?" and "Do you like typing all day?"