Extracto de la transcripción automática del vídeo realizada por YouTube.
- Alright, we're gonna get started here. We are constantly asking questions everyday: How's it going? Have you used this gem before? Do you know where lunch is? Well, what if asking these questions makes us feel like an imposter, unworthy of the job they're paying us for and unworthy of our friends? And what if that feeling of being unworthy keeps us from making new friends, from questioning our coworkers, from learning and improving ourselves? Well, this was me until about a year ago.
Once I realized that I was avoiding asking questions out of fear that someone would find out that I didn't belong, I made a conscious effort to change that. And so I'm here today to give you A Programmer's Guide to Asking Questions. My name is Amanda Quaranto, and my background is in manufacturing and process engineering.
I've worked in both aerospace and electronics manufacturing. I taught myself to program, brought up on tutorials and books like Chris Pine's Learn to Program and Code School. And as of March of this year I am the Customer Support and Happiness team lead at Travis CI.
Travis CI, for those of you who don't know, is a continuous integration platform. You provide your code and your test via GitHub and we provide the virtual machine and we can also deploy your code for you. As always, it's free for open-source projects. And I do have tons of stickers so please come and get some stickers.
So I wouldn't be here today if it weren't for Travis, but I also wouldn't be here if it weren't for two exceptionally patient little boys who. . . sacrificed a lot of mommy time for me to be able to come here and talk to you. They love fist bumps and stickers so if you see them, please say hi to them, and of course, they are the cutest builders in town.
So before we dive in, Coraline and Peter, if you can help me out. We're going to do a quick writing activity. I have some exceptionally large index cards and some pens, it's not necessary that you have them, but we're gonna start thinking critically about the questions that we're asking and not asking everyday.
So we're gonna divide this into two parts. We're gonna have side A and side B. Starting with side A, I'll give you a few minutes to get your note cards. Poor planning for a process engineer, let me tell you. Alright, all the questions will be up on the slide so you can can catch up as you get them.
So like I said, side A is going to be about the questions that we're asking everyday. So the first thing I'm gonna have you write down is: what was the last question that you asked someone? It's very possible that it happened right here in this very room.
You turned to the person next to you and said, "How's it going, what are you working on?" Anything like that. It could've been something more complex like, "How do I implement this gem?" or, "Can you teach me how to do that?" But whatever it was, go ahead and write it down.
The next thing I'm gonna have you write down, and it's gonna sound kind of silly at first: did you care what the answer to your question was? And I know what you're thinking, "Of course I cared. "I opened my mouth "and the words came out of my mouth "and I directed them at a person, of course I wanted a response.
" But did you really? In the case of asking, "How are you?" or "Sup?", we oftentimes throw that out as an icebreaker, and so you don't really necessarily care the answer to that question. So this a simple yes or no, did you care? The next thing is fairly easy as well: did you learn anything? In the case of "How are you?", you probably learned, "The person sitting next to me is fine.
"They had a terrible flight in, "they had the Quaranto baby sitting next to them", anything like that. What did you learn? The next thing, and we'll talk a little bit more about it, is: was it a leading question? Did it start a conversation? Did it start an argument? A leading question is gonna be anything that is more than just a yes or a no question, like this one, this is a yes or no.
And the last thing we're gonna have you write down for side A is: what was the outcome? This is a little bit different than if you've learned anything. In the case, again, of "How are you?", maybe you're making a mental note to check back in with the person sitting next to you.
Maybe they said, "Fine", and you don't really believe them, and so you're gonna check back in with them in a few days to see if they are actually fine. Or maybe you have to go Google something later, but whatever it is, let's write down the outcome. So let's flip over to side B.
[ ... ]
Nota: se han omitido las otras 2.216 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.