Merken

Implementing the LHC on a Whiteboard

Zitierlink des Filmsegments
Embed Code

Automatisierte Medienanalyse

Beta
Erkannte Entitäten
Sprachtranskript
and it more and more and of the good and the but I think it's time we really the I have to tell you something funny before we get into this part I decided it would be cool to have my 5 daughter do the illustrations in the pictures for this had talked so you know how about halfway through I realize and giving all these weird requirements and making the do all these things you know to take my talk so I think I'm actually become that interviewer that we all hate and might be a problem set of data as the talk with an appropriate grain of salt guess and lower in a talk about coding interviews today and as a how to
pass through the interviews with the eyes that kind of thing and uh the reason I wanted to do this chart is basically this week greater here this is laid out the name from the fact by red and and it's true right if it's true it's sad we and when I see you later up well we doing interviews and what we do in our day jobs there's a bit of a disconnect there and we don't spend enough time talking about the viewing side so let's talk about the interviewing inside as do the coding interviews I'm familiar with that their in wide practice you now take on problems where they do the some challenge the work on with without a time limit and technical interviews where you you work with 1 of their employees often involves some kind of parent is probably not right normal-appearing white you do on the job mostly it's them watching you struggle to figure out some problem or as something like that maybe providing a with a bit of insider at questioning and there's a white board interview where programming on a white border or in a Google Doc or something like that and then there's i've seen auditions where people have you I do some real work on their and application either on your own or with help and then they did you based on so I wouldn't know red ink and as part of my job I do migrate take homes I do technical interviews as so I see a lot of work doesn't work and that and then I think I have some tips that I can give to help you I get past those problems and it's kind of the my interest to do so right right if our Director of Engineering comes to me and says with higher 8 new people this year if I could find a bunch of good programmers say like in May then I could take a few months off for many of you right so that would be just great man the OK this talk comes with caveats for sheer as 1st of or you know there's no guarantees I'm going to tell you the major mistakes to avoid and and and and you try raises chances interviews but it's well known that the mood of your interview where their level of training they've had no right these are all things that are out of our control so it's definitely a numbers game I'm sorry about that I wish it wasn't uh but it is and that's that's something we can fix that from this talk I'm also not gonna judge the various interviewing practices as I think there's things our industry does well I think there's things plenty of things our industry does not do well as and that's a great conversation that have but that's not this conversation there was a really good talk yesterday called hiring people with science if he didn't catch that talking should probably watch the video gets in the some of this and it was really good and also I am not familiar with every kind of interview out there as for example the whiteboard interview I've never taken were given 1 so I won't have much to offer their aside from general texts and finally if you do everything I tell you to do in this sort of thing to take a lot of time in your head spouse and family as problematic be that happy with you so it's up to you to apply apply the appropriate filter and how much you should you hearing and that for your needs OK caveats aside with start where you can do
on the worst thing you could do is show up to the interview and then start trying to pass the interview right and you need to do some things to get ready and to help you swing the odds in your face and the 1st 1 is to study interview questions are pulled from a well-known subset of Computer problems so that if you are more familiar with those kinds of things you're going to do better in the interview and had it may not be stuff that you are using every day in your job so if that's the case it's really important that you can have both this back in your brain these are some of the concepts I think the the most useful I've cross-checked this list with a couple of different sources they all pretty closely agree in i've tenure as but my own interpretation on it as I kind of arranged it so that as the most important step is at the top and to the left so you can work your way this way you have time I think it's probably the most helpful and that these are things that you need to know and it's not that I I think you will be asked to implement a binary search directly but sometimes just being familiar with and these concepts can help you in that in some ways interview from will talk about so I stuck big O notation in the upper left which might seem a little bit surprising and anything it's more important than people give it credit for this is a tool for our understanding how long your codes and wine or how much memory it can be used up in the upper bound and I would say that I think they can actually help you solve problems easier and we'll get into that in just a 2nd but take a look at these lines is the difference and common complexity is for algorithms and it's a big difference if you're on that green line that slowly climbs up where whereas if you're on that orange curve which is almost a straight right to the top right and that's a big difference in understanding the difference between these can be very powerful so I think big O notation kind it's a bad rap I think we think of it as a formal tool that only matters when where you know documenting something on or things like that I didn't think that cities I really do believe it's useful even in a programming and and maybe even more especially in interview styles program so was stickup take a quick big O notation grades let's see if you remember and how much you remember so how many give you a few seconds to think in your head of what you think the complexity of this code is and then I'll show you the answer checked yes is when it is they and then it's when you're going to write the 2 important that's the right here we stand over the data the entire set twice summing once and multiplying the 2nd time and that would be to end but in big Oh notation we dropped constants and non down here terms so it's just picking right like here I have at this 1 this is the classic recursive algorithm and the Fibonacci sequence do the seconds chain I this 1 a is big O to the and I wanted to show this 1 because if you run into recursive algorithms there is a formula you can use to figure it out so this line right here is the important 1 it's however many branches there are and then however and raised to the power of the debt you have to go down so in this case we're making 2 recursive calls 1 with i minus still along with i minus 1 and we have to go down however many had head steps in the sequence is based on the parameter of the past and so and that's a formula for figuring out workers utterances OK this one's more complicated so super bonus points if you get this 1 the right they thing going on I'm sorry and London at this kind of part of it this 1 is big O B log B plus a lot being which seems horribly complicated right effect but it's not as quite is a is challenging is that works I think if you break it down so this is the sort of break here where the users are hybrid sort and like most good so it's it's beyond behavior and long and so that's the 1st term in the hands of the and then the 2nd term is the answer comes from these 2 lines were scanning over a and for each element in a were doing a add binary search on the so the dependent work you have to multiply and together so that's where the log becomes round there's sort is independent from that so we have enough and in don't feel bad if you don't know these reading that is a Tobago quiz when I was preparing for the sort of Michael 1 our again the this plenty of himself right it's not right everybody gets he's right all the time but as studying them will give you some advantages I might try to make the case for that now so let's do this this is a classic interviewing problem I pulled it from a list and interviewing problems it says given 2 sorted arrays finally elements in common the erasure the same link in each has all distinct elements so they're most obvious solution to me is something like this where you would scan over 1 of the sets and for each item in the set you would see that than the other set and this 1 is I believe O and squared and because as with a running over the set you can potentially after run over the other set to the entire set for every i right so and this is the brute force approach and at the just looking at the problem and knowing what I know I know that this set sword and I know the distinct and no they're the same size if i use all of that knowledge and I'm guessing there is a linear solution right I suspect that's the best I can do that I can walk through this at 1 time and know what items are shared and I can try to figure that out on my own and that might look something like this this is kind of the way I just described it where I can scan over 1 said and collecting answers meanwhile I can keep a pointer into the other set and bump it along whenever you know I pass a certain size this and I know I won't have to
consider those anymore but this is hard for me to think about and I don't know if I got it I think it's linear but I'm not entirely sure and anyway it's it's it's complicated right but if you're familiar with things like big O notation and how we measure complexity that there's easier ways to get to a similar solution so we could do something like this 1 we just run through this at 1 of the sets and loaded into an and then was run through the other set and check it against that we make 2 passes but they're both in many right so we're still at the linear algorithm and we added hash insurgent check but that's constant that right so it's a non down dominate term we end up dropping it anyway so this is a linear solution and it's much easier for me to think through this 1 and realize it so the that's my argument that this can be a tool to find easier solutions to problems really can't help user playing with these things and many tests include some assertions that well uh give you inputs and then measure the time your code dates line and fit to a curve to see which category it falls in add this to the little small I apologize for that you're not missing much those this is the recursive algorithm I showed you earlier for the Fibonacci sequence this 1 is pretty much the same thing except it's inside a default block for Ruby hash which gives us memoization right once a values being calculated to be in passion it's just catch and this is the dynamic programming version so if memorization is coming at the problem from the top down as with caching then dynamic programming is coming at it from the bottom up and building up to the correct answer you just 3 different ways to calculate same thing so that we can test these with many test using many test benchmark you get these assertions and you can say I expect this algorithm to the exponential the problem is this algorithm is so bad it quickly overwhelms Ruby and so I had to change the inputs it down to a set that would keep it something that can execute in a reasonable amount of time and and in this case I really had to check the inputs down maybe not a lot of data points which is kind of bad but that's kind of a bit of feedback to if your algorithm overruns Ruby quickly it's probably not a great algorithm right so that you can kind of still use that as a guideline this is the memo as version he it's linear still a little bit more than repeated handle but they only had a trend that and the range of tiny bit I knocked off the highest category and then the dynamic programming version repeated handle just which kind of surprised me at the highest version is happening mostly in C you would think I expected that when you do better I didn't as so the there's some tools you can use to play around with algorithms in line with the mostly get a different problem this is not a coding problem into brain teaser it says you have 9 balls data the same weight and 1 is heavier you're given a balance which tells you only whether the left side or right side is heavier you find the heavy ball interest to users of the scale I give you a couple of seconds said to think about this and see if you can come up with a solution so I think the hundred units of ideas my daughter illustrated this 1 for a so if we put 3 balls on the left side and 3 balls on the right side you can lead 3 balls on the table if a website heavier it's an asset at the right time to be it's and that's that if there even if it's on the table right the way we've narrowed it down to a set there we can do the exact same thing was 1 ball each and find that people right it this is part of what I was saying when being familiar with certain concepts can help you get to interest to interviewing problems so this problem I think you are more likely to figure out if you've played with things like binary search or merge sort is kind of similar to those principles right dividing mad and categories and and managing those key categories individually so that's what I meant by just being familiar with the concept even if you don't specifically have to implement that our no matter where you need a practice these kinds of problems I wish there was a better way but there's not and my favorite site for doing the practices and sources and I O that their problems are a fairly good size it pretty consistent and that while you solve on the you can produce paid in the feedback mechanism on the site so you know help improve your code at same time you need to get to where you can solve exorcism style problems in under an hour right if ever technical interview that's an hour and a half maybe not decoding the entire time so really got be solving these problems in under an hour the and you can also use my older site will be quiz . com there's more problems there but the less consistent so you can take it with a grain of salt exorcisms probably more useful if you really wanna go at all in this book is over 600 pages of programming interview problems it is this guy and exploitation and general advice it gives the readings to the problems discusses the answer is that this is the deep dive right here if you go through this and that where you're familiar with problems that you're pretty much ready for anything I think so the and this if you wanna go that far another thing I would recommend it's not about as solving problems specifically neither have some open source and you wanna be able to send it add to the hammer did it to them had in your cover letter is a great place to put it when you're applying but I it doesn't have to be a big gem a small gem is fine effect I prefer it when go to look in your open source of I don't have to read through thousands of lines of code figure out what's going on so that you know having even 100 line gem is great focus on things like having a great read me clean code was small methods test documentation the kind of stuff you do in your day-to-day job hopefully and that's what's great right is that they get to see you as you are in your day-to-day Just right which is something they don't necessarily get out of some of the things in the normal interview process so this can help OK that's enough of
a parent what about we actually get to the interview these are the things you should do while you're there actually taking the challenge so 1st of all it's Goals your main goal is not to be seen as a bad hire we have lots of information that tells us that good hires a dude but bad tires are really bad right it's not just the performance of the bad higher itself they dragged down the performance of other employees so it's like the multiplier right it's bad so companies are optimizing for avoiding bad virus which is done this is actually what it means if you can avoid making major mistakes you look a lot better than a lot of other people so really wanna try to just avoid making major mistakes there should be a primary goal OK and I'm going to be some tips for things you can do to do this number 1 and you have to read
this carefully you must understand the problem you are trying to solve or you're not going to solve it well right this is pretty straightforward if you're being given the problem verbally you have to ask clarifying questions into you really have your around it this 2 reasons for that 1 you have to understand the problem we've already talked about that bitch you if you are taking the problem from someone else then your goal is to get that person on your side and it begins with this conversation right as acting out the problem of understanding we're trying to do and that's what you're trying to accomplish here and I want you will make this mistake the basic mistake I when I interviewed ignorant at a very nice dynamical Michael guys who interviewed me give me a problem to reimplement set time out in the in the very 1st thing I did was like I said time had reactor we're talking about my described of an intense air and started writing a test about and however I can attest the different threads going out and Michael lot up in JavaScript there's no direct searches as this 1 you know as stream of execution I waited a like that 0 yeah that's different so yeah everybody makes this mistake you have to understand the problem the same the following directions this is important have lots of people don't do this it's a little bit shocking and here I'll give you a pop quiz of stating but if the problem says you should use get should you use getting yes or no yes this is really an idea right if they said that and add some reason for something you're trying to get out of the way maybe they're looking at how you structure your comments have been there or not not and perhaps the checking the amount of time it took you between 2 minutes they can see that uh but anyways they have some reason for telling you that you should do it here's another 1 of the major if the problem says no 1 has ever solve this using rails should you use Rails yes or no no home why did not everybody's say no yeah way of thinking in your head you haven't I to be the 1 right is that you were thinking you're not going to be the 1 I'm sorry to break it to you and don't need to be wide tie 1 of your hands behind your back why make it harder weighted you try to just solve the problem well that's easier for the heat and so don't do it don't don't do that stop and think as programmers
we are just you know will jump way there were start coding it'll come to is we can always refractive right and yet OK but if you're on a time limit you get user time well right and using 5 minutes to make a plan so use the rest of your time better that will pay you back right it's OK to build the plant it doesn't mean you're doing waterfall development if you build a simple playing a game so get and in fact I feel like this is important enough that we need another hilarious tweets OK go yeah that when you're doing
this thinking you have to think out loud and this is tough for some people and I really feel for you I know that some people struggle with this loudmouth let me with no problem with this we can stop that but as some people do struggle with this if you do you need a practice and in front of the mirror you can have you in your friends interview each other you can do it with a spouse of another whatever until you get the hang of it you must externalize that internal monolog I interview multiple people that dental partner search thinking and they just the stop talking and try to be respectful of interval time and then I'll ask a question like can you tell me which are considering and I have actually had people see me hang on I just can't figure this out and I might here and I'll have to figure out whether or not the 1 higher you based on where you're figuring out never have a hard so at EU we have to know where that is we have to be understand it and when you're doing this work in magic words these there's some great magic words that out of my 1st thought is whatever after that it almost doesn't matter I don't have the 1st part a terrible idea right it was the 1st slide and then I did the want to walk through the process and see if it's good or bad right and considering the trade and love hearing this 1 hopefully you know by now that all of programming is straight as and you're always you 1 thing versus the other thing if you tell me you're considering the tradeoffs and then you make a choice that I wouldn't have made I don't hold that against you I know that you know that there were trade-offs evolved and for whatever reason your experience told you this pattern was better that's fine by me you're considering 100 I might still go back to this all programmers right so they don't like hopefully you know that to an end we you break things around and naturally satisfied with that maybe I'll come back when I have a better idea if it's great to hear that they you know that that you're aware of that the you've got to improve it but right now you're going to get on with solving problems these 3 magic words are the most important I don't know say it apparently this is very hard for people to say that have very odd if I can make you say I don't know in an interview it's a huge black mark against it as far as I'm concerned and it's think of the 1 thing you know really really well maybe better than me but maybe it's Ruby programming maybe it's add Goals and maybe it's paying you Warhammer 40 Gamages I don't get 1 thing you know really well the think about how much it in Norway's you to listen to other people talk about that thing when they clear we don't know where you know right that is you in every other subject OK if there's a lot of things we don't know you need to get comfortable with admitting that great that there's no reason not to say that there are things interviewer doesn't know right is if you just say I don't know it's not that hard said I don't know yeah is my head a school I wish I didn't have to have this slide and there's by as much I we interviewed a candidate as to why has and doing a E as CSS re-creation of a page on a site that happened to include a woman model and they were making sexist comments about the woman model as they work please don't do that In an interview on the job and birth and just don't right we want to know the other personality and a sense of humor that would be great but please keep it appropriate if you are a five-year-old deciding which dessert you're going to have is the hardest decision of all and if you're given an interview problem there's a hard part in the middle of the core of the problem it's a search a sort and algorithm had that thing that does the work transformation of data the interesting bit that's the part may want to see you do start they do that 1st this is the most common mistake I see make in solving problems they read the problem in think 0 yeah I knew where they were doing with so assembling elaborate object 3 doing all this set of word data a beautiful UI which times up that's what they submit you know they didn't do that problem that you get to that thing if you run out of time you wanna with no you did they think right the important that you know you can always say I added to the data import that's like to lines of CSP you whenever you know but you want to have worked on the interesting part so scary thing also while you're doing that really interesting fired because you're faking out in hard-coding decisions from the UI go ahead and make it a test case it's the same thing it doesn't cost you any extra time you can test their success case you can test for couple of education is and here's that killer secret no 1 does this no so this is a massive advantage and it doesn't cost you any extra tap you don't need to test the whole thing when you get to the data important you I whatever drop the testing that's fine but when you're doing that quarter back at the beginning testing you will work amazing no 1 does this it's a great secret I promise avoid dependency to it right it must some problems specifically says you're working with something they into view problems of such a scope that there is the simple problems they're not the kind of thing where you need to drag out rails don't do that they don't want to see that they want to see if you can think through a simple problem they wanna see if when the sales team ask for a certain reported are you going the of the takes and data demands around and come up with right that's what they're looking and also don't use Rails means don't use rails and it also means don't try to recreate whales and then use that and this is the best it wrong scope wrong scope you off the map rate and keep it keep it simple the along similar lines right Lester I feel compelled to point out that mad about this picture because my daughter was not following directions and told a job ones and zeros so what is this bottle and with if I told you have become that interview you know that when we don't but I in my defense I used to this picture I have another 1 without the butterflies and use about and seriously don't go play and you have to keep your solution small enough that it doesn't overwhelm me to go through if I crack it open and 500 lines of code and the 1st thing it does is fire up the lecture and runs and stuff through that hindered opens up to a brighter My has the body glazed over and over here would you did his that you're again you're off the map you're in the wrong stuff with the ignore the bonus challenging don't do it it's not 1 thing it's a trap and then hits from bird it's it should have an yeah I don't do it it has a problem challenges be had they often involve extra words you probably have to do more data him for REDD right semester you I here is the insidious part when you read it you think 0 I'm a right my solutions so that when I have time and come back and already set it up for the bonus challenge kay you're not gonna end up having the time so you're not going to come back to what you did is you made the main problem hard bright and dark do it ignoring the bonus challenge it's not worth it if you do that part of testing the core it's worth 10 times the points of the bonus challenge just test the core bit from the knowledge challenge this is good news for you when you read the words extra credit you can interpret them as i think completely ignore this it's great it's like that and manage the time can exist for
several different reasons have 1 might be that the company wants to know where you can do in a certain amount of time and other might be that they're trying to keep you from sending you know massive amounts of your time to something that they land that provide minutes and I know that right so there's lots of different reasons time limits can exist you don't know what reasoning they have for using it so if you're working on a problem you close in not go ahead and submit we have at the time limit then if you wanted to go for finish it if you're you know 30 minutes over the time limit rapid up descended into and say you know have a problem I D 1 and find that less than the 1 in the handle this other case and here's within that feel free to ignore the paper they did you write is made will you submitted on time that made Oracle without 1 but have for me I will always great the way you want can meet for me knowing that you wanted to finish the problem means way more to me than what you can do in a specific time so I had that as and you it can't hurt please go ahead and and finally if you are taking the interview face-to-face you need a practice your text editing skills get good at and this is a biased but when people watch you use in your text editor and they see you using shortcuts they think that you work with code all the time that you develop these coping mechanisms that and you've practiced it and so you you should come out looking better are more prepared you don't need to know every whiz-bang featuring the editor if you're like me and use Emacs that's literally impossible and I won't live long but had you needed just pick 5 it doesn't matter you won't have that much time show off that many anyway make sure 1 of the ones you pick is multiple cursors or macros because these are while features right whenever you see somebody multiple predators and macros yeah well ahead of betas changes tending the onset of using of right so it sticks with you and just make sure you have some some editing skills to show off yeah you probably won't work all of these in the everytime from that's OK at interviewing is hard for everybody that's kind of the point right they're watching you struggle with the problem they want is you stress it's supposed to be hard and that everybody else is doing that to break you're not competing against the problem you're competing against the other candidates right so avoid the major mistakes here were pretty good compared to those other can and so it's OK Brittany tough review work over these things and practices things I believe they will increase your chances and these retirement about what intervenes
had and thank you
all know the the the this this
Menge
Mereologie
Umsetzung <Informatik>
Rekursivität
Computeranimation
Gradient
Zahlensystem
Algorithmus
Kontrollstruktur
Gerade
Metropolitan area network
Array <Informatik>
Güte der Anpassung
Optimierung
Konstante
Menge
Forcing
Rechter Winkel
Festspeicher
Login
Pixel
Lesen <Datenverarbeitung>
Folge <Mathematik>
Subtraktion
Wellenpaket
Teilmenge
Hash-Algorithmus
Unrundheit
Kraft
Whiteboard
Mailing-Liste
Fibonacci-Folge
Spieltheorie
Endlicher Graph
Vererbungshierarchie
Modul
Soundverarbeitung
Tabelle <Informatik>
Algorithmus
Tropfen
Raum-Zeit
Verzweigendes Programm
Gasströmung
Binder <Informatik>
Whiteboard
Array <Informatik>
Gamecontroller
Programmiergerät
Bit
Punkt
Familie <Mathematik>
Kartesische Koordinaten
Element <Mathematik>
Computer
Komplex <Algebra>
Zahlensystem
Videokonferenz
Übergang
Prozess <Informatik>
Kurvenanpassung
Quick-Sort
Parametersystem
Interpretierer
Element <Gruppentheorie>
Systemaufruf
Programmierung
Quellcode
Linearisierung
Teilmenge
Verkettung <Informatik>
Datenstruktur
Message-Passing
Maschinencode
Programmierung
Zahlenbereich
Kolmogorov-Komplexität
Term
Ausdruck <Logik>
Konstante
Inverser Limes
Biprodukt
Optimierung
Zeiger <Informatik>
Hilfesystem
Leistung <Physik>
Schreib-Lese-Kopf
Beobachtungsstudie
Binärcode
Zwei
Mailing-Liste
Gemeinsamer Speicher
Quick-Sort
Inverser Limes
Keller <Informatik>
Warteschlange
Mereologie
Binder <Informatik>
Brennen <Datenverarbeitung>
Term
Bit
Punkt
Prozess <Physik>
Versionsverwaltung
Rekursivität
Komplex <Algebra>
Binärcode
Computeranimation
Homepage
Zahlensystem
Softwaretest
Algorithmus
Einheit <Mathematik>
Maßstab
Prozess <Informatik>
Maschinencode
Minimum
Kurvenanpassung
Default
Figurierte Zahl
Gerade
Benchmark
Bildauflösung
Caching
Softwaretest
Parametersystem
Zentrische Streckung
Merge-Sort
Exponent
Datumsgrenze
Kategorie <Mathematik>
Rohdaten
Ausnahmebehandlung
p-Block
Quellcode
Ein-Ausgabe
Exploit
Linearisierung
Konstante
Menge
Twitter <Softwareplattform>
Rechter Winkel
Fitnessfunktion
Tabelle <Informatik>
Lesen <Datenverarbeitung>
Lineare Abbildung
Rückkopplung
Web Site
Maschinencode
Hash-Algorithmus
Gewicht <Mathematik>
Term
Überlagerung <Mathematik>
Open Source
Spannweite <Stochastik>
Gewicht <Mathematik>
Fibonacci-Folge
Hash-Algorithmus
COM
Optimierung
Ideal <Mathematik>
Hilfesystem
Soundverarbeitung
Algorithmus
Diskretes System
Open Source
Zwei
Gasströmung
Gemeinsamer Speicher
Objektklasse
Fokalpunkt
Summengleichung
Mereologie
Normalvektor
Computervirus
Umsetzung <Informatik>
Programmiergerät
Diskretes System
Zahlenbereich
Optimierung
Computeranimation
Richtung
Streaming <Kommunikationstechnik>
Multiplikation
Rechter Winkel
Vererbungshierarchie
Richtung
Thread
Information
Schreib-Lese-Kopf
Objekt <Kategorie>
Maschinencode
Programmiergerät
Bit
Web Site
Mereologie
Punkt
Prozess <Physik>
Kreisfläche
Automatische Handlungsplanung
Transformation <Mathematik>
Eins
Richtung
Homepage
Informationsmodellierung
Softwaretest
Algorithmus
Spieltheorie
Prozess <Informatik>
Maschinencode
Mustersprache
Inverser Limes
Optimierung
Softwareentwickler
Figurierte Zahl
Gerade
Auswahlaxiom
Schreib-Lese-Kopf
Softwaretest
Sichtenkonzept
Codierungstheorie
Güte der Anpassung
Ähnlichkeitsgeometrie
Automatische Handlungsplanung
Bitrate
Quick-Sort
Entscheidungstheorie
Mapping <Computergraphik>
Rechenschieber
Objekt <Kategorie>
Twitter <Softwareplattform>
Menge
Rechter Winkel
Ein-Ausgabe
Mereologie
Speicherabzug
Wort <Informatik>
Software Engineering
Kraftfahrzeugmechatroniker
Schnelltaste
Subtraktion
Maschinencode
Punkt
Betafunktion
Mathematisierung
Cursor
Computeranimation
Inverser Limes
Eins
Texteditor
Multiplikation
Schnelltaste
Rechter Winkel
Makrobefehl
Inverser Limes
Punkt
Normalspannung
Makrobefehl
Cursor
Videokonferenz
Computeranimation

Metadaten

Formale Metadaten

Titel Implementing the LHC on a Whiteboard
Serientitel RailsConf 2016
Teil 32
Anzahl der Teile 89
Autor Gray II, James Edward
Lizenz CC-Namensnennung - Weitergabe unter gleichen Bedingungen 3.0 Unported:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen und nicht-kommerziellen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen und das Werk bzw. diesen Inhalt auch in veränderter Form nur unter den Bedingungen dieser Lizenz weitergeben.
DOI 10.5446/31527
Herausgeber Confreaks, LLC
Erscheinungsjahr 2016
Sprache Englisch

Inhaltliche Metadaten

Fachgebiet Informatik
Abstract If you apply for a programming job, you may be asked to complete a take home code challenge, "pair program" with another developer, and/or sketch out some code on a whiteboard. A lot has been said of the validity and fairness of these tactics, but, company ethics aside, what if you just need a job? In this talk, I'll show you a series of mistakes I have seen in these interview challenges and give you strategies for avoiding them. I'll give recommendations for how you can impress the programmers grading your work and I'll tell you which rules you should bend in your solutions.

Ähnliche Filme

Loading...