GitHub Universe 2017 - Featured Sessions, 25 Oct 2017

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Opening Keynote - GitHub Universe 2017

Description

Learn about what's new in the GitHub Universe from Chris Wanstrath, Miju Han, and Kyle Daigle.

About GitHub Universe:
GitHub Universe is a two-day conference dedicated to the creativity and curiosity of the largest software community in the world. Sessions cover topics from team culture to open source software across industries and technologies.

For more information on GitHub Universe, check the website:
https://githubuniverse.com

A

♪ (jazz music) ♪.

A

Welcome to github universe.. This is my third time here, and every year I come in and I'm like, "oh,. I know what it's going to be like.", but how amazing is this?.

A

This place is so incredible., it's so great to see so many of you.. Thank you for joining us..

A

I want to start by just giving a huge round of applause and to thank you, to, specifically,, the github events team and everyone involved in pulling this off.. Thank you so much, everyone..

A

This is going to be a really great couple of days.

A

(applause) and it's already started.. We had a great partner day yesterday;. We got tons of events going on., no matter what you're interested in, or what kind of software you're building,.

A

There's someone here for you; there's something here for you.

A

so,, please enjoy it, explore,, ask questions.

A

We're all here, together. so,, I want to again,. Thank you all for coming, taking time out of your days.

A

And weeks to talk about software, talk about the github universe,.

A

Spend some time with the hubot and the octocats..

A

This is always a special time of year for us.

A

october is when we started working on github.

A

and actually,. This year is a little bit special,, because we first began working on github in october of 2007.

A

So, next friday,, the 19th, will be the 10-year anniversary of our very first git commit for building github itself.

A

Which is pretty amazing. unfortunately,? It's a default rails, app import.

A

So, the commit itself is not that interesting.. I think it's says like "default import" as the commit message., but it's really the content that counts, right?

A

or I guess more importantly,, it's the journey.

A

and where we've all come together since then--. That's really amazing.

A

2007,, I know some of you maybe weren't born then--.

A

But it was a very different time in the world..

A

Twitter was just a baby bird,, not the social media monster.

A

That it is today. only a few people in the world had iphones..

A

I think android still had a keyboard.

A

so,, smart phones and bringing computers with us everywhere--.

A

That was called a laptop back in our day., but things were changing.. The world was about to go through--, or at least the u.s.--, a recession.

A

And we were still recovering form the dotcom bust,.

A

But things were different., open source was really starting to catch on,, and this is before github.. It was a real power in the industry..

A

Software was becoming cheaper, more inexpensive..

A

The cloud was starting to become more than a thing in the sky,.

A

But a way to talk about using other people's computers for your own purposes. and thing were generally becoming more accessible to people,, whether it was building a business, finding a community, or just working on something on your own.

A

github,. I think, didn't start any movement.

A

We were a part of a movement that was beginning around 2007.

A

When I think about the early days of github,, I think a lot about the software projects that inspired us,.

A

And the philosophies that those projects had and what we brought in to our own product., we were using open source heavily by the time we started github.

A

I grew up on open source.. I was a heavy, heavy sourceforge user for a long time.

A

And-- I love sourceforge. rip.

A

But a huge fan of open source,, I learned about linux,.

A

I learned about all these things that people just put online for free,, and I learned how to code that way., but more importantly,. I learned how to think about software that way..

A

There were three philosophies that we talked about a lot in the early days of github, that we were inspired by projects.

A

Like rails, projects like django, new programming languages,.

A

That put the developer front and center, that thought about ease of use and accessibility and sort of getting out of the way.

A

so,. The three things that we used to say were "developers first.".

A

Obviously, we're talking about developers., but it's important because it doesn't mean developers only..

A

We wanted to build github as a platform that people can jump onto and use.

A

Hopefully, other people could use it that weren't developers,, but primarily,. We were building this thing for the people using it,.

A

Specifically, for software developers, and not for any other audience or agenda.

A

Why was that important? well, obviously, a product for developers, you think,, should be built for developers.

A

But it didn't feel like many were at the time., and my favorite software to use were projects like rails, and projects like django. things that were explicitly built by and for developers..

A

So,, why not build a development tool,, a commercial one, even,.

A

With that same philosophy, behind it?, the other two are just approaches that we took based on.

A

These sort of software workflow tools that we used, as well.

A

One was reducing friction, and one was lowering barriers.

A

We wanted to take out friction in your workflow,, whatever that may have been. whether you have ten open source projects that you're jumping between,, maintaining every single morning, and it's just a lot of meta-work on top of the actual coding.

A

or whether you're working in a big enterprise.

A

And you have the compiling joke where you have to take a coffee break.

A

Every time you try to build or commit or review code with someone., we wanted to remove that friction,. So you can really get into the zone, really get into the flow, and focus on the unique problem. You're solving,.

A

Which isn't drinking coffee while your code is compiling or the build is running. the lowering barriers? One is a little bit selfish, I think., but I had a hard time getting into software..

A

I had a hard time getting into programming.. I don't have a lot of patience., I'm stubborn. and so,. I had many false starts trying to become a gaming programmer when I was a kid, trying to find a school that had a great course for me.

A

That I would really click with. and many times,. I just didn't think I would ever become a programmer,, because the tools I was trying to learn, they seemed impossible.

A

and it seemed like you had to be a lot smarter than me, or have a lot more experience than I had to get to use them.

A

in many cases,. Some of that was true,. Some of the tools were inaccessible,.

A

Not through any purpose,, but because the person that wrote it was writing it for an audience that had a certain skill level., they made certain assumptions about it. git was this way. git was very hard for me to use..

A

It was not really focused on ui,. It wasn't built for a web generation.

A

It was really great at what it did,, which was a distributed version control tool that came out of the kernel community for a group of people that collaborated through mailing lists, and have it down to a science..

A

One of the biggest software projects of all time was built--.

A

Git was built to help manage it..

A

I've not worked on the biggest software project of all time.

A

And most of my projects are not the biggest projects of all time.

A

so, git at first,. I wanted to use the power.

A

I believed in the vision. I loved the idea of social coding, of this idea of not having.

A

A canonical technological center of development,.

A

Where the gold master is or the server lives., but having that be something social-- having that be something decided that people pass around and talk, about.

A

linus's kernel is the real one,, because that's the one that gets put to press,, not because he flipped a certain config or he has a special piece of software..

A

It's because that's the address people go to.. I wanted to be a part of that world,, but I had a hard time setting up ssh,. I had a hard time setting up my vps slice,.

A

Or whatever we were using at the time. and I had a hard time collaborating through mailing lists..

