Merken

Teaching GitHub for Poets

Zitierlink des Filmsegments
Embed Code

Automatisierte Medienanalyse

Beta
Erkannte Entitäten
Sprachtranskript
and and and and and we can go ahead and get started so you design teaching get help for poets I am
sons I go by K-theory on social media and I'm the lead operation to do a Kickstarter and I'm a terrible dancer this is me dancing horribly in a grizzly bear like the is called degrees code is a Kickstarter award and and the yet I was a little nervous starting at these talks but I feel like once again to see me dancing Paulina grizzly bears see there's nowhere to go but up and the so or a Kickstarter
Kickstarter's mission is to help create a projects on the life of we are a Ruby on Rails application ideas poly know-how works if if you have an idea for a comic book or a film are Gadjah software project you post your idea without with a pitch video and your friends and family and strangers on the Internet pledge money to it that sort of the ultimate way of saying like I want this thing to exist in the world and if you get enough money to to complete the project and then we collect the money paid out to you and you can go on and and a bill the thing you want and In my role as the operation to engineer is my job and passion to make tools and processes that help the engineering team and that the whole Kickstarter organization do awesome work and to that end 1 of the programs that we do it is called get hub for poets
and so super quick outline of what i'm going to cover in this talk and talk about what the upper poets is why it's awesome and useful and beneficial for for our organization and and for your organization's to and how you can implement yourself and yes so jumping right into what they help for poets areas so it's of really quick
class but takes about an hour that goes over how to make a copy change to our website and it's using that they get help browser so sort of be and finding a file that we wanna change changing it committing it making a pull request and it's opened up all step everybody in the organization not just developers and not designers the people that you'd expect to be committing coding like working with a rails that but it is also an introduction for everybody in the company into the tools and processes that the engineering team uses really trying to be and accessible and clear to intransparent throughout the organization of all working on the name get proposed by the way comes from is a reference to like a lot of liberal arts schools at my college at least had this Physics for Poets class and the idea being that it's certain elective class geared towards people who were going to become physics majors but I want to have a just part of enriching their lives they should know something about electromagnetism and the relativity and things like that and so this is the idea that people and there are lots of people in our organizations that are expected to be a doing rails development or working with get help on a day-to-day basis but knowing something about it can really improve the workflow and so that's where the name comes from our own begin a little more into what each of these 3 bullet points entails so you do you lie down over copy change but this is this is so the guy up along browser for those who are familiar with it is a way of just finding files to edit and editing them in committing at all inside chroma a some like that and the great thing about this is there's is nothing to download it or install like you don't have to tell people to open up a terminal you don't have to get clone anything and you're just searching it in your get help repository a lot like in search google or something like that there's something else so the learning curve on getting started and both in terms of technical know-how and like the commands you actually have to run it is very very low but you don't have to run any command you just go to a website and and this can be this flow of finding a file to change changing it and committing it and then making a pull request I see that as sort of the fundamental development loop like that it that is the cycle that even very expect that all engineers and designers and anybody building a product and that is the cycle that you're doing over and over again and it to show that make that accessible for people who and optimal that is a really powerful tool and this this is really helpful agora CST art community service the moral integrity team who who would be a trying to find it confusing parts on the site we we had a poorly written validation or something like that they would use this to improve copy changes also because we're just changing copy like the text and user e-mails or something like that you don't really need to know the Ruby programming at all we don't need to get into a really at all like how Ruby works how rails works this is the kind of thing that you can cover in our work and come away feeling like you have a better understanding and so like I said it's open all staff and what that means a Kickstarter as is we have about 110 employees about 1 3rd of them work on the product either as engineers or designers our product managers and but then means mostly employs a Kickstarter are doing things like H maybe like it you know doing as a recruiting or managing a job postings of things like that do some legal stuff like if we ever upgrade our Privacy Policy or Terms of Use or something like that those are code changes could changes that were really is tax changes that people who have gone through or get proposed class can do and a lot of the community support team is is also at making these kinds of changes but in a much more straightforward way than before we've done this class and it's sort of grown to become apropos poetesses grown to become part of the onboarding process for new employees uh I think it is analogous to how a lot of companies have customer support rotations where every new employee spends a day answering support e-mails because that is a great way to get to know what your customers are a scene when they're interacting with the the product and similarly if you wanna know how engineering how product development team works showing them this cycle of how code like how the sausage gets made is really I opening and often startlingly easy for a for a lot of people who were familiar with that they sort of assume that you're doing a really complicated genius hacker type stuff but that's hard for train Hollywood but if he's a showman like you're doing this really simple thing and is changing some text in some files uh it can it can and it really improve their understanding of how engineering works and right so it's it's that intro to to the tools and processes we have this class this is involved with like how you run tests before deploying to production or something like that so we'll talk about how we have a continuous integration environment but how we test things like you have to if you sign up with a username and password me like submit those username password you'll be logged into the website and similarly will have task on testing things that shouldn't happen like you can have 2 users sign up with the same e-mail address or something like that on we explain that just as much get as you really need to in order to do that development loop which is released to things like commits and branches and if you understand as a command as my God the like of a single change with a message describing why you did that change your file and that's a committee and a branch is just like a list of all these changes are being made throughout history and and any any branch can represent like all the work you've been doing and these branches are safe places for you to do your work without affecting anybody else's work and rails we explain as as a collection of tools for building many websites and we don't really have to go into the nitty gritty of you know how active record works or something like that which is need to show them that the directory lay out most of the copy lives in have user at mailers views from maybe in confidence me files and and this is this is the wave is a great way we've made that the engineering process transparent and inclusive for everybody to kick-start organization so because the poets are going through this process and and they're they're doing this loop we end up in this place where everyone In organization can commit code and a lot of people when they when they hear this other so have this reaction
the what I'm again will be this is pretty
great and if the
system so what happens when you let everybody in your organization commit code and actually works out pretty well and and they're going to go now into
the middle section of why it's pretty awesome you get up for poets
so the biggest reason is it makes are processed more weight forgetting information differ for making easy changes but it used to be the case that our community support team would notice that a validation method is confusing and generating a lot of support tickets and ordered notice that there's a typo on the website of someone I got like you were actually writing in the correct this type of because most of the copy was written by engineers of time they would tell this to the to the VP of community support VP community support would have a weekly meeting with the VP of Engineering who would then say OK uh these are all things that we knew engineered effects and then filed these like really simple changes into our ticketing system so that an engineer can go in like fixed that typo or clarify the error message or something like that so the process is really you know somebody noticing something that they were empowered effects telling their VP VP tells another peak and then that if you like trickles down to the to the people who actually fix the problem and that is just crazy that is way too much process to fix something that anybody that that should be really easy to fix and so you have a poets now just means that the person who knows a typo we notice is that a validation is is written a confusing way they can edit that file themselves put up the pull requests and at the end engineer will I get painted my goal node emerging deployed pretty shortly thereafter words and everybody else is informed but no longer part of the critical path right they they can see what happened but you don't have to wait on your boss to tell you that it's OK to do something and another really great reason if you get up about what's is that it lets you avoid building a CMS and so as you're as you're making these of minimal viable product features and and things like that it is like throwing about there like trying to see if it works and you don't know what you're going to be committed to this long term and there's often this sort of awkward phase of a product of the feature where it might need to become a CMS at 1 point we're gonna be changing it so much that you want other people to just feel the turf fix it themselves and but you don't know the actually changed that much and in our case it's like we lot editorial features where people like staff could highlight different films the comic books or something like that and we have this flexible pages but we're not sure exactly how they're gonna wanna change them or what the rate of change is going to be and having get help for poets like to say well the Jews go in and like Edit this view just like we use Hamilton like camels really easy to learn as just like copying these chance around and if the test passed that means there's not a syntax error and will check it on staging now on its way out the production and it's just a low risk change and that saves a lot of engineering effort in storing all this stuff in a database of summary that we don't really know what the full and life cycle of that feature is going to be the this another way but version control is a content management system and you're just letting everybody uses that thing instead of building your own bespoke content management system alright so those are very practical reasons why you would build this right this is like you saving yourself work you increasing the productivity of the engineering team and the real the really awesome benefits I think are the more cultural value the but the cultural reasons for doing this right but and also but we kind of stumbled into some of these like initialy helper poets was just going to be a Ruby on Rails for poets because we wanted to each so that some people really want on Ruby on Rails and we said we have a Ruby on Rails applicable to show you how it works and and will be helpful and and then people a it was like way too much material to cover in a couple hours like boot camps are 12 weeks long so and you know you just like getting started it with with 1 of those and so it was a ridiculously overambitious to be like I want to spend a couple hours on how about we held that'll get it but what we found was like as we started talking about how get works it was sort of his mind blowing its experience being like you guys have so much transparency in context about every change that anybody has ever done and we ended up just talking about how get pub works all time but so I values here that there were sort of realizing is we wanted to improve the transparency without like the engineering process and units and that sometimes the features that are about to go out and at the 11th hour we notice of you know security liability or a performance gotta something like that it'll be in the pull requests were like well I think this is not really work that well it we gonna carry factors on like that and for everybody on the marketing team to know that that's why this feature is the late at nite because we're building this extra this extra stuff into it and it's great to just happened the part of that workflow so that the transparency and the inclusively part of it and there is also a lot of consensus that is sort of baked into the to the a pull requests cycle that we use which was pretty surprising for how a lot of people vote for how a lot of other departments make decisions and to do so what kind realizing here is that version control is a communication tool and really in the same league of like you're chat or e-mail client that you guys get back that everybody in your organization should have access to chat room everybody normalization has an e-mail address people in e-mail each other that your version control for your for your product is this rich history of why you built everything and how it was built and thinking of it that way it's like of course everybody should be able to see that context it's it's so useful to know that you know the
product was built this way because of these very good reasons that were hashed out in this engineering like in this discussion amongst engineers on a pull request and and why that's not a simple checker like what you think might be a simple change is not actually a simple change and it's really kind of amazing that think that as we work were building up the story of how we build things rule are did have commit through our through or get commit history almost as like this by-product and that that idea that I'll be able to go look back in time and of you have something triggered by memory of why I did it that way and that's really powerful and it was almost like efficient water like a fish water kind moment for me realize like at something of that that David Foster Wallace anecdote about to fish swimming past each other and 1 fish says to the other like a says because the water today and the surface as what's water and is getting at that that thing that's like so ubiquitous to the way you work you don't always realize it's there and and so engineers using version control we are used to this this idea of having this rich context around how we build things and that when other people see that force a community support or a marketing team and there is sort of a mind-blowing experience for them to just know that they can you they have those sorts of tools for their own documentation or something like that on so yep version control is really increasing the transparency that not just the engineering team had over like other teams had with the in G waving engineering team works but it turned out that other people wanted this for themselves so they started making at their own repositories for documentation or for like policy documents of how they would and how they would handle troublesome cases or something like that so these those decisions now have this like commit history in a pull request this'll rich context of the discussion around how or why a particular thing is the way it's and so I I should say to this is called the upper poets but it's really pretty applicable to any version control system and the 1 thing I particularly like about at the the way it did how does pull request is the sort of getting years getting this idea of consensus and as a sort of a political tool for decision making or like a tool for a governing what code is good enough to get in master and to be deployed the production and things like that and you do it by asking in a pull requests and so even beyond the our commit history pull request even adding this even richer context about you know what the discussion is around is not just what the developer says in their polar request but it's like really this dialog between several different parties maybe it's the product manager whose urging like that they're getting something out quickly because it's an important deadline to meet or something like that another a security engineer talking about security trade somebody asking about performance on all this conversation is happening in the pull request and now also because everybody else is it everybody in the organization is is on github we also have a marketing person is in there who can be like tweaking marketing copy up to the last minute as they figure out how they how they wanna position this new feature and another really cool thing make the the other really great thing about pull request is that there is this shared responsibility that's implicit in them but that if things break because at like as a result of you merging your pull request in Anbar and applying it it's not entirely your old at all in fact you know it there we have a pretty blameless culture to and so it's not your fault at all but in any organization that uses pull request you put it out there and you ask people to try out like help you make it better and it really this expectation that you're not like nobody's doing perfect work but we at least expect you to ask how you can make a better and and I see that as like a really mature a mature attitude and amateur way for teams to work on and once other teams the way engineering did that they want to do it themselves so this is some of the cultural reasons why you should do get help for poets the last reason is a really self it is kind of a a a a personal reason for it for you in in their career development this is a great way to increase the impact in your organization and and so as you level up and and progress in your career you'll find that 1 of the things your boss expects of you is the have ever greater impact like you should be able to manage yourself really well then you should be able to improve the way your team works and they should start improving things throughout the organization and in ever greater concentric circles of impact and that the helper poets is really like a few hours of your time at teaching the class getting everybody in here to have organization but answering their questions about how it works and you know merging in deploying the pull request and they're ready to go and it can have a radical change on other departments workflows because it's so much easier for them they make changes on a site like that is now a tool in a tool kit of things they can do and and the it creates this better or attitude around working with this asking for consensus and and expecting transparency in this rich context and how decisions were made and so the final reason to do get help for poets is because your boss will like you for doing it and you will make your organization about right so how
did you get up poets and this is sort of a whirlwind tour maybe like of a media session of like get help for poets is like a Kickstarter and so
the things I explain up front or but how branches and commits work and because it's really confusing to use github . com at all without understanding what a branch or commit is and we explain that the sort of bog-standard rails file layout really be and the important places are apt to use and and at mailer views and your config file if you have a lot of copy in Yemen files but a nice analogy here which I I'm I'm cribbing from my friend Emily re su coat of the class of me and is think of like in college when you when you would have for each semester you have a folder of like all the classes you took an each folder you have like a term paper 1 term paper to so on and so forth and so it's just like this big hierarchy of folders with a bunch of files and I'm and like really that's all our code bases or at the end of the day and and for somebody who's not used to programming like that can be a radically simplified view of of how a code works and another really important thing is this idea of always be learning a lot of people are reluctant to start contributing because they feel like they don't know enough to you to do that and they want a bit like an expert at all the things before they make their 1st copy change and you have to disabuse them of that notion that they're ever gonna feel like they're an expert in all the things and that engineers never feel like that either on this always be learning concept is is pretty important so get some slides but what I found 1 of the most useful things to do in these idea proposed classes is to demystify the development process we we sort of our engineering team has sometimes been glorified as like these really only smart hackers who had a sorta like a communal mind meld with computers and just make it do amazing things but actually we're trying to do the most simple things like we're generating real scaffolding and it it is just not rocket science but we or googling for a gem that does most of the work that we want to do and we're not doing something really clever and so really lowering the barrier to entry like lowering the amount of knowledge that you need to have to get started out I like to talk to have this dovetails with the with the programming of pattern of the and philosophy of dry don't repeat yourself right and that In a macro level this means that if you were writing code to do something that you already written before but that's that's not dry and you would use reuse the code that you've already written and as as a kind a corollary to that it means that you're always writing code to do something that you've never done before if you're writing code to do something that you got it done before you just use that old code and so it's really it's really just get comfortable with the idea of your you're always going to be working at the edge of your comfort level also that it's really OK to ask for help it's OK to ask an engineer and how to do this thing or what this piles borders show you how history works or something like that engineers are spread out all the time from Google and stack overflow I yeah so that's what I go into when doing a gap for poets session I also just wanted to do a really quick wide demo here of what it involves so if anybody else once it follow along too long ago to get back on its last K-theory flesh rails the amount and we'll see how well my networking works many couples issue display the
but and another contrast may not be great but I'm yet so we're looking at a very broad standard Rails application and in this case adjusted like Rails new and then I generated a user model scaffolding and so as the whimsical copyedit that we're going to do I'm going to go to the user listing and we're going to increase the SCO of that page so to find out I know that there's a user listing somewhere I don't remember where there's some search for it sure enough there is active use users index . html that you're being on click into 1 of these line numbers that I want at and so sure enough this looks like HTML is a little bit of magic down here that I'm not gonna worry about because I'm not trying to change that part of so in order to head to add at this any did go from that particular tree back to a ransom hop on the master branch and then I'm going to edit this file and so I wanna be sure that people know as we listen users can't have a sub headed to hear that and and expresses what I like about monoliths so let's say model are of a new audience participation time models are what help me out the rest of the majestic integrated systems alright and you guys are all incurs to make own regressor so now I'm going to have to make this ever committed to a new branch and I'm a describe what i'm changing of CARE ART but this out so i'm changing the user listing and the reason I'm doing this is I'm adding some SEO around model of and then it's always nice to show the emoji thank you are and then we become try to encourage reasonable branch names to you but honestly doesn't matter there so many branches we should just let it go and a never going to be mean tidy just embrace the chaos and so we could leave this Aurora call it something like Rails come only and CEO and now I'm going to propose this file change there we go so we can preview this we should say what we would like to what feedback would like in this pull request and please share yes monoliths are actually majestic and for integrated it and we can have mention just for the and as well as her the great the pull requests and then pretty much done so so in our process where goes from here is we have a support engineer every is sort of a weekly rotating basis of that the person who is trying to stand up whatever bugs come up and basically absorbing interruptions from other engineers and and so do you begin at mentioned in 1 of these people requested just give a quick spot check with the continuous integration set up so you get a nice green check mark on and if all its good it is deployed and it's out on production within a couple minutes are I think since it's good to see some participation on this ball requests of In our our how back to the to the slides yeah OK so that's more or
less what we covered I the there are a couple common concerns that people have when when they think about giving everybody at access to the idea of repo on the most common here is Bill break the site honestly the poets themselves or are incredibly concerned about this in fact I think I even more concerned than engineers and people on the product team about bringing the site of so as a result of that the people gone through the get proposed process tend to be very cautious and they'll ask for help a lot even though they're making up what are from an engineering perspective very trivial changes but just fixing typos J. moving towards around is not going to have a significant impact on on your site the worst thing that we've had happened to it like there is because we use Hamel like indentations gotten screwed up and then we discover that because the test fails and you should be testing of views protect and so yeah these are really low risk changes and the changes that can have a really awesome impact because believe it or not like the copy that on your site is actually a huge part of your product some small copy changes can have a really in impressive effect on how usable and how how usable your priorities and how well it converts and so yet we have not found it to be the case that giving more people to access to our code repository has decreased code quality or has and been a liability for for the website and back has been has been the opposite so other people are worried about security and that that are coded so special and it's so dangerous for everybody else to be in there but I also think this is gonna crap so 1st of all let's say we have to remember that the communication medium right version control is a communication tool this is just like chatter e-mail and there's always a possibility with every communication tool that if that information got out it could be damaging or just like embarrassing and so that's true but it's a it's a trade off the you always accept because chat and e-mail are so helpful to so as you increase your productivity so much there is worth the risk that if somebody had a bad password like all that information we get we and and so there's some like really easy start you can do to improve your security like we have everybody's 1 password so that they have like strong of unique passwords for every website they use you can require a two-factor authentication for lots of important stuff and also another reason I think is kind of a bad reason about excuse to not do this is that your code is not a trade secret your code is not that special but most Rails apps that I've seen are just mostly rail scaffolding up with some small customisations and a bunch of gems that you're requiring like that is the majority of the cleverness that goes in the most rails applications we are not trying to make clever genius apps we're trying to build simple things quickly and if R code was ever it was it was ever leaked to the public or something like that we like to think that another rails engineer would look at it and then get all yeah that that's how I do it like it is the obvious thing to do that we're not trying to be clever we're just trying to make it using obvious but as a as a result like it's really not that much of a security liability I also so few protects here and these these are a something you should also have a place just to make sure that you're all your bases are covered as in terms of security and site reliability and stuff like that some sort of putting on my like obs at me like we have to see these things and so you should like poets should know that they're working and they're all that when working in a get branch it's really their own space to do whatever they want to experiment is what much as they want but without affecting anybody else's work on any other feature and so anything they did that anything we do in I get branch is not gonna break things for on production our break things for other developers and you have lots of tests and continuous integration to catch lots of obvious features that if something managed to slip through all this was your process of of and checking it on a stage in environmental production environment and pass all your tests and things like that is really a breakdown in the engineering process and I think it's kind of my problem to have a better process so that would make sure we detect these things before they get out if they get out and it's and it's still but it's probably going to be a really minor but and and yet another safety Jack is that we have deployed whoever's doing deploy scans exactly what commits applying dislike sanity checks that these are what they expect to be the point so if you if a poet like forgot to create a branching committees directly on master that goes into our chat room and everybody wants you to make immediately and we'd be like Hey did you mean to do this is a really important chains and he's a get out right away if novel just reverted and we can say OK let's go and do this through the pull requests for of on another
thing that we've got a lot of questions about is what it means you thumbs up inTable request and it means something positive obviously but that doesn't mean like you convert this that is ready to deploy in order that me and like I like the idea that you're doing this doesn't mean that I like this particular feature but I'm not sure about the moment like in the media like the implementation of you do like just the direction that the features like this is actually a surprisingly rich Imojean's and so yeah talking about like it is often just means that like it it could really depend on the context whether this mean like actually going to deploy or on disliking grab example requests i so as I want to show you guys to some of the poets are a Kickstarter but
these are a bunch of our employees who are who have gone through the hub for poets and had been gone on to the make several commit simple requests but in particular 0 yeah so there I do a little odd wrapping through forget history and realize that of the US seventies or so people have gone through get for poets class but 29 of them have gone on like actually make a pull request that we then emerge in the master and we have a total of 11 hundred commits and which I am I think super amazing like that is 11 hundred times a developer didn't get interrupted to do a trivial copy change and that's a lot of time saved and that is a lot of people who have an improved workflow that's a lot of people who were able to to fix a solution by making a change to the website instead of say making a support macro but to to reply to a customer support to get this so actually there's a whole anecdote behind that but there was a confusing part of our video uploader where the editors support meaning they're saying like all the creators writing and interviews that they're not seeing the video preview where when they're expecting to because they go well the test code and maybe I were getting enough these tickets mediation is write a macro so we can like were required of them more quickly and then they realized like weight we can just edit the HTML around the video uploaded and it just put a message being like would I show you preview on the next page don't expect to see a preview here really even get those support take in the 1st place it is like a big win for a contextual help and and longer term there is like we wanted this to the engineering widely wanted to show the preview but just complicated front and stuff and like asynchronous that it was we want to build a better we were going to get to it soon and and just adding what 1 div tag of inline help was a bit when a drastically support cut support tickets and article about a 3rd from the right is carol and she has alone made 312 of these comments and she's on the copyright in the now because she's so awesome at editing and and making a copy of really pop and there's an interesting scenario where a copywriter started recently in our 1st project was to and to get familiar with that with all the the tone in the copula site she looked for any place where we didn't work using a serial comma like which is which is grammatical pattern where if you have a list of 2 or more things like through more things get like have a common for the final item she felt very strongly about adding those because it clarifies what we're talking about and but so she goes through it makes all these pull request like each 1 fixing his 0 come up and this is like the 1st week on the job and you never use Rails never used up before and it's pretty great a that of yeah OK
so the final thing of like here is a slide I don't know how well this shows up because it because it's on a light background and they have this is an example of some of our colleague and on making a pull request and is a especially doing a great job with the MOT here a lot of people chiming in right after she makes a pull request is really good it's a good feeling when that other engineers are congratulating you on a job well done for making a 1st requests and because they have this
because I'm up here I get to sort of talk about how weird abstracts as a wall or thing that I would like to happen and and that is that coding becomes more like writing and that what I mean by that is writing is a tool that we spent thousands of hours learning how to read and make written language like is not something that comes naturally to humans at all it's something we work very hard at and it is worth doing all that because it's so useful these written language it's such a powerful way to communicate ideas and is not you know starting a few generations ago using computers and software is going to be just as important as this is something that people spend thousands of hours learning how to use software learning how to use computers but it's something that is worth to invest in that time because you use it all the time it's so helpful and and so I see get help for poets in a small way helping us along that path of giving of of making or an Indian but like the software development process a bit more accessible and giving people another tool in the toolbox and as they're trying to solve problems through to try to solve it by adding our code base and you so the the final couple slides here are examples of the kicks from the Kickstarter homepage that things that have been made by poets so this
is an actual screenshot of the Kickstarter . com homepage at 1 point we have these big like Eurographics where were calling out and the things that we want highlight on the site so this was about films that in helper poets collapse and we play around with editing these that Eurographics in a pretty fun and when to collect so behind the camera here is is that our caudalis so here's what the poets came up with the another actual hero graphic that we had on the page and the home page was a island video games at the bottom that says 87 7 thousand Kickstarter backers help produce the viewer being broken age and Boeing Catherine got a hold of this it turned into a donors but those points scheme where 87 thousand dose going center Catherine and the call action button says and more those points uh the final 1 and highlighting library projects but the way they do have proposed actually ends up often is people everywhere chaos the but so that the and my
talk of I I'm K-theory online social media you hit me up there I also have time for some questions and actually the myriad of but come up and ask you questions and just in case there is some people here who were really wanting and some poetry I'll leave you with some bad gate poetry I think all of the size microphones in some of the
Nichtlinearer Operator
K-Theorie
Minimalgrad
Hypermedia
Vorlesung/Konferenz
Code
Hilfesystem
Videospiel
Nichtlinearer Operator
Ruby on Rails
Prozess <Physik>
Selbst organisierendes System
Familie <Mathematik>
Kartesische Koordinaten
Quick-Sort
Videokonferenz
Internetworking
Font
Font
Flächeninhalt
Software
Prozess <Informatik>
Vorlesung/Konferenz
Projektive Ebene
Optimierung
Klasse <Mathematik>
Punkt
Prozess <Physik>
Browser
Adressraum
Drehung
Datenmanagement
Prozess <Informatik>
Radikal <Mathematik>
Vorlesung/Konferenz
Kurvenanpassung
Hacker
E-Mail
Softwaretest
Sichtenkonzept
Prozess <Informatik>
Gebäude <Mathematik>
Biprodukt
Dienst <Informatik>
Grundsätze ordnungsmäßiger Datenverarbeitung
Datenfluss
Ordnung <Mathematik>
Verzeichnisdienst
Programmierumgebung
Message-Passing
Web Site
Wellenpaket
Selbst organisierendes System
Stab
Wellenlehre
Klasse <Mathematik>
Mathematisierung
Physikalismus
Term
Code
Demoszene <Programmierung>
Task
Loop
Datensatz
Bereichsschätzung
Datentyp
Spektrum <Mathematik>
Passwort
Softwareentwickler
Inklusion <Mathematik>
Optimierung
Hilfesystem
Demo <Programm>
Fundamentalsatz der Algebra
Datenmissbrauch
Open Source
Relativitätstheorie
Browser
Verzweigendes Programm
Kontinuierliche Integration
Validität
Mailing-Liste
Elektronische Publikation
Datenfluss
Quick-Sort
Integral
Basisvektor
Dreiecksfreier Graph
Mereologie
Stab
Abstimmung <Frequenz>
Prozess <Physik>
Punkt
Adressraum
Versionsverwaltung
Hinterlegungsverfahren <Kryptologie>
Homepage
Client
Einheit <Mathematik>
Speicherabzug
Vorlesung/Konferenz
E-Mail
Phasenumwandlung
Prinzip der gleichmäßigen Beschränktheit
Softwaretest
Extremwert
Sichtenkonzept
Prozess <Informatik>
Datenhaltung
Computersicherheit
Gebäude <Mathematik>
Kontextbezogenes System
Biprodukt
Bitrate
Entscheidungstheorie
Verbandstheorie
Benutzerschnittstellenverwaltungssystem
Rechter Winkel
Chatten <Kommunikation>
Garbentheorie
Information
Fehlermeldung
Telekommunikation
Web Site
Gewicht <Mathematik>
Selbst organisierendes System
Content Management
Stab
Mathematisierung
Gebäude <Mathematik>
Term
Iteriertes Funktionensystem
Code
Knotenmenge
Gewicht <Mathematik>
Canadian Mathematical Society
Soundverarbeitung
Videospiel
Ruby on Rails
Booten
Validität
Telekommunikation
Physikalisches System
Elektronische Publikation
Content Management
Quick-Sort
Mereologie
Dreiecksfreier Graph
Wort <Informatik>
Normalvektor
Resultante
Web Site
Subtraktion
Umsetzung <Informatik>
Ortsoperator
Momentenproblem
Selbst organisierendes System
Wasserdampftafel
Klasse <Mathematik>
Mathematisierung
Versionsverwaltung
Euler-Winkel
Hinterlegungsverfahren <Kryptologie>
Code
Erwartungswert
Datenmanagement
Arithmetische Folge
Flächentheorie
Endogene Variable
CMM <Software Engineering>
Radikal <Mathematik>
Vorlesung/Konferenz
Softwareentwickler
Hilfesystem
Dokumentenserver
Computersicherheit
Telekommunikation
Schlussregel
Biprodukt
Kontextbezogenes System
Software Development Kit
Quick-Sort
Entscheidungstheorie
Konzentrizität
Polarisation
Forcing
Benutzerschnittstellenverwaltungssystem
Festspeicher
Hypermedia
Ablöseblase
Demo <Programm>
Bit
Prozess <Physik>
Gemeinsamer Speicher
Schreiben <Datenverarbeitung>
Kartesische Koordinaten
Computerunterstütztes Verfahren
Homepage
Übergang
Netzwerktopologie
Mustersprache
Stützpunkt <Mathematik>
Vorlesung/Konferenz
Kontrast <Statistik>
Hacker
Gerade
Analogieschluss
Feuchteleitung
Sichtenkonzept
Datennetz
Biprodukt
Rechenschieber
Automatische Indexierung
Ordnung <Mathematik>
Makrobefehl
Standardabweichung
Rückkopplung
Klasse <Mathematik>
Mathematisierung
Zahlenbereich
Keller <Informatik>
Hierarchische Struktur
Term
Code
Interrupt <Informatik>
K-Theorie
Informationsmodellierung
Endogene Variable
COM
Softwareentwickler
Optimierung
Konfigurationsraum
Hilfesystem
Demo <Programm>
Expertensystem
Green-Funktion
Verzweigendes Programm
Kontinuierliche Integration
Indexberechnung
Mailing-Liste
Physikalisches System
Elektronische Publikation
Quick-Sort
Integral
Programmfehler
Pufferüberlauf
Mereologie
Resultante
Telekommunikation
Web Site
Prozess <Physik>
Punkt
Mathematisierung
Versionsverwaltung
Implementierung
Kartesische Koordinaten
Term
Kontinuierliche Integration
Raum-Zeit
Code
Computeranimation
Richtung
Perspektive
Stützpunkt <Mathematik>
Kontrollstruktur
Vorlesung/Konferenz
Passwort
Softwareentwickler
E-Mail
Hilfesystem
Soundverarbeitung
Softwaretest
Sichtenkonzept
Prozess <Informatik>
Dokumentenserver
Computersicherheit
Kontinuierliche Integration
Verzweigendes Programm
Web Site
Kontextbezogenes System
Biprodukt
Quick-Sort
Arithmetisches Mittel
Verkettung <Informatik>
Rechter Winkel
Chatten <Kommunikation>
Hypermedia
Mereologie
Authentifikation
Information
Ordnung <Mathematik>
Repository <Informatik>
Programmierumgebung
Portscanner
Web Site
Bit
Gewicht <Mathematik>
Total <Mathematik>
Mathematisierung
Klasse <Mathematik>
Term
Code
Division
Computeranimation
Videokonferenz
Homepage
Prozess <Informatik>
Mustersprache
Vorlesung/Konferenz
Softwareentwickler
Hilfesystem
Softwaretest
Mailing-Liste
Kopula <Mathematik>
Rechenschieber
Texteditor
Rechter Winkel
Mereologie
Verbandstheorie
Projektive Ebene
Makrobefehl
Faserbündel
Message-Passing
Brennen <Datenverarbeitung>
Bit
Web Site
Prozess <Physik>
Punkt
Formale Sprache
Gruppenoperation
Computerunterstütztes Verfahren
Code
Viewer
Homepage
Computerspiel
Software
Unordnung
Minimum
Programmbibliothek
COM
Vorlesung/Konferenz
Softwareentwickler
Codierungstheorie
Abstraktionsebene
Spieltheorie
Systemaufruf
Nummerung
Quick-Sort
Rechenschieber
Generator <Informatik>
Projektive Ebene
Faktorisierung
K-Theorie
Verknüpfungsglied
Code
Physikalische Theorie
Hypermedia
Stereometrie
Vorlesung/Konferenz
Computeranimation

Metadaten

Formale Metadaten

Titel Teaching GitHub for Poets
Serientitel RailsConf 2015
Teil 30
Anzahl der Teile 94
Autor Suggs, Aaron
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/30709
Herausgeber Confreaks, LLC
Erscheinungsjahr 2015
Sprache Englisch

Inhaltliche Metadaten

Fachgebiet Informatik
Abstract Discover the benefits of training your entire organization to contribute code. Kickstarter teaches GitHub for Poets, a one-hour class that empowers all staff to make improvements to our site, and fosters a culture of transparency and inclusivity. Learn about how we’ve made developing with GitHub fun and safe for everyone, and the surprising benefits of having more contributors to our code.

Ähnliche Filme

Loading...