The story of Dr. Kildare. Whatsoever house I enter, there will I go for the benefit of the sick. Whatsoever things I see or hear concerning the life of men, I will keep silence there on, counting such things to be held as sacred trust.  The story of Dr. Kildare, starring Lou Ayers and Lionel Barrymore. Metro-Goldwyn-Mare brought you those famous motion pictures. Now this exciting, high-warming series is heard on radio. In just a moment, the story of Dr. Kildare. But first, your announcer.  Wider, Dr. Gillespie, a little bit wider. Come, just found it, Jimmy. What do you think I am, an alligator? No, I just think you're a human being who needs a regular check-up just like any other human being. Check-up? Well, I never felt better in my life.  Oh, is that so? Yes, that's so.  Well, if your health is as good as it seems to be, there's no harm in having it verified.  Well, now what are you going to do? Just have a look at your eyes, turn out the overhead lights, Parker. And just you keep looking straight ahead of you. I know where to look. I was doing this before you were born. You were doing it before Abraham Lincoln was born. Well, you ought to know, Parker, you were there. Oh, why? Please, Dr. Gillespie, just be still for a moment. Now, roll your eyes to the left. Stay that way. Well, Jimmy, what is it? Just eye strain, probably. All right, Parker, lights on, open the blind again. Oh, don't be mysterious, Jimmy. You found something? Tell me about it. Have you been straining your eyes or doing any special work away from the hospital? Well, yes, just a little. Well, now don't you be mysterious. All right, Jimmy, all right. I have been preparing the paper. On what? Well, a new method of establishing infallible controls in the use of antibiotics. If I'm right, it'll eliminate all guesswork with any reasonable number of test cases. But you've been working on that on and off for years. I know, I know, I know. But for the past few weeks, I've been working on them every night. Oh, why the sudden rush to finish? Jimmy, I have been invited to read my findings at the International Scientist Assembly at the Warren Hotel next week. Why, Dr. Gillespie, that's wonderful. It's just wonderful, recognition by the international. Yes, why did you keep it to yourself? I kept it to myself so as I wouldn't have you fluttering around me like a headhunter and a cannibal picnic. Well, international. I knew it. I always knew they'd recognize your work sooner or later. This puts you in line for the Henderson Award, the highest honor in science. Now, hold your horses, Jimmy. Hold your horses. I am not the only one who will be reporting to the assembly. They pick three men every year. I know. One of the others may make a contribution much more important than mine. My money rides on you. Yes, and mine too. They'd have to be crazy to pick anybody else. Well, thank you, Parker. Thank you. Jimmy, well, are you finished poking into me? What about my eyes? Oh, just simple eye-rises. Well, then why were you looking at me like Calamity Jane when you finished examining them? Well, because I didn't know the work strain you've been under. It simplifies the diagnosis. Well, what would your diagnosis have been if I hadn't told you about the paper? Oh, why? Well, I'm afraid it might be glaucoma. Glaucoma? Well, nothing to get excited about. You know the symptoms are similar to eye-rises. The symptoms may be similar, but the diseases aren't. Glaucoma is a mighty serious thing. Well, all your eyes need is a little rest. What else are you prescribing, Jimmy? Nothing. No, mydriatic? Not even atropine? Not necessary. It's a mild case. Jimmy, mydriatic is usually prescribed for eye-rises, but it would be very harmful in the case of glaucoma. Is that why you want prescribing? Oh, I knew it. I knew it. You know what?  Oh, is that so? That is so, yes. Don't I have a right to know what's wrong with me? Oh, you just forget all about glaucoma, Dr. G. Just concentrate on your dictation to Diana. We're pulling for you to bring home that Henderson Award. What's on your mind? Parker, is something wrong? Well, Dr. Kildare, it's that horrible suit. Huh? No, no, no, no, not your suit. Here's Dr. Gillespie. Oh, well, oh, what about it? Well, of course, you'll be in a man you'd never notice it. But he's been wearing that same suit for the past ten years, day in and day out. Well, I admit he isn't exactly a fashion plate, but that's not a serious ailment. He'll never win the Henderson Award in that suit, mark my word. Now, you've got to make him buy a new one, and that's all there is to it. I'm afraid there's much more to it. Getting Dr. Gillespie to go shopping is something like getting him to walk barefoot over hot coals. He'll fight every inch of the way. Besides, the award will depend on his paper, not the crease in his pants. Well, just the same. He looks like an unmade bed. And you know what they say, clothes make the man. Yeah, well, if we're going to get him into a new suit, he'll have to think it's his own idea. Oh, how are you going to do that? Well, maybe I have a plan. What is it? Mm-hmm. Psychological approach. With the help of my new patient in room 412. That fringe girl, that Susan DeChampse? Why not, Parker? She's a female Adam Baum. That's why not. Well, remember, Parker, if we're going to get Dr. Gillespie into new duds, we only have five days. Drastic measures are prescribed, and psychologically, Susan de Champse is the prescription. Prescription? You'd better put poison on the bottle. No, no, no, no, Parker. 50 million Frenchmen can't be wrong. You just asked Dr. Gillespie to join me in room 412. Civil play? All right. But more work and less civil play would be a lot safer. Problem, Susan. Will you help? But, of course, Dr. Kildee. Good, good. Such a charming man there to pass away beside. There he is. Come in. Parker said you wanted to see me, Jimmy. Well, is this your little patient? Susan de Champse, Dr. Gillespie. Oh, such a great pleasure, Dr. Gillespie. Oh, pleasure is all mine. He has a need. What's wrong with this little lady, Jimmy? Oh, just a simple sprain of the knee. Nothing really. Do you think a sprain could have serious complication? Oh, a sprain might have mighty serious complication. Oh, doctor. Don't worry now, young lady. We'll take care of that. You know, I'm really pressed with other patients, Dr. Gillespie. I thought I'd turn Susan's case over to somebody else on the staff. Now, would you suggest anyone? Well, somebody common, of course. Yes, that's what I... If you're really busy, you are busy. Oh, I know that. Excuse my asking you that. I might take it over for you.  Oh, Susan is great furl to be left in the care of. Well... Sasha distinguished my... All right, Jimmy, you run along. Yes, sir. Well, my boy. Miss Susan will be perfectly safe in my hands. I'm sure everything will work out just fine. Goodbye. Goodbye. Goodbye. Well, Parker, what are you doing on this board? Oh, have you left him alone there with her? Yes, and the plan is working like a charm. She'll make him conscious of that old suit in no time. Patient this morning. Oh, I am fine, Dr. Gillespie. I better have a look at you, just to make sure... Oh, no, no. Let me look at you. Stand there just as you are. Oh, Sasha, man. Sasha physique. It is too bad. What's too bad? You do not have greater care for yourself. You look so fine in some ways and so poorly in others. Poorly? Who looks poorly? I've never been better shape in my life. But this shape is so hard to see as you are. Come, look in the mirror, Dr. Gillespie. Docs, I know what I look like. And you are not concerned. You do not care. Should I be concerned? Wait. Wait a minute. Has Kildare said anything to you about me?  He could not come right out and say that... You mean, uh, is that bad? But of course. You have just let everything go. And now look at the condition you are in. The bagginess, the fading color from too much use. Can you not see? So that's it. And Kildare wouldn't come right out and tell me. I knew he was pussy-footing around. I knew it. Fred, he said you would be very difficult if he told you. Difficult? Yeah. I'm a doctor myself. Why didn't he tell me I was suffering from glaucoma? Glaucoma? That's the American word for looking as you do. Well, what did you think it was? Are I right as...? I'm afraid, Susanne is confused. Well, I'm not. Not anymore. I'm afraid of Dr. Kildare in just a moment. Dr. Kildare and Lionel Baramore as Dr. Gillespie. Hello, Parker. Oh, good morning, Dr. Kildare. Dr. Gillespie left a message. Wanted to see me, isn't he here? Yes, he's in the examination room. With a patient? Yeah. Who? Himself. Himself? Himself, taking his tongue out, examining his eyes in the mirror, trying to convince himself he's got glaucoma. Glaucoma? Again? I better straighten them out before you... Oh, good morning, Dr. Gillespie. Well, you're looking bright and chipper this morning. Yes, isn't he? He brightens up my whole day. Ah, why don't you go and watch yourself out of here? What? Recently around here. Girl. Girl! You haven't been a girl since Betsy Ross took up sewing. Oh! Say, Jimmy, why didn't you tell me I have glaucoma? Oh, because you haven't. Ah, don't tell me. I know what's been going on around here. Even Susan commented about the bagginess of rotten my eyes and the fading color. Oh, so that's it. Well, what's funny about that, Jimmy? Oh, Betsy wasn't talking about your eyes. She was talking about your suit. My suit? Of course. Bagginess of the trousers, the fading color from constant wear. Constant wear. How much is it worn? I only bought it, uh... Oh, it was, uh... 10 years ago? Ah, doggone. Jimmy, it's a good suit. There's another 10 years wearing it. Feel this weave. Oh, sure. It's a fine suit. Why, who'd ever notice this mark here by the lapel? Oh, it only got scorched a little once when that Bunsen burner in the lab flared up unexpectedly. I know, I know. And this hole here near the jacket pocket. Why, you can barely see it. Well, just a little. Some acid I spilled there a few months ago. It can be re-woven someday. Of course it can. Susan ought to know that. Susan? What's she got to do with it?  She's probably been trying to get you to buy a new suit. What would I do with it? Wear it over this one?  Susan's spoiled. That's all. She's used to the continental gentleman. Continental gentleman, huh? After all, I suppose it should be considered flattering. Well, what's flattering about having a good suit criticized? Woman doesn't generally make comments about a gentleman's dress unless she's interested. Well... Of course, I know you wouldn't let that influence you. Of course I wouldn't. Good. Neither would I. And for all my own suit is a little... shine to it from where, but who cares? Jimmy, that's not the proper attitude. Oh, why? Appearance is a very important thing.  No, no, Jimmy, don't argue with me. You need a new suit. I guess I should set the example for you there. I'll go shopping with you and buy a new one myself. Well, if you really think we should. But... Jimmy, I know what's best for you. Always have. Come on. Here we are, gentlemen. This is a new line, very fine quality. I'm certain we'll find the proper sizes on this rack. Would you like them, Dr. Gillespie? How about this blue with the pinstripe? Too loud? Too loud? It looks like the kind of thing you'd wear to a seance. Haven't you got anything with a little more zip to it? Well, we have some new greys, pearl greys. No, I'm afraid they'd be a little bit too... A little too what? Let's see them. Over here, sir. Here they are with the powder blues and the canary yellows. They aren't very conservative, Dr. Gillespie.  What are those suits over there? That's the past, that partition. That, sir, is the collage shop. With each suit you get a free ukulele, Junior. Well, there's no harm in looking. Oh, hello, Parker. Where's Dr. Gillespie? Where would he be? Well, don't fret, Parker. Susan leaves the hospital today and victory is ours. See this box? Yeah, that's what's in it. Dr. Gillespie's new duds, the raiment he will don for the meeting at the International Assembly when he wins the Henderson Award tomorrow night. I picked him up this morning when the alterations were completed. Look, he did, Parker, of his own free will. Then you take it from me, Dr. Kildare, that Susan, the chance isn't leaving this hospital one day too soon. Parker, fortunately for our plan, Dr. Gillespie has never asked Susan how she injured her knee. When and if he ever finds out, we'd better go and hide. My knee, it looks as good as new, no? Yeah, sure, it looks fine. And I owe it all to you, Dr. Gillespie. Merci beaucoup. Well, you're welcome. Yes, sir, you're welcome. I'll have to keep an eye on you, you know, after you leave here. See that you have no more accidents. Oh, this time I would be careful of the train. Oh, so that's how it happened. You were hit by a train. Hit by a train? Oh, no, I tripped over the train. How did you trip over a train? Oh, not the train that makes shoo-shoo. I mean the train that pulls after me. The long train on my wedding gown. Wedding gown? Oui, I cash my heel while we are rehearsing for the wedding. Andre and me. So we postpone until tomorrow. You will come to the wedding, no? No. I have another engagement. I'm going to a prize fight. A prize fight? Who is fighting? Kildare and me. Take it easy, Dr. G, take it easy. Take it easy, take it easy. Why, I order up all the low. Well, it looks like you found out about the train, which means that you missed the boat, Romeo. Romeo. What are you talking about? I don't even know what you mean.  But you just won't admit it, otherwise you wouldn't have come in here screaming and yelling. I'm not screaming and yelling. I just want to know why my office is littered up with all this junk. Junk? What junk all we have here? The new clothes you ordered. I ordered? Jimmy Kildare, you high pressured me into buying every single thing there. You and this female Lucretia Borgia with the snooping and plotting. I was not snooping and plotting. I just told Dr. Kildare that he had to get you and do a new suit for the assembly tomorrow night if you ever expected to win the Henderson Award. Well, I might have known it was your idea. Parker, now I got news for you. I won't wear the dog-gone thing. Oh, yes, you will. It really looks good on you, Dr. Gillespie. I won't wear it. I'll tell you. Now, you listen to me. This is one time you're not going to tell anybody.  Potato sack? Jimmy, do you think she would do a thing like that? Parker's a very determined woman at times. She's an old witch. That's what she is. I don't know. There's no way you can stop her. Well, I don't care what she does. I'm not going to wear that suit. Okay, okay. Just the same. You better try it on. You too, Brutus. Come on, Caesar. It won't hurt a bit. Dr. Gillespie. Oh, you were fine. It was a wonderful paper. And you looked good, too. The award committee is coming back to the platform. You'll be selected, I'm sure. Ah, Jimmy. No, I won't. There's the winner. That little man over there. Dr. Blanker from the Copenhagen Institute of Denmark. My great scientist, Jimmy, you heard his paper. His classification of viruses is invaluable to mankind. The award announcement. It is my privilege to announce the winner of the Henderson Award for this year. Stop being sorry and beat your hands together. There's a great man going up on that platform, Jimmy. Start over again, Parker. Start on something new that may win the award next year, or the year after. The year after that. Dr. Gillespie may lose, but he'll never quit. We will return to the story of Dr. Kildare. Come in, come in. Don't you have their starting on a new project already? Well, it's something I've been meaning to get at for some time now. I suppose you noticed he's wearing that old potato sack again. Don't call this suit a potato sack.  You should be wearing your new suit, Dr. Gillespie. A new suit? Feels more like a straight jacket.  Here's the morning paper. Picture the assembly and Dr. Blanker and his one of you right on the front page. Picture me? Oh, say, you look real nice. Real nice. What does it say, Jimmy? Well, it says, uh, Dr. Blanker, winner of the Henderson... No, no, where's the part about you? Oh, here. Dr. Leonard Gillespie, who received an ovation for his paper on antibiotics, was given a special citation by the committee after the meeting ended. He was... Oh, no. Well, he was what?   Best dressed doctor at the assembly. Best dressed? I gotta go to the wards right away. Okay, you come back here. You'll need a jet plane to catch you today. Best dressed. If only the committee could get another look at you now. It was. Oh, yeah, yeah, yeah. In my potato sack. Yeah. Original music was composed and conducted by Walter Schumann. Supporting cast included Virginia Gregg and Diamond and Junius Matthews. Dick Joy speaking.