A

I grew up on aol and message. Boards, and the internet.

A

I wanted to use the web to collaborate. I'd already signed up for and quit facebook a few times by that point.

A

So, for me,, I had a hard time getting into all these things, getting into git,, and what we saw was something like rails,, something like django,. A lot of these dynamic scripting languages like php that were becoming more and more popular and less of a joke, I think, at the time, was. This is a way for people to get in..

A

This is a way for software to become more accessible..

A

This is a way for people to get to the real meat of software. Development.-.

A

Which, at the end of the day,, isn't the coding,. It isn't. The typing,.

A

It isn't the compilers--, this stuff's all awesome and it's super important. at the end of the day,. It's what you're building and the effect it has on the person. You are building it for..

A

We are all builders. we're all creators. and software and technology, and all these tools,, including github,, are super, super important.. We can't lose sight of why they matter., because they help us do something.

A

either for ourselves or for someone else.. They help us have an impact.. They help us make something better or maybe worse, but hopefully,. That's unintentional.. Software is a means to an end.

A

and the more people we can invite into that, the easier we can make it to get to that end,.

A

I think the better the world would be for all of us,, the more powerful software will be, and the brighter the future will be..

A

We were not thinking about that at the time, we were thinking,, "I want to use git,, and I just can't." I'm almost going to give up. so,. How can we make it easier?? How can we make it more approachable??

A

How can we take a cue from this movement,? This developer, friendly movement,.

A

This tool-focused movement, and how do we bring that into the products that we love, and the products that we use everyday?.

A

So,, we never thought that github would be this big,.

A

Because that community seemed niche at the time., this idea that open source was going to produce software.

A

That massive enterprises were going to use., even though linux, in 2007, was the biggest thing ever..

A

It still didn't seem real that for someone like me,, I could have an impact on a company like an ibm or a facebook, or a stranger across the planet that was building something real.

A

Again, I used sourceforge., I knew the power of open source., but there really was a barrier and a divide between what seemed to me.

A

The real projects--, the linuxes of the world.

A

and the things I was working on,, which some of them--- maybe they were little companies,. Maybe they were little app ideas,.

A

Maybe they were the world's 500,000th blog software.

A

Didn't matter. I wanted to tinker with that stuff;. I wanted to share it with the world.

A

and a lot of people did too., but we just didn't realize how many people really wanted to get into this movement,.

A

This developer-focused movement. at the same time, we started talking about software, is eating the world.

A

And as we know,, software is powered by developers,, but the real surprise, I think, was how many people.

A

That resonates with, and the power of software.

A

Continues to grow today., maybe I'm just preaching literally to the choir here--. We all know this., but the point I am trying to make is we never thought github would be this big.

A

and that wasn't about thinking about our own ambitions, or our own abilities,, but we never thought there'd be so many people.

A

That believed the same things that we believed., we should've, right? because focusing on people,, focusing on reducing friction,, focusing on lowering barriers, and building great things--, that all sounds wonderful. and so,. Why you're here,? Why I'm here,? Why we're able to have.

A

Such an awesome space like this,, why the github community has grown so big, and people have heard of us--.

A

It's not about the founders and our three philosophies.

A

From 10 years ago, as much as I really like-- list of three and these ideas.

A

it's about all of you. github is a business, right?. It is a product;, it is software,, but what is code that doesn't run?.

A

What is a social network with no one on it, right? github is about the people,, it's about the community., and I don't just say that in the way, "thank you for signing up.".

A

The reason people go to github is to meet you, is to use your code,.

A

Is to learn and to get better.

A

when people think about github,, they think about the things that they can do with it, and all of those things come from other people., whether it's reviewing code,, whether it's finding a mentor,, whether it's finding a new job, or an open source project..

A

All these things come out of you., it's all about the people that are on github and sharing together.

A

And we take that very seriously.. We talk about the community, a lot.. We talk about the open source developers;. We talk about software developers,.

A

But what we really mean is what we're thinking about is how to connect you., whether it's your software to one another,, whether it's your ideas to one another,.

A

We believe in that power, because we're you too., we came from the same world..

A

A lot of github employees are github fans first and foremost.

A

They learn to develop software on github and then came to work for us.

A

We are a part of this community.. We use github everyday, as well.

A

And I love finding new projects on github that I can use in hobbyist projects,.

A

Or I can just learn and see something new..

A

The future of software is very bright,. Obviously.

A

Because I think the future of humanity is bright., maybe not a popular thing to say right now,, but I'm an optimist. and I've seen the negative side effects of technology,.

A

But I've also seen the positive side effects of technology.

A

and it's really amazing;. It's really inspiring.

A

and the scale that we're at right now is just the very beginning.

A

A lot of us were developers before github.

A

some of us,. I think, have become developers after github., but many of us were developers before github.

A

time marches on.. What we're thinking about now are the next hundred million developers, for whom their expectations, their ideas about collaboration, their demands of what it means to learn,, build software, work, together,.

A

It's going to be a lot more imaginative,, a lot more creative than someone like me, who grew up in the world of aol aim,.

A

Before something like git., we can see this in the numbers. so,. We have 67 million repositories on github right, now,.

A

Which is pretty cool,, but it doesn't speak to the fact--. This isn't 67 million linuxes,.

A

As we know. there's all sorts of projects., we have little ones.. We have big ones. they're growing at a rapid rate..

A

I think what this speaks to is the scale of collaboration on github,.

A

Which, I think we all know, is pretty huge and still growing rapidly.

A

We get over 50 million people to visit github.com every month,.

A

Downloading code, reading it, looking for help--.

A

All of the things I listed before. there are millions and millions of unique people visiting github.com everyday,, which means that the programming community, the software community, it's a lot bigger than I think anyone has ever imagined.

A

there's over a million and a half teams on github,.

A

Groups of people,, whether they're businesses, community groups,, even churches, non-profits-- everything.,.

A

Over a million teams using github to build software together and collaborate. some of the biggest companies in the world, and maybe someone starting a company right here during this talk, hopefully,, putting it on github, right?.

A

We have a huge number of students that are using github, from actual classrooms,, like harvard, berkeley-- teaching computer science, using github, to people that are hobbyists, and they're using github in their free time to learn., maybe they're, making games with unity, or just trying to figure out how compilers actually do work.

A

over a million students on github.. I think I said this last year,, but when I was a student,, I pirated most of the software that I used.

A

so,. If you're a student, and you want to use github,, it's free., you don't have to pirate anything. check out the student developer, pack.

A

we're going to cut that from the video.. I didn't pirate anything. (laughter).

A

So, we're about building software.

A

and one of the most key parts of building software is obviously the text editor.. If you haven't, checked out atom already,, it's our open source, collaborative text, editor., it's hackable., it's all written in javascript, coffeescript..

A

You can get inside the internals, html., there's tons and tons of packages out there. over 2 million people are using it every single month.

A

and I think the best part of atom is that it's an open source project.

A

The features of atom are great.. What it can do is great.. The price tag is really great., but I think the future is the brightest part about atom..

A

It can be anything., it can be wherever it needs to go, and it can always adapt to what's happening,, because it's an open source project, and if it can't, we'll fix it, we'll do something,, we'll change it--, that's the nature of open source., it evolves and it grows. so,, I'm extremely optimistic about atom's future.

A

and if you haven't checked it out, there's been some really cool releases lately, like the atom ide.. So there are--, we have this platform called electron,, which is pretty cool,.

A

If you haven't checked that out. it lets you build desktop apps locally, using web technologies similar to atom.

A

So, there's 404 registered on our electron directory.

A

Which is sort of poignant in a way,, because we don't know how many electron apps there are out there.. We think there's thousands of them.. We know companies use them to build internal apps, really quickly..

A

Remember the days of building an internet app really quickly.

A

Using rails or something like that, spinning it up., a lot of companies are now moving to something like electron,, where they can just distribute the package.. They have a server.. It's a really easy web-like experience for building something internally.

A

so, 404, not found.. We really don't know how many are out there., but a lot,. I think.

A

we've had over 100 million pull requests merged in the history of github., which is pretty amazing., not just created, right?, there's probably been a lot created that haven't been merged., I'm guilty of the not clicking the button in many cases., but over 100 million pull requests have been merged.

A

Since we wrote our pull request some time in 2009,, 2010,.

A

Which is really remarkable,, but my favorite stat is how many people are creating their first pull request every single day.. This goes up every year,, which is great, right?

A

right now,. It's actually closer to 4,000.

A

so,, not 4,000, new pull requests,, not 4,000 new projects--.

A

4,000 people everyday create their first pull request.

A

Collaboration is growing.

A

And this is probably my favorite--, I mean just because it's a big number., I'm pretty sure those zeros are right.. Over 1.5 billion commits pushed to github this year.

A

Past 12 months, 1.5 billion., there are more--, that's more than there are grains of sand in all of-- no,. That's not true at all., but it's a really huge number,, like 1.5 billion commits.

A

And obviously,, a lot of them are rolling back previous changes.

A

And whatnot,, but still the activity is growing--. It's astronomical..

A

I first saw this number,. I thought this was all-time on github..

A

I just can't believe the scale of what's going on right, now.

A

I like to think these numbers are big, because network effects,.

A

Our business model, talks like these--, I'm sure you're all signing up.

A

And creating more repos,, but I think at the end of the day,, the core of it is this stuff is useful.

A

You're building things for other people; you're having an impact.

A

people go to github because they can get something out of it..

A

It benefits them;. They get a cool piece of software;, they find a job--.

A

These are good, things., they're, useful. and so,. It grows. people see, and they do it more..

A

What we may forget is it hasn't always been this way.

A

When open source started,, it was called free, software., it was in the 80s.. There really wasn't an internet as we think of it today., and the problem was that you would get a piece of software that you would pay for.. You would own it.

A

and if it would break, you're out of luck., you couldn't do anything with it;. You couldn't change it.. That was very frustrating to a lot of people,, especially folks who thought it's your property,.

A

You should be able to do whatever you want with it. so, free software came out of that and other ideas, where, now,, with free software,. I get some piece of software,.

A

It breaks, I can fix it. of course,. I need to have the skills.. I need to have the knowledge., but I own it,. I can do whatever I want with it. free software pushed that forward..

A

What they never could have predicted was the impact that the internet had on free software and open source..

A

Free software came a lot out of ideologies and property ownership.

A

But really, the massive thing,, the thing: the reason why we're all here,.

A

Is that it's just not about me being able to fix software that I bought for myself. when I give it back to you,? It goes from me benefiting,.

A

To you, benefiting, surely., but when you post that online, everyone benefits.

A

anyone involved in the project gets something out of that.

A

and not only that--. I benefit from every one of you who contributes to your project, as well. so,. The effect of open source is not just linear from can't fix. It,.

A

To I can fix it, to now, two people benefit, to three people.: it's exponential. everyone in that little community;. Everyone in part of that project benefits.

A

If there was something beneficial in there., open source is amazing for this reason.. It's not just a linear improvement on collaboration..

A

Multiple people can get involved.

A

so, the thing is,. Why stop there?.

A

What if we went from everyone in a project winning when there's some good collaboration, to everyone in the world, winning?.

A

And I'm not talking about participation, trophies. okay?, I'm talking about actual victory., actual benefit, actual improvement..

A

What if, when we collaborated on a piece of software,, everyone got something out of that?. What, if every change you contributed, made all software better? right??

A

What if you didn't just make one project better,, but every project on github?? And what? If, while you were sleeping, your projects were getting better??

A

Not because people were actively, synchronously sending you pull requests.

A

Sitting at their computer, but because the system was learning?.

A

That we're all in this together. and we could passively collaborate with each other..

A

Why not?? We have 10 years of data.

A

you're, all putting out over a billion commits every year..

A

All this knowledge is being shared in the open, in the public,.

A

On github, on open source, in the community., what if we can take the step from me contributing to your project.

A

Benefiting everyone in that project, to benefiting the entire community?.

A

I've never been a fan of "what ifs.".

A

I've read some of those "what if" comic books where batman is an accountant, or wolverine, is actually batman., not interested in that., I'm not interested in what if we could all get better.

A

I'm much more interested in how do we do that and let's start doing that, today. so, we've been working very hard and thinking very deeply about. How can we take all of the data? That's out there--, not just code--.

A

And how can we use it to make everyone better??

A

How can we make not just software better, but developers better too?.

A

How can we benefit each other while we're sleeping?

A

and to talk about that,, I'd like to introduce to the stage miju han from github. miju? thank you., ♪ (rock, music) ♪.

B

Thanks, chris. hello, universe., my name is miju han, and I'm an engineering manager on the data science team at github.

B

and today,. I'm really excited to talk to you how at github, we're preparing.

B

And evolving ourselves for the next phase of software development.-.

B

As chris mentioned, there's a huge amount of data and activity on github.

B

And that can be focused on changing how we develop.

B

That's because github is one of the largest software datasets.

B