So the top five things to do in a lucid dream based on almost a decade now, probably over a decade of my experience and research into this topic. They're not in any particular order, the things I like to do. So the first one is dissolving the lucid dreaming space and creating an experience of pure awareness. I've only done this once or twice but when you do it, it's pretty life-changing. The second one is just to go into a lucid dream, get really clear and aware, maybe do a few reality checks, find a computer and then search for my channel on YouTube and then just keep subscribing. Number three is telekinesis and flight or flying. This is probably my favourite one of the five. Maybe number two is a close second but basically with telekinesis you're controlling objects with your mind. So you might be lifting a car, you might be like creating a city or even just throwing some nightmare character out of the way. It's really good, it's really fun, it's a good way of avoiding nightmares and it's kind of like a superhero movie but except you're the superhero. Flight in a lucid dream is a bit more difficult because you need to be meditating every day, you need to be really focused on the moment and being aware and present in the moment but also it's a lot to do with your internal blueprint of the world. When you fly in a lucid dream you're challenging what you know deep down to be true which is gravity is real. So when you challenge that in a lucid dream your whole subconscious mind is working against you. That being said I do have lots of tutorials on this on my site, on my channel, just go and check it out but flying and telekinesis definitely one of my favourite things to do. And then number four is interacting with aliens, extraterrestrials, otherworldly beings and things of that nature. This is an interesting one because when you do that you really are bringing in a higher awareness into your dreams and you're actually communicating with different dimensions, different things. It's a bit of a rabbit hole. So when you start exploring this stuff it will open your minds to a lot of different things. Very interesting. I would not advise you to do that if you're a beginner. If you're a beginner just focus on the basic stuff. You know just fly around explore the city, talk to people, whatever.  So leave a comment down below letting me know what your favourite thing to do in a lucid dream is and I will upvote the ones you like and I'll read out the best kind of top three in my next video. So I'll see you next time.