In the world., and maybe the largest, even., you have created almost half a petabyte of code.

B

You made more than 1.5 billion commits in the past year, only,.

B

And you've merged over 100 million pull requests.

B

The next phase of our products, and therefore,, the next phase.

B

Of software development in general, is turning all of that data.

B

Into useful and actionable information.

B

We want to capture the collective intelligence, that's sitting inside that data, and bring it back to you to help us all work better and smarter..

B

So, now, I'm going to try to make that less handwavy by talking about how we're going to get there.

B

We want to demonstrate what's possible with our data by showcasing.

B

Different applications of it.

B

The first piece of data I want to talk about is community actions.

B

And that means the things you do, your interests in your social graph.

B

We're using that data to solve one of the biggest challenges on github,.

B

Which is actually finding a project to work on.

B

Now, we know there are several barriers to ramping up to github.

B

The first of which is learning git and github itself.

B

And even if you do know, git, and you do get github,.

B

There's real fear: involved,, like chris, was talking about, when you're making your first contribution to a public project.

B

And that's really why our community and safety teams' work is so important., but still,. It can be really daunting to figure out which projects you want to follow, and ultimately contribute to.

B

And at the same time,, we know that there are a ton of projects.

B

That need more help from enthusiastic people.

B

That's why we're launching a newsfeed that has better highlights.

B

And interesting events from your network.

B

now,, you can see the best highlights from your network.

B

With redesign events in front of a better and smarter algorithm.

B

But the real magic happens in the discover repositories tab.

B

Here, we're personalizing suggestions specifically for you.

B

Though it's not actually magic,, like I said. it's machine learning., it's science.

B

populated by things like stars,, contributions, and followers.

B

We'll recommend you new projects based on your interest, each day.

B

We know that there are some of you who want to go down a rabbit, hole.

B

Of haskell projects all weekend long., we see you doing this.

B

with the discover repositories tab,. We can be your guide.

B

And even if you're, new, and you're, just starting to explore github-- we'll help you find content, that's popular and trending, based on our understanding of the activity of millions and millions of people doing interesting things.

B

On github everyday.

B

We're not stopping there. we're not just going to throw you on to a repo., we're also launching some onboarding call-outs to help new contributors get up to speed on the projects.

B

They've just discovered. for example, we're offering standard ways for maintainers to specifically designate.

B

Which issues are good ones to get started with, or which issues really need? Some extra help.

B

Together,, the newsfeed,, with its improved highlights,, the discover repos tab, and onboarding experiences.

B

Make finding projects to follow and build with, then contribute to,.

B

Easier than ever.

B

So, sometimes,, you want to go deeper into your own interests.

B

But sometimes, you want to do things that are totally different.

B

If you're a front end dev,, you might want to dabble in machine learning, or the opposite is true. Too.

B

We know that one of the core values of being a developer--.

B

This is true whether you just learned to code a few months, ago, or you've, been working as a professional software engineer for decades, is always learning new things, new skills, new technologies.

B

And that's why a second type of data that I want to talk about.

B

Is community curation. information that comes from our community experts themselves.

B

We're shipping an all new explore tab, which is one of the best ways to see what's going on in github.

B

It's a great resource for new and aspiring developers, in particular.

B

To highlight the amazing efforts across our community, part of the new explore is all new collections,.

B

Which are hand curated by our experts.

B

collections, introduce you to concepts like user security, or machine learning.

B

And they connect you to resources, and repos,, and people.

B

So that you can dive deeper., another part of explore is brand new topic. Pages.

B

Earlier this year,, we launched the ability for you to label your repos with topics.

B

Which are either programmatically generated by machine learning,.

B

Or manually entered by you.

B

and you all created more than a quarter million distinct topics.

B

To learn more about.

B

now,, you can not only find projects by relevant topic. Tags,.

B

But you also can learn more about those topics on dedicated pages.

B

And they're community curated. so,. If you want to suggest improvements,, you can submit a pr.

B

To the github/explore repo.

B

These features use the data we have across over 67 million repos.

B

And this is the best explore we've ever built.

B

Together, with our newsfeed,, anyone using github can tap into the wealth of knowledge in the open source community and stay up to date with the latest. Technologies.

B

developers can become more productive at work.

B

And more people can become developers if they want to.

B

So,, the next type of data I want to talk about is probably the first thing you think of when you think of github's data.

B

And that's the code itself.

B

for awhile now,. We've done a lot of the work.

B

Under the hood to help make sense of the various parts of code itself, its structure,, its grammar,, its syntax, and ultimately,, its meaning.

B

Conversational human language,, like english,, also has structure,.

B

Grammar, syntax, and meaning.

B

One way to think about what we're doing with code is to think.

B

About labeling the words in a sentence with their part of speech.

B

Once we have their parts of speech, identified, the process of creating a sentence can become modular.

B

That means that we can start to create sentences.

B

By pairing up verb and noun combinations.

B

We can verify that sentences are grammatically, correct.

B

and then,. We can take a run-on sentence and break it down into more digestible.

B

And more understandable, parts.

B

The first feature to use our semantic understanding of code.

B

Is table of contents,, which launched earlier this year.

B

It allows you to navigate directly to methods and functions and pull requests., but the table of contents feature is only the tip of the iceberg.

B

Of what we can do once we have a semantic understanding of code.

B

We can start stitching code together., we can simplify it., we can evaluate complexity. or perhaps, most exciting--.

B

When you make a pull request,, we can tell you all the parts of your code base that are affected.

B

This type of functionality is going to streamline code review.

B

And the code review of the future is going to look very different.

B

Than it does today.

B

it's pretty exciting.

B

another piece of data we have is code metadata.

B

That's data that provides information about code, for example, say,, the upstream and downstream dependencies of a project.

B

You all know that the code that we write is increasingly connected.

B

And increasingly interdependent.

B

If you start to dig into the stats,, it's pretty crazy.

B

Over 75% of our repos use, dependencies.

B

And of the ones who do, well over half of them.

B

Use more than ten., it is super common for us to see projects with more than a hundred dependencies.

B

That's a norm on github now., it's yet another signal of the strength of our community.

B

At the same time,, it's a lot to manage.

B

So, to help you manage those connections, today we're launching.

B

The dependency graph in javascript, ruby, and soon, python.

B

In our redesigned, insights tab,, you can see both which dependencies.

B

Your project uses, and if you're, a public project, who depends on you in the dependents tab.

B

But it's going to go further than that.

B

We know that once we introduce dependencies into our projects,.

B

There's a bunch of stuff that we have to keep track. Of, right?.

B

So, we're not just drawing the dependency graph., we're also enriching it with useful information.

B

One of those things was inspired by our inaugural open source, survey.

B

You told us that open source users, value security and stability.

B

Above all, else. and realistically,, we know closed source users, value that too.

B

and in the open source survey, 58% of you responded.

B

That you believe, open source to be more secure.

B

But we all know that security is not a feature of open source.

B

Security is a process-- of always being aware and checking on what's going on.

B

So, we're going to make that easier by doing the checking for you.

B

We're announcing that security alerts are coming soon to github.

B

With our understanding of the dependency graph,, you don't have to scroll through a hacker newsfeed to see whether or not you're affected by the versions that they're announcing.

B

Instead, repo admins can specify a user or team.

B

To manage private security alerts as they are announced.

B

For your dependencies, specifically.

B

And that brings me to the fifth type of data that I want to talk about: today,, which is code, changes or diffs.

B

Sometimes, we learn the most about code when you change it,.

B

Either your code or someone else's code., and we learn even more. If you tell us why you did that.

B

So, we're not stopping with just alerts.

B

we're combining public data sources with output from our machine learning team.

B

To go further and deliver suggested fixes if a known remediation is available.

B

Sometimes public data includes a safe version,.

B

But sometimes we see reputable sources doing the same thing over and over.

B

We want to combine both signals.

B

So that you can help-- so that we can help you.

B

Keep your project safe. and over time,. Our fix suggestions are going to get smarter.

B

And smarter and smarter.

B

We're going to add security alerts and suggested fixes to both public and private repos.

B

and then, we're going to bring the dependency graph with the alerts and the fixes to github enterprise.

B

We know from recent events, if we already didn't know it before,.

B

That vulnerabilities and our dependencies have real world consequences.

B

But apart from that, building, the frameworks for better security management is not just a new feature.

B

It's a platform responsibility for us to make it easier for you.

B

To keep your projects more secure.

B

and our security needs change, as our community changes.

B

for example, javascript is not only our most popular language,.

B

But if you can believe it,, it's also our fastest growing.

B

And at the same time,, we know that for all software, systems, public vulnerability coverage is just a subset.

B

Of the true number of vulnerabilities out there.

B

It's particularly true for javascript for several reasons.

B

first of all,, it's a younger community, and can be legitimately really difficult.

B

To verify exploitability.

B

At the same time,, we know for a fact that there exists lists.

B

Of javascript dependency vulnerabilities that outnumber.

B

The publicly identified ones by at least the hundreds.

B

And that's why the github open ecosystem is so important.

B

Some of our ecosystem partners have deep security, expertise.

B

To keep your project secure,, including data on vulnerabilities.

B

That aren't yet public. you can work with gemnasium,, snyk, or sourceclear. Today.

B

Using their github integrations.

B

as a platform,, it's our job to connect their expertise to your projects.

B

And we can do so much more together than we can accomplish. Separately.

B

We're excited to work with partners like these, and many more with expertise in many different areas.

B

you'll hear more about that. Tomorrow.

B

I want to end by admitting that, even though I describe.

B

These types of data separately and distinctly,.

B

At github,, we don't really think of them, as that different.

B

So, the five types of data: community actions, community curation,.

B

Code, code, metadata, and code changes.

B

They're really a part of one connected piece of data,.

B

The code graph., your actions,, your curation,, your code,, your documentation--.

B

They're all annotations, on top of a giant connected web of software.

B

Or if you want to get technical,, it's a really big, highly enriched.

B

Abstract syntax, tree, or ast.

B

So, our ability to learn and help you walk the code graph.

B

Comes from the relevance and the quality of our data,, and that comes from you., it's quality, in, and quality out..

B

These new features are the first steps of how we can give your data back to you.

B

And to be clear,, we're not talking about launching autonomous coding.

B

On github today,, because autonomous coding.

B

Is an ai complete problem., but we are talking about launching autonomous coding, features.

B

And that is where we believe the next era of development has to go.

B

In the future, we will continue launching data-powered experiences on github.

B

And then, we'll have more data.

B

and then,. We will continue launching better data-powered experiences.

B

On github, and then we'll have better data and so on.

B

You'll start to see more and more of it in our core areas, like code review,,.

B

Pull requests, the insights tab, and even the process.

B

Of writing code itself.

B

Now,, we know the next phase of software development,.

B

It can't happen without really solid fundamentals.

B

Artificial intelligence and machine learning-- they aren't going to revolutionize or take away the work that we all have to do next, week.

B

so, for us to be able to bring you anything actionable from the code. Graph,.

B

We need to fully support developers,, integrators,, teams, and businesses.

B

To share more about what we've been up to in the past year in those areas,.

B

I'd like to welcome kyle daigle to the stage.

B

kyle. ♪ (rock, music) ♪.

C

Thanks, miju. thank you, miju.. My name is kyle daigle.

C

and I'm the director of ecosystem engineering at github., I'm so excited to be here with you at universe., as miju said,. This past year has been about changing the trajectory.

C

Of software development.- we want to lower the barriers to entry for developers to start.

C

Writing code on github, for businesses to start taking in open source best practices,.

C

And for integrators to work in our rich ecosystem and build on top of our platform., it's been an amazing year,, but I have more to share with you. Today.

C

But first, I want to start with sharing the octoverse,.

C

Our yearly update about the github community.

C

every year,, we're impressed by the projects you build,.

C

The people who contribute to open source for the first time, and how much our community has grown.

C

There's a lot of fun stats in this, like how our 100 millionth pr was a documentation. Update.

C

Or how microsoft visual studio code had the most contributors, this year.

C

It's a beautiful, in-depth guide of the state of the octoverse.

C

So please check it out at octoverse.github.com.

C

We're really excited to see what you all do in 2018.

C

Now, though,: I want to share how we're going to help you have your best year on github., and I want to talk about four audiences.

C

community, businesses,, integrators, and developers..

C

But first,, let's start with community.

C

as chris mentioned, github started with open source.

C

We want to make it easier for everyone to contribute to open source code.. We want to help open source contributors,, but we also want to help open source maintainers.

C

and we shipped a variety of improvements in this way., but first up, we have the first time contributor, badge.

C

Now,, when you contribute to a project for the first time,.

C

We'll put a badge next to your name, to signal to the maintainers.

C

That they might want to take a little extra time. Reviewing your pr.

C

A study showed that a quick response within the first 48 hours.

C

To a first time, contributor's pr is one of the best ways.

C

To keep that new contributor in your project., this has been a really great experience for new contributors, so far.