Hi guys, so today's video is going to be a nighttime nursing routine that I do the night before I have to go into work So I hope you guys enjoy my routine


The moment you sign Manny Machado you are making your team better but you're signing him as we just talked about it's an eight nine or ten year deal and does a team want to make that heavy of an investment it's going to be 30 to $35 million so I think that's what the Yankees are exploring right now and I asked Brian Cashman about the fact that you might sit in that room and maybe there are five people on this side of the table who say sign Machado and then there are five people on the other side who whether it's Daniel Murphy or anyone else who says well we think we have other options that we can go to and Cashman said that happens all the time it's our job to then figure out what's the resolution where do we go and I think this is in such early stages right now Bob I think the Yankees are having those discussions and there might be a voice saying yes let's sign them and there might be a voice that saying listen we don't want to be under that kind of contract for the next ten years yeah and that's the thing I think people look at it and say well if you have that much money out there you don't have to spend it maybe you can put it in different areas now again a stop cap maybe go out and get a short stop or maybe as I mentioned a Daniel Murphy to play second slide towards over till Dita gets back and I think Murphy is an interesting choice I'm glad you brought his name up because you look at what he was able to do in the last 71 games last year coming back from knee surgery he really struggled hit under 200 only had one home run look at what he did for about half a season that OPS is close to 900 he's 34 years old obviously the knee is a concern but he can play second base he can play first base and you're probably going to be able to sign him for two years you also DH him once in a while and the thing about Murphy Bob is he gives you quality at bats the Yankees are always going to be a home run hitting team but you like the idea of filtering some players into that lineup that work at bats that extend at bats and I think Murphy is the type of hitter who does that