C

Codes of conduct are an important part to ensure that a friendly,.

C

Respectful, and collaborative community grows around your project.

C

In may, we launched the feature to make it easier for you to add a code of conduct to your project..

C

You can pick a template on the left, fill in some details on the right,.

C

And then we create the code of conduct and put it in your repository.

C

Since this launched in may,, we've seen a 50% increase.

C

In medium and large, open source projects adopting a code of conduct.

C

This has us really excited.. I want to give a shout out to the github community and safety team.

C

Who really helped drive some of this adoption.

C

C

But we also want to give you control about your experience on github.

C

And that includes who you interact: with.

C

We've introduced better blocking features to make it easier to manage the people.

C

That you've blocked on github. but also, we'll show you when you go to a new open source project.

C

And want to contribute-- if one of the contributors is someone that you've blocked., it's important, that we make sure you're, comfortable, confident,.

C

And safe, when you start your open source, journey.

C

and better blocking tools is a great way for us to do. That.

C

But it's not just project features..

C

We also built opensource.guide,, which is a bevy of data.

C

To help new contributors and people wanting to start their first open source project. before building a community,, we want to make sure we set you up for success.

C

and so there's documents in here about project governance,, making money on open, source, and the legal side of open source projects,, where you can learn from successful, open source, maintainers.

C

Now, one of the best parts about open source is learning from each other.

C

We answer questions;, we solve problems, and we work together.

C

And today,, we have a new way. You can do that, with the github community forum..

C

We want to allow you to start a conversation,, ask questions, and help one another.

C

with 24 million developers,. You can write your best code,.

C

And support one another in our forum.

C

You can start a conversation with the community and github staff.

C

From across the company., we'll recognize your contributions in the forums. that way, everyone knows you're an important part of our community.. We've been working on this for a while,, because we wanted to make sure.

C

That we got it right., but I'm excited to share that the github community forum.

C

Is launching october 31st.

C

and that's our update for community..

C

C

The github community isn't just limited to open source, though.

C

As miju mentioned, over half of our repositories are private.

C

Whether you write open or closed source code,.

C

Github is the best place to do that..

C

We want to meet you where you are and be the best place to collaborate on code.. Earlier this year, we launched github for business,, which brought many enterprise-level features to github.com-- things like saml, single sign-on,, ssh, authentication,,.

C

User provisioning, and an uptimesla.

C

github for business makes it easier for small startups, all the way up to enterprise companies to get up and running with the enterprise level tools that they expect.

C

and thousands of teams have signed up for business..

C

Speaking of teams,, as chris mentioned, today,, we have 1.5 million teams.

C

Side by side with the open source, community, and just clicks away from buying and installing powerful integrations.

C

From github marketplace., we also have our on premises: offering, github enterprise,, which is used by 50% of the fortune 50.

C

github enterprise, gives you complete control over your github environment,, hosted on your environment.

C

In september,, we released github enterprise 2.11.

C

And 2.11 had three major features that customers have been asking us for:.

C

Geo-Replication,, which allows you to put your instance into distributed data centers with multiple replicas., we'll always give the fastest route to you by choosing the closest server.

C

Governor,, which dynamically adapts, git traffic.

C

so,, if you're doing ci builds, we're not going to stop you from letting a developer, do a clone due to all the traffic.

C

And finally, hotpatching is out of early access.

C

now,. You can take your patch releases, put them into your instance,.

C

With zero downtime. so,, you can put those security releases into production. A lot faster.

C

Breaking down the walls between closed and open source is so important to us. great software. Innovation happens at big companies, like ibm, and hp, and facebook.

C

we'll be talking in sessions today, as well. so, go check. Those out. starting today, we'd like to make it even better on github enterprise.

C

If you needed help, or had trouble with your github enterprise, instance,.

C

We've asked you to put a request in via a portal.

C

but now,. We have another option. I'd like to introduce premium support for github enterprise, customers.

C

Now,, your admin can pick up the phone, call us, and start getting help right. Away., urgent tickets will get a response within 30, minutes.

C

and high severity tickets will get a response. Withing four hours.

C

We're looking to expand this offering in the future., but I'm excited to offer this to you available today.

C

By talking to your sales team.

C

and that's businesses., (applause).

C

It's been a pivotal year for the github ecosystem..

C

The platform is more powerful than ever, with features like our graphql api,.

C

And github apps. earlier this year, we launched github marketplace.

C

At our satellite conference in london., the marketplace has 26 powerful, full feature: developer tools.

C

That are built by passionate teams that want to solve your pain points.

C

In your specific workflows. and we're working with dozens of more companies to go into the marketplace., 9.3 million github users have used an integration.

C

And the growth is huge., it's up more than 4 million from just may.

C

More people than ever are trying integrations..

C

It's because you told us that integrations are an important part of your workflow.

C

That's why 60% of teams use an integration.

C

Integrations make your developers stronger and more efficient.

C

We now have 200 million daily queries to graphql from our own engineers.

C

And integrators. with graphql,, you get the same api, the same tools, and the same data.

C

That github engineers use.

C

and when I talk about integrators,, I'm not just talking about folks like codec,, circleci, or snyk., I'm talking about you-- our customers.

C

building tools, building workflows, using our api.

C

And that's why we've seen huge growth in oauth apps as well.

C

We're at 400,000 oauth apps,, which is also up about 100,000 since may.

C

It's an amazing time to build an integration on github and bring it to market.. We want to make it easier for you. so,. You can try integrations, and find your perfect tool.

C

And we're going to do that with marketplace free trials.

C

For example, folks, like waffle, can allow their customers.

C

To take a look at what their integration is, offering.

C

and then go down and find the plan that works best for them-- personal, in this case-- and start a 14 day free trial..

C

We really think this is going to help customers find the tools that work best for them,, but also give integrators.

C

A better way to grow their businesses.

C

With marketplace free trials, customers can find the best in class tool.

C

And sell it for 14 days, and then ultimately choose the plan.

C

That's best for them. integrators can choose whether they want to offer free trials,.

C

And customers will get an easier upgrade flow.

C

I'm excited to share that free marketplace. Trials will be available to all integrators starting on october 31st.

C

We believe this helps github users find their perfect integration,.

C

Integrators to find the right, customer.

C

And that's our update for integrators. (applause).

C

There's a unifying thread--, community,, integrators, businesses--.

C

We're all developers. and as chris mentioned, there's still too much friction in writing. Code, reviewing code, managing projects.

C

Our product and engineering teams have been chipping away at that friction.. Our desktop apps have seen immense growth, and have amazing workflow updates,.

C

Like our git and github integration for atom., you can commit code, manage pull requests, in the world's most hackable editor..

C

In collaboration with facebook,. We released atom ide,.

C

An optional set of packages to bring ide functionality.

C

Hacked right into atom., if not having ide features, was stopping you from giving atom a try,.

C

Now's, a great time.

C

we've also rebuilt our desktop application on electron, and it's blazing fast.

C

We also completely open sourced the client.

C

It's the best github desktop client to date.

C

and we're very excited to work with the community to bring new features and evolve. Github desktop over time.

C

We also brought git and github to more developer communities,.

C

Like our native extension for visual studio., you could connect to github, clone repositories, list and create pull requests, and view and reply to pull requests comments.

C

if you're a game developer, or if you want to be, it's easier to use. Git and github with our github for unity, extension.

C

You can bring your git repos into unity, use lfs for large file support, and then use file, locking.

C

To ensure that you don't run over each other's assets.

C

And in collaboration with apple,, we released a new open in xcode button.

C

For swift and objective c projects.

C

Developer workflows aren't limited to writing code, though.

C

We spend a lot of time talking about code,, triaging, issues,.

C

And collaborating on code.

C

as miju mentioned, as we understand the semantics of code,.

C

We can allow you to browse pull request gits by method and function.

C

You jump to the method with the table of contents,.

C

You can see all of the other methods that have changed in the pr, and you can review prs faster and more efficiently than before.

C

We added branch protections with code owners., you can create a code owners, file, assign ownership of file types and folders, and then assign those file, types and folders to teams, individuals,.

C

Or even email addresses. that way,, you can ensure the right people are seeing the changes in your code.

C

And if you want,, you can turn on branch protections for your prs.

C

To stop prs from being merged until a code owner has reviewed this.

C

We've seen many companies build internal tools for this.

C

And we wanted to offer it to the entire github community.

C

This past summer, our interns,, with some help from github engineers,.

C

Made it a lot easier to share snippets.

C

now,, you can go into your code,, select a range, copy, a permalink,.

C

And then paste that permalink into issues or pull requests.

C

Then, we'll automatically expand that snippet. So you can see the code.

C

Around your discussion., it's really slick..

C

We also launched nested teams,, which mirror your org on github.

C

This is what github's technology team looks like..

C

It starts with the technology team, that has an application engineering, team,.

C

Which then, has other nested teams within that.?

C

A big benefit of this flow is that the permissions can cascade.

C

From parent teams to child teams.

C

and it's a lot easier to create and manage teams of developers.

C

Today,, I want to share something with you that we've been working on for developers.

C

We want to make it easier to collaborate outside of the code.

C

So, I'd like to introduce you to team discussions,.

C

An all new, yet instantly familiar way of collaborating with your team.

C

Here, we have the awesome panda rocket team,, which now has a new profile page, and can choose an avatar.

C

That works best for them.. You can use features that you know and love, like github, flavored, markdown,.

C

Browse the members of the team,, the repositories, the team has access to,.

C

And any nested teams., or simply catch up with your teammates in the all new discussion, timeline.

C

For the most important messages, you can pin them.

C

and your team can react to messages, leave comments, embed images,.

C

Just like you would expect.

C

if you want to have a bit more of a limited audience,, you can post messages to just your team, and mark them as private.

C

Team discussions have a new profile, page, custom avatars,.

C

Where you can see your team and any nested teams., you can post messages to your discussion. Timeline, pin the most important ones, post just to your team,.

C

And then we'll use your notification preferences to keep you up to date,, whether that be with the web, ui or email..

C

Team discussions are currently in private beta., we're working with large and small teams to try the feature out.

C

I've been using it internally at github, and it's a really great way to share information and collaborate with my teams.

C

we'll be sharing more information about team discussions in the next couple of months.

C

So,, let's recap. first,, we have a better way to collaborate with our community and github staff,. With the github community forum launching october 31st., github enterprise customers can purchase premium support by talking to our sales team. Today.

C

integrators can offer free trials for their marketplace apps starting october 31st. and team discussions,, which bring a better way to collaborate.

C

With your teams, outside of pull requests and issues.

C

All of these features, all the features that miju talked about,.

C

This entire event is a huge undertaking, and we couldn't have done it on our own.

C

I want to thank our sponsors for making this amazing event possible,.

C

And giving us an opportunity to meet all the github users face to face.

C

Let's give them a round of applause. (applause).

C

Make sure you visit them, too, because they have a lot of really awesome. Experiences.

C

I'd like to also thank the hundreds of github employees.

C

That brought these features to you from across the company.

C

We're passionate about giving you the best software development.

C

And collaboration experience in the world.

C

and that takes a team effort.

C

I'd like to invite you to say "hi" to the ask github section,, where we have githubbers from across the company available to talk to you about these features, or anything about github..

C

We're really excited to see what you do with these features, and where you'll take github in the next year..

C

Thank you so much. and now back to chris., ♪, (rock, music) ♪.

A

Thank you, kyle, thank you, miju..

A

That was a lot. there's some awesome stuff there.

A

alright. so,. I, like writing. Code.

A

I'm not allowed to really work on github.com anymore,, but I still really like it. I've, always loved writing. Code..

A

Someone once recommended that I get this book called the the little schemer.. It's short. and I do all the exercise in it on paper.

A

Step away from the computer, step away from the keyboard, and just think and reason and try to figure out this mind-bending way of software development..

A

So,. I was once on an airplane, and I had my hipster little moleskine with me and I was doing the little schemer..

A

It was fun,, it was a couple of hours flight.

A

and I got off the flight, and this really nice older lady.

A

Next to me, said, "excuse me.! Are you a poet? or are you a writer??

A

I saw you writing.". I was like, "you're going to be very disappointed with my answer." but no,. I was writing code, actually, on paper..

A

I'm not crazy,. I promise., but writing code is an amazing act.. It's challenging.

A

But in some ways, it can be a barrier. and what we're interested in is the future of coding.

A

Being less about coding., we used to use this tagline, social coding,, which I've always loved.

A

But as miju was saying, coding is not the main event, anymore.

A

Building software is the main event.

A

coding is just one small part of it., the more data we have,, the more we put onto github, the more we share and innovate together, we're not really standing on the shoulders of giants as much as we're all doing. This together.

A

We're standing on each other's shoulders., we think the future of coding is no coding at all..

A

We think autonomous coding is a very real thing..

A

Software development isn't going anywhere. in fact, software development itself is getting more and more important than ever., but the actual act of coding, the act of sitting there and typing.