Here we are at the house of Mozart. Mozart, for any music lover in the world, Mozart is not a strange name, but the sad story of his life and the fantastic nature of his life is he started composing when he was five years old and by eight he performed or he conducted a symphony. This is only possible when there is a samskara like this that the learning is not from what is around you. The learning is what one has imbibed from elsewhere. So this is what is called a samskara. Samskaric learning is a great significance unfortunately being lost in the modern school education systems but Mozart is a fantastic example of that and within his short span of life he became a you know like the god of music in this region but unfortunately he succumbed to some unknown illness at the age of 36 and nobody knows where he's buried in some unmarked grave somewhere. That's a sad story of who he was but even today anybody who loves music their hearts will flutter when they hear the name of Mozart. Mozart is a master of music not learned but imbibed music.


everyone. Before I get started today, I just want to say who is a Ruby expert? It's in this interview. It's in this session. Okay, great. So this is about Ruby Technical Interviews. My name is Chris Marr and I'm a software engineer at Custom Inc. But I've been doing technical interviews for over 15 years. I started with C++ interviews and then I used to do Java interviews and now I do Ruby interviews. But through all that time, early career developers are always plagued by the same problems during interviews. So you've been learning Ruby. There's a lot of great resources out there. Maybe you're doing a bootcamp or online code school or reading books, but you've been learning the Ruby and now you're ready to start interviewing for your first job. The first thing that's going to happen when you start looking at job descriptions is going to say one to two years of experience, maybe of scripting language experience. And if you don't have any experience when you go into these interviews, you don't have anything interesting to talk about. So how do you get this experience? Well, you build something. This is the number one recommendation. Build something. And don't just build anything. Find something in your life that you're passionate about and build something for that. So let's say you collect Magic the Gathering cards. Build a website and manage your Magic the Gathering collection. And don't just build the obvious thing that's a website showing your Magic the Gathering cards. Do something interesting. Maybe you want to calculate the future value of your card next year. Write an algorithm that's interesting. And when you start doing this, reach out into the community and use some gems. So reach out to the Ruby community and find gems that help you solve your problems. If you only have time to pull in one gem, always pull in device. Every company you interview with is going to be using device. After you've created this project on your laptop, you've been typing away, push it up to GitHub. If you haven't done this before, this is the cathartic moment where you're taking something you've created and you've pushed it out there for the world to look at. After you've pushed it up to GitHub, deploy it to something like Heroku. The reason you do this is to show that you can create something on your laptop and productionalize it and put it out there for everyone to use. Then you send this link along with your resume. And before we interview you, we're going to go look at that link and say, hey, this is great. I really like the way they put together this magic they gather in website. Then we'll say, oh, I wonder how they're calculating these future values. That seems like an interesting algorithm. So put one of these banners at the top and go see my source code on GitHub. And we'll be able to go over to GitHub and we'll take a look and see what you've done.  Same thing with your source code. Clean up the code. Remove any commented out code. Make sure your indentation is nice and pretty before you invite people to come over to look at it. Now, one of the important skills of a developer is to be able to describe what they've built. There's a technique called rubber duct debugging. And this is where you keep a rubber duck on your desk.  And a lot of times the solution will reveal itself during that process. Same thing here. Find a duck and describe what you've built to the duck. Practice describing what you've built to the duck. Then find some non-technical people in your life and describe your project to them. Maybe you can call your parents up. Hey, mom and dad, I built this great website. Remember all those magic, the gathering cards you bought me? I've determined they're going to be worth thousands of dollars next year. Let me tell you how I did it. Then go to a local meetup group and find some technical people and say, hey, do you mind if I tell you about my project I built? See what questions they ask you. So all the learning you've done, the code school, the boot camps, and your passion project, that's going to fill about half a resume. The next thing you need to do to fill out the second half, the best way to do that is to contribute and to contribute to open source. Here's the secret. Even if you don't feel like you know enough Ruby to contribute to some of these projects, every project needs documentation. And you say, well, that's not Ruby. How can that show what I can do with Ruby? Well, actually, if you were able to look at someone else's source code, understand it and then document it, that's more difficult. And if you can create a pull request and work with the engage with the project team to get the pull request pulled in, that's a great demonstration of your abilities. A friend of mine, Kevin, he created what we called the most pendantic pull request of all time. He went around to a lot of big projects on GitHub and explained to them that they're using the EM dash for the range of years in their license instead of the grammatically correct EM dash. Super pendantic, but he got engaged with a lot of project teams. And now he's actually one of the top 10 contributors on Bootstrap. Now you can put together your resume. You have a lot of experience that you can put on it. Here's the secret. Most developers are lazy. And when you come in, we're just going to read straight down your resume asking you questions. So you have the opportunity to construct the conversation before you go in. So put it in, I built this project. I read this book. I did this class. Here's the projects I contributed to. And then you can practice that conversation before you even come into the interview. Speaking of practice, a technical interview is a lot different than writing a movie on your laptop. When you're learning, you're sitting at your laptop focused on the screen typing. Soon as you come into an interview, the first thing we're going to do is we're going to say, here's a whiteboard marker. Please stand up on this whiteboard over here and solve this problem. And if you've never done that, that context switch can be disorienting. So find a whiteboard somewhere and practice solving problems on the whiteboard. While you're practicing, practice solving the problem but also speaking while you're writing. So say I'm going to create this array. Now I'm going to iterate through the array. Remember, the whiteboard doesn't compile. So you don't have to write perfect source code. But don't sit there quietly. If there's nothing more awkward than we're staring at your back while you're quietly noodling a problem. After you practice solving some problems, some writing code on the whiteboard, practice your domain modeling. This is your box and line drawings. This is things like maybe active record models or Ruby classes and how they relate to each other, even SQL tables and how they relate to each other. This is how you, given a problem domain, how would you construct, how would you diagram the concepts? So for example, if I were to ask you, how would you model RubyConf? Oh, well I would say there's a conference. The conference has many sessions. Each session has one speaker. Each session has many attendees. When you start writing on the whiteboard, most people tend to start in the upper left corner. And that puts you in a corner. You don't have any space if you have to make annotations or insert codes. So always start in the dead center. That way you have space all around if you have to make insert annotations on your code.  So you need to understand what the community is doing and where the direction is going. You're already here at RubyConf and that's a great start. And while you're here, make sure you figure out who the thought leaders are and go to their talks. Tenderlove just gave a great talk, Matus talking on Wednesday, or I'm sorry, Tuesday. But listen to these people and if you don't have time to see them here, they get conference. They've been talking all year at different conferences and they're talking about the direction the community is moving. Another great resource to learn about the community are podcasts. There's many of them out there. I'm a host on Ruby 5. Every Tuesday and Friday we give you five minutes of news of what's happening in the Ruby community. But if you only have one to listen to, I recommend the Ruby rogues. They've interviewed a lot of thought leaders and a lot of project leaders and they have an amazing back catalog that's approachable to all levels. Know what's happening. Ruby 2.3, they just went into preview and they're going to be talking about it at this conference. Nobody's really using this yet, but if you were to go into interview, if you know what's happening and maybe you could ask a nice question like, oh what about the new navigation operator that's coming to Ruby 2.3? Are you guys thinking about using it? What do you think about that law of demeanor? How does that work? Maybe Rails 5. Maybe you're looking at, maybe you're thinking about Action Cable, the new WebSocket framework. No one's using that yet, but you could ask them, hey, are you looking at using that? Now at some point during the interview, they're going to ask you an innocuous question like, hey, what code editor do you use? Never ever say, I'll use whatever you want me to use. Always have an answer. You're talking to developers who spend all day long working in their editors, fine tuning them. They really care about the craft and the tools they use for the craft. I can start awards from them by saying, all these vim users over here, tell us why you do it faster than everybody else. So when they ask you what editor do you use, whatever you're using, if you've been using Adam, say I use Adam. I use RSpec. I use Cucumber. Whatever it is you're using, that's the tool as you've chosen to use. I'm open to using new tools, but right now I'm using Adam.  A lot of people put Ruby expert on their resume. I'll tell you what happens.  Let's see how much of an expert they really are. It sets the bar so high that you're going to fail before we even get to the interview.  So what are we looking for? I did a survey of some senior developer and said, what are you looking for for early career candidates? And these are what they said. They said, we're looking for curious minds. People with curious minds. We're looking for people who are coachable. Are they willing to enter into an agreement with a coach and learn and listen from a coach? Are they passionate? Are they passionate about Ruby, passionate about solving problems? And are they enthusiastic? What's the one thing they didn't say? Ruby experts. They're not looking for Ruby experts.  So who's going to conduct the interview? Well, the technical portion is typically handled by engineers. And what are we doing? Well, we're sitting at our desk. We're on our computer, headphones on, we're jacked into the matrix. We're typing. We're doing what we love. We're solving problems. Manager is going to come over to us, tap us on the shoulder and say, hey, we have a candidate. Can you stop what you're doing, what you love to do, and go talk to this candidate over here? And of course we do it. That's part of our job. But we're going to get up and we're going to start walking over towards the room. And we think, what do we like to do? We like to solve problems. That's what we do all day long is we solve problems. Manager comes to us, website slow. If you have a problem, yeah, I'll solve it. That's what we do. And we build things. We love to build things. We like to sit at our computer building things. And we love Ruby. A lot of the senior engineers that you're going to meet with came from other languages, maybe Java.net. And they came to Ruby because they love the community and they love the language. And here's a tip. We want to hire you. Hiring is difficult. It's hard to find people. It's hard to get them into the interview. And it's stopping us from doing what we love. So if we can say, we can talk to you and then go to our manager and say hire this person, then we're done doing the interview portion. We get back to what we like to do. So we want to hire you. Now, when we get in there, I have one hour to decide. Will you help me solve problems?  Will you and I be able to go back, sit at our desk and build the solutions that we've designed? Will it be fun building those? You don't have to know Ruby. I can teach you the Ruby. I had a lot of great mentors in my career that taught me things. And Atlantis always pays his debts. But I have to be thinking it's going to be you and me for five years sitting together solving problems and building things. I'm going to see you more than I see my spouse. And I have one hour to make this decision. So those are what I'm thinking about. But when we come out, my manager is going to come to me and say, how much Ruby does this candidate know? So we're going to have to do some Ruby questions. Every Ruby interview is going to revolve around enumerable. Almost all questions end up being around enumerable. So if you're new to Ruby, make sure you know enumerable. And if you only have time to learn a few things, make sure you know each map and inject. All questions probably will start within each map or inject. But if you have time, because it's so important, pull up IRB, pull up the API doc and just write a little example for each one of the enumerable methods. Because you may find yourself in an interview with someone who's trying to trick you with an obscure enumerable question and you'll be ready for that. If you're in for a Rails job, make sure you know your active record associations. And the three big ones are the has many, the belongs to, and the has many through. Guarantee most questions somehow end up being the has many through or the classic hasn't belongs to many. Now then there'll be a series of questions. These are the algorithm questions. This will be a question like, give an array of integers determine if two of the integers add up to 500. And if you don't have a computer science background, these can seem daunting. They don't have to be. Because there's actually not a correct answer. We don't have anything else to judge you on, so we ask you these questions. And all you have to do is answer them better than the pool of candidates we're interviewing. And there's a good technique to answer any of these algorithm questions when they're asked of you. First thing you do is ask a lot of questions. Make sure you understand exactly what the algorithm question is. Then solve a brute force. Get the answer on the board. Don't worry about any corner cases, just say, this should solve the problem. Then apply the bud technique. Go through your algorithm that you written on the board and look for any bottlenecks. If there's one line of code that's the slowest, that's going to be the speed of your algorithms to try to improve on that. Look for any unnecessary work you might be doing. Maybe each time through the loop you're doing a line of code that could be done once before the loop. Then look for any duplicated work. A lot of times when you're searching through an array, you can remove elements from the array each time to reduce the amount of the times the next loop has to iterate. Know how the web works. A lot of people ask, how's the web work? What happens when you type a URL in a browser? Now be able to explain what happens when you type the URL in the browser, the request response cycle, what happens on the server, the process, is everything involved. And then we come to the hard questions.  Nobody cares how many ping pong balls fit on the bus. The point of the question is to ask you something in a problem domain that you're not used to and how you approach the problem. And there's a simple way to answer all these questions. You say, I have never thought about this. I've never thought about how many ping pong balls fit on the bus. But I would start with the smallest thing I do know. And what's that? Maybe the size of a ping pong ball. I can determine that a ping pong ball is maybe one inch by one inch.  Then you can kind of start estimating how many fit on the bus. Then ask questions about the problem. How big is the bus? How many seats are on the bus? Are there people on the bus? Is the bus moving? That's engineering. If any of these questions, the Ruby questions, the algorithm questions, these hard questions come up and you get stuck, it's fine to say, I'm having trouble getting started on this problem. Turn to the interview and say, could we pair on this solution? Could you start on the whiteboard helping me head in the right direction and I'll pick it up from there? Every developer loves to pair with people. Now, if these algorithm questions, you're still concerned and want to be prepared, there's an easy 700-page book you can read before you go into the interview. This is actually a very good book and she covers things like the bud technique. Now, at no point when you ask a question during the interview, say, oh, I could just Google that. Of course you could Google that. I Google all day long. Most of my job is finding things on Stack Overflow and copying and pasting them over. But that's not the point of the interview. You're the end of the interview when the wrapping things out. Usually they'll turn you and say, do you have a question for us? Always ask a question. Have a question that's prepared. Say something like, oh, earlier in the interview, you asked me if I had experience with Redis. Do you use Redis? What do you use Redis for? Or before I came to the interview, I was looking at your website and I saw this cool JavaScript widget you're using. Why did you choose that? Now, a lot of the comments in this talk are about company and culture fit. And not every company is going to be a good fit for you. But there will be a place for you. And remember, we want to hire you. So thank you. We have plenty of time to answer some questions. Do you have any questions about interviewing, finding a job, resumes? Ruby? Yeah, well, that's a good, typical one. Let me turn to you. Have you ever been asked one of these hard questions? Oh, OK. Well, you can Google for a lot of these. I don't Google for that. But you can find a lot of examples. But that's one of them. I mean, there's a lot of legendary ones like how many wire manual covers round. Typically, there are logic questions like, you're giving a series of light switches, how much you solve a problem. Maybe best if you kind of search around for those. But the point is that they're looking at how you approach the problem, not necessarily how to solve that problem. There's always the one that how many windows are in the buildings in Seattle or that's another one. Right. So she's asking, is there another resource besides the 700 page book on cracking the code interview? And that's the best resource I found for at least the questions. And then you just have to kind of search around and try to solve some of those problems. There's 189 algorithms in that book. So it's kind of hard to know every one of them. But if you just kind of know the series of them and how you would approach each one of those. I mean, a lot of times the questions are about like if you get into nested loops, how do you break out of the nested loops or how to do things ahead of time? And a lot of that comes with experience. But like I said, they're not actually looking for the correct answer. It's how you approach the problem. And that's the secret is just get the problem on the board and then start trying to optimize the algorithm. And it becomes actually repetitive patterns as you do if you've done a lot of them, you'll kind of start to see that it's the kind of the same techniques over and over again. That's a very good question. He's saying in 15 years of interviews, what has been your best source of candidates? There's not one that really stands out. We've definitely hired people coming straight out of college, people with experience. I've hired great people that didn't have any schooling and I've hired people who've had boot camp experience. So there's not one that sticks out. It's really about the person and being able to work with the person and if they're open and willing to learn. I'd much rather have somebody who's coming in enthusiastically teach me everything you can and willing to listen versus somebody who comes in and goes, I already know everything. I've done this before. So the question is, do I have any do's and don'ts for blogging? I would say do blog. It's a great resource. It gives you time to format some of your thoughts and if you put that on your resume, we can go look at your blog and see things you're writing about. It's a great resource and something that we can get to know you even before you come in. And a lot of times if you have a website or a resource like a blog, we'll make a look at things and ask you questions about it. So you ask how many people come in cold? A cold call? Yeah, if we get a cold resume, you have to remember we get hundreds of resumes maybe a day, like we get a lot of resumes. The ones that stand out are the ones who've kind of researched our company and maybe they write a nice cover letter to attach to the resume and to explain why they want to work specifically with us. It really sticks out if you use a cover letter that we can tell that you're just sending into all the companies. But if you have something that's kind of personalized for what we're doing, another secret is to go to local meetup groups. Like every developer and I that work with us, they actually go to a lot of the local meetup groups and you can easily find someone and just make a connection and you can see them in the email when you apply. Yes, that's a great thing. So she's saying if in the cover letter maybe she saw something that she'd like to change or she can improve. And I think that's great. That's you're looking at well, you're solving the problem and us solve the problems that we're trying to solve. And that's a great introduction into the company. I mean, open source is great, especially in the Ruby community. I think it's a big part of our community is giving back. And even if it's just you're publishing your own gems or scripts onto your own GitHub, I think it's important. I feel they most people, especially if it's a senior engineer, we go through all their GitHub projects and like the comb through GitHub. That's actually more important than the resume. So get some stuff up there. Just some examples. It's like your portfolio. Yeah, so the question is about giving homework to candidates before they come in. It's actually interesting because we've just iterated on what we used to do. So we used to come in and give you a cold problem and have you sit down and try to solve it on spend one hour coding. And we found we're getting better results though by sending that out early and say it worked on the problem. And then when you come in with what you've solved, then we can ask you to iterate on we'll ask you questions about something, maybe add an additional feature or something. But we found that we're actually getting better results by sending the homework out. So what are some of the best questions that we've been asked in the interview and how maybe how we can determine that they're going to be the best asset for our team. I really like and that's personal because you're trying to make a connection with the person interviewing you. I love it when someone's asking me what I do, maybe why, how long have I been there and why have I been there so long, what's great about the company, how I work, and kind of so it's just a lot of interest in what we're doing. The question, the worst question to ask are what can you do for me or what are you going to teach me?  But if you ask them if you're asking what we're doing and how the team works together, I think those are fine. Those are the best questions. Just a personal question about what I'm doing, what am I trying to solve? And so she's asking about the length of time of the homework. And we have had debates about that because you don't want to force someone into like eight, nine hours of their own time just to apply for a job. So we're still iterating on that as well. I think the project we give, you can do an hour or two of sitting down and just kind of putting something together. And we don't expect a full blown out solution. We kind of expect based on your skill level the approach that you've taken. But that's definitely something you can ask. If you're given an assignment from any company, especially the HR person, just say, hey, how much time do you expect is reasonable to expect that you put into this? And if a company is expecting you to put in 20, 30 hours, right? That's a lot of commitment. So I wouldn't expect that. So the question is, how do you help if you're the interviewer and your candidate freezes? How do you kind of make them more comfortable? One of the great ways to do that is to kind of just switch. If they're frozen, kind of talking about Ruby, switch. Maybe like, what do they do in the personal time? What are their hobbies? And kind of see how they approach those. A lot of times people have these hobbies that they're real passionate about that they'll geek out on. And then that's actually just as good. You can kind of hear about how like if they homebrew beer, how do you do the beer? Like, tell me all about the process and what's involved. And that's a lot of like engineering and problem solving, too. And then that makes them more comfortable with you. Then you kind of get back to the Ruby and the technical pieces. How do you come up with them? Yeah, that's a hard problem. And I think through my research I feel like nobody, because I've worked with some big companies, too, and it doesn't seem like they, I've never been given like, these are the questions we ask. It's almost like every engineer it's left up to them to come up with the questions that they're going to use. And a lot of people are lazy and they're just going to sort of say, oh, these sound like three questions I can use. And honestly, it's the approach. How the person approaches the problem. So the question is not, being correct with the question is not actually what I'm looking for. I'm looking for how they approach the problem. But I do usually have a backlog. Sometimes I'll interview candidates and they'll say, oh, I've been asked this one before or I can answer it if you want. Or you can come up with another one. So I usually try to have two or three that I ask. But I think for when you're interviewing, the important thing is you ask the same question to multiple people and you'll see the different approaches. And sometimes when I ask, I have a couple of algorithm questions asking, if someone pulls out something that I've never heard before, it really like, it's like, I'm like, this is great. I just had never thought of that approach before. I'll be around the conference. There's a few other anchors here and we can kind of talk to you and we'd love to talk to you about interviewing and maybe give some tips and resumes and things or you can hit me up on Twitter at CMR. Thank you.