A

Or dictating to a screen--, that's not what humans are great at.

A

That's not what we do best.. What we do really well is we think. and we solve problems. and we're experts. and we take in input and we devise a solution..

A

That's the essence of software. Development.- that's the essence of overcoming challenges.. That's the essence of building something great..

A

I started becoming a software developer, not because I wanted to learn. Scheme,.

A

Or php, or c. I saw a screen., and I want to make things move on that screen.

A

and when I figured out that the way to do that was software development,. I really fell in love., but a part of me still cares very deeply about making something move on a screen.

A

And there are a lot of people out there that want to make something move on a screen or on a watch or on a tractor or a jumbotron..

A

But software development is impenetrable;, it's inaccessible;, it's hard for them.

A

To get up and running. what we think about is the next 100 million developers,, what they want to do,, how we can make it easier for them.

A

And when I say we,, I'm talking about everyone in this room,, everyone here, together., the next generation of development- is going to be more powerful.

A

And mind-blowing than we can ever imagine, because the current generation is already astounding. and what we can do by working together, by sharing our data,.

A

By building more on github, by changing our own technologies,.

A

It's we can bring more people into that fold, who are then doing the same thing and we're all benefiting.

A

Software is a universe that we know almost nothing about.

A

We don't know anything about our real universe, basically.

A

and we know even less about software.. But what we're doing here is we're exploring it.

A

we're charting out new paths. we're finding new planets. we're experimenting. With,, you know, teleporters and all sorts of weird things.

A

But ultimately, what we're trying to do is we're trying to make something. Happen.

A

We are builders;, we are creators; we're trying to create something.

A

That has an impact. at github,. We think that we can make your impact larger by working together,.

A

By building the largest software development community and not just sharing words and ideas,, but sharing insights passively.

A

All the time., the next 100 million developers, are going to think about this very differently., and it's not clippy.. It's not someone. That's telling you what to do.

A

it's something more akin to the internet..

A

What we're excited about is--, if you think about moore's, law,,.

A

If you think about a lot of the great predictions that came out of the early 20th century--, they were linear., you can imagine screens getting smaller.

A

moore correctly pointed out, you can imagine chips getting smaller and more powerful., but we could have never imagined the internet.. We could have never imagined this invisible thing that changes the way we interact with each other.

A

and then to carry around in our pockets--. I don't think there are a lot of theories about how society would be transformed.

A

When we're all connected., not just through pdfs and documents,, but through our thoughts.

A

And more so,, through our code., the future of software development, we believe,, is ripe for a change like that.

A

coding has been getting smaller and smaller since the beginning.

A

I mean, we know this., we used to measure by lines of code.

A

but now, we're standing on all these great libraries that have come before us, meaning,. We write less code., it's a big part of why open source is so great.

A

so,. If you play that out, eventually, there's going to be zero code,, not for everything,, but for some projects, you're not going to have to code at all.

A

I see that as a little screen prediction..

A

I see that as a linear prediction.. What we're really excited about is the inflection point that we're on the precipice of.. There are more developers now than ever.. There are more joining now than ever., we're writing more software. we're focusing more on the craft of development than ever.

A

and all around us,. The world is changing. automation,, which is a word that developers have embraced. Forever-- I mean automation's, the greatest thing, ever-- means I have to do less stuff--. That is now one of the biggest buzz words.

A

In the entire world, right? and who's pushing that forward?, who is automating the robots?, who are the people that are actually making this change? Happen?, it's us., it's the people in this room., it's you,, your colleagues,, the future developers.

A

and, what's most exciting to me about that,, is we don't just have to automate.

A

Warehouses, and doctor's offices, and all these great things.

A

In the real world,, which is amazing., we can also automate software. Development.- all the changes with self-driving cars,, with vr, with the world.

A

Becoming more networked,, those all apply equally to software development.- typing on a computer is such a low fidelity way.

A

Of exchanging information with a system.

A

Right? voice is great.. This is why conversational uxs are taking off.

A

you're, experiencing one right, now. and in fact,. Even if you can't hear what I'm saying, there's a way for human language to be--, there's an argument that human language is a really great interface into each other..

A

We're really excited about seeing what this does for the future of software development, and what all the future software developers do with this,, but we're really most excited about seeing what you're going to do. what comes out of today,? What comes out of the next ten years,?

A

What comes out of the next 50 years of software? Development., because we are just at the very beginning. we talk about software as eating the world..

A

We talk about all these great technological innovation, and yet, at the end of the day,, we're still just hitting buttons on a keyboard.

A

so,, I'm going to leave you with a quote,, a bill gates quote,, which I feel like is appropriate., and this might not even be true., but I'm pretty sure he said this, or I can at least promise you.

A

I read once that someone told me that he said this,, which was-- someone asked bill gates--. This is the 80s, when microsoft.

A

Is a little bit smaller, but still, a dominant force.

A

"What makes a good programmer to you,, bill?" and specifically, "how. Do you know who the great programmers are in microsoft?" and his answer was a bit of an allegory.

A

it was, "if. I walked past someone's office 10 times a day, and every time I walked past their office, they're typing,.

A

That raises some concern for me." and they said, "what. Do you want them to be doing?"?

A

He says, "well,, you know, programming, isn't about typing. we're. Not typists.. Programming is about thinking. it's about solutions., it's about solving problems.

A

so,. I want to walk by someone's office and I want to see them typing,, but I want to see them thinking..

A

I want to see them considering input,, making decisions, and then using their fingers or whatever input device they have, to share those insights with the computer.".

A

It's not about the typing., it's not about the coding., it's about the solving problems,, the building things., and that doesn't mean this is going away..

A

That means this is going to become more awesome..

A

There's going to be more great tools and more ways for you to communicate.

A

To the computer, to the system, what you want to build, than ever, before.

A

We're going to have more control over the software we build in the future,.

A

And it's going to be way better,, because all software.

A

Is increasing together. a rising tide lifts all boats,, someone once told me.

A

that's what we're trying to do with the open source community with the entire software development community..

A

We want to work together to make all the future generations great,, but at the end of the day, we want to reduce the friction;.

A

We want to lower the barriers;. We want to help you build something great, and we want to do this. All together.

A

so,, we are the pioneers of the universe's software..

A

The world is going to get really weird in the future.. Software is going to be very different. and I cannot wait to see what it looks. Like. so, thank you, everyone.. Thank you to everyone that put this on..

A

I hope you have a really great three days.

A

enjoy github universe. I'll, see you next time. thank you,, everyone., (applause), ♪, (jazz, music), ♪,.