Duration 43:40
16+
Play
Video

Day 1 Keynote | Brad Green & Igor Minar

Igor Minar
Software Engineer at Google
+ 1 speaker
  • Video
  • Table of contents
  • Video
ng-conf 2019
May 1, 2019, Salt Lake City, UT, USA
ng-conf 2019
Request Q&A
Video
Day 1 Keynote | Brad Green & Igor Minar
Available
In cart
Free
Free
Free
Free
Free
Free
Free
Free
Add to favorites
28.35 K
I like 0
I dislike 0
Available
In cart
Free
Free
Free
Free
Free
Free
Free
Free
  • Description
  • Transcript
  • Discussion

About speakers

Igor Minar
Software Engineer at Google
Brad Green
Engineering Director at Google

Igor is a software engineer at Google. He is a lead on the Angular project, practitioner of test driven development, open source enthusiast, hacker. In his free time, Igor enjoys spending time with his wife, two kids and a dog, doing outdoor activities (including but not limited to sports, gardening and building retaining walls).

View the profile

Brad Green is an Engineering Director at Google where he manages that Angular Framework, Google's internal CRM suite, and other internal development productivity tools. He lives in Mountain View, CA with two kids and four chickens

View the profile

About the talk

Q&A session with the entire Angular team at Google. Team members answer audience questions on the future of Angular, Ivy, Angular Elements, the CDK, diversity, and other questions.

ng-conf is a three-day Angular conference focused on delivering the highest quality training in the Angular JavaScript framework. 1500+ developers from across the globe converge on Salt Lake City, UT every year to attend talks and workshops by the Angular team and community experts.

Follow us on twitter https://twitter.com/ngconf

Official Website: https://www.ng-conf.org/

Share

Good morning. Hi, I'm Brad green. I'm an engineering director at Google and I managed the angular team. I want to ask how many of you been in the angular Community for less than a year. Just show me your hands great. Awesome. Thank you so much for everyone who didn't raise your hand. Thank you for coming with us on this journey for so long. It's wonderful to have you. before I start and get into some serious content I want to make all of you a little bit of an Insider into how English started

and why we do the things we do and how we all get to be here today when I started to do it one of the first projects I got to work on was Gmail that's pretty cool I came in 2008 at a time when Gmail has some problems that was actually up to me I was charged with helping to solve these problems mainly we had not shipped a new version of Gmail for 6 months The problem was that we actually we had really low test coverage. We couldn't make a stable build and I remember getting

into an argument with the tekla dealing with John and by the way, he's a fine guy, but we were getting into it and I remember I think I got to the point where I might have screamed at him. We need to get in there. I just write some tests. And the thing you told me next made me stop. Kelly said how And you look totally defeated. I felt like a jerk because what we realized then was that it was just infrastructure Ali hard to build test the way we had written Gmail.

We spent the next year or so digging out and we're fine now we can really see email multiple times a week every day if we want. Tell you the story because this stayed with me and by the way Mishka was on the team with me and this kind of set our town for what we wanted to do and thinking that we could help more by providing a lot of infrastructure to support all doing building Rich applications today where we have an ecosystem that we provide that has everything that you know, and love in the framework with dependency injection and change detection and declarative

templates, but far broader than that where we have forms and animations and I-10 and a ritual components and a framework for building those components. And we do this all so that you don't have to do this work so that you can build on top of it and not have to run into the problems of not having the proper infrastructure. We spend a lot of time on this. We spent a lot of time making sure all of these pieces work together as one unit. What are the other things we spend a lot of time on is making sure that you can come along with us?

To the latest version and so that when we release the next version, which was going to angular version 8, we're already in the release candidate phase that you can just go to update the angular. IO. Playing with Virgin you're coming from you get some simple instructions on how to do it. Most of the work actually happens inside the CLI. When you type Angie update and our packages were able to do this because it's actually our responsibility on the angular team to upgrade to update every verse every application at Google that uses angular. So we go through all of this with

the apps at Google that use angular. And then we bake this into this energy update command for you to use. We've been working at this since version 6 but we got some really good validation two were on the right track from some of our friends that are France and KLM where they wrote this article about how we upgraded the website with half a billion annual users to English 7 in less than a day and how we're going to do it even faster and angular hate is pretty cool. They have this wonderful quote in your which I'll just read to you that we believe that the best

measure of a healthy codebase and development team is the time. It takes from wanting a change to the time is developed and deployed into production or another words my goodness how well I'm doing is an inseam is measured by how quick I can get my ideas out into production for themselves and they measured how long it took to do it. For upgrading from angular from one branch to another the grafted for us. We're going from 2 to 4 was a month for to 5 and 5 to 6. Just two weeks and going to angular 7 just a day. That's pretty cool. Now it's not

all stuff we've done in the injury update command. It's a bunch of things that they've done to prepare to make sure that they can take advantage of our new releases every 6 months and that's why we give you a consistent release schedule. One of the other things that might not be obvious that we spend a lot of time on is supporting the community and making it something that we love to be a part of it. That's why we're here this week with you. Our best measure of growth for the Angela Community is number of people coming to our site angular. IO and its

2018. We grew more than 50% to 1.5 million 30-day actors on that site. More than how many people are coming to our website that we actually care about what the organizer started to talk about which is how we all treat each other in this community. I want to tell you a story. About three years ago. I was making dinner cooking the kitchen my daughter comes in and she has a burning question. She says Daddy. When you were a kid, did you pick your nose? And so I was a little conflicted. Because I might and I want to tell her the truth, but on the other hand, I want to set her up for success in life.

I thought I said hey, you know sweetie. Yes as a kid. I did pick my nose. But what I've learned is that it's important to use a tissue instead because it's an attorney. I'm not going to offend anybody by picking my nose in public, but she has another question says Daddy when you were a kid and you pick your boogers. Did you eat your boogers? So again, I'm a little conflicted. Forget I said yeah, baby. I probably did eat my boogers the kid, but I've learned it's better to use a tissue and that's what I want you to do.

I thought we were done but she has another question. No. baby use a ticket She's progressed. She is now four years older and is in the burping contest. I'm telling you the story because what she was really asking is what's the right way for me to behave? What's the acceptable way for me to behave in this world? And that's what I want to spend just a little bit of time to give us some really good time explaining the code of conduct was calling the backstop for bad behavior,

but that's not what we're after. If you trust me, I want you to go through a little exercise with me, right it is safe here. If you would maybe close your eyes cuz we're going to imagine something. Imagine you come to the angular Community for the first time. imagine that because of who you are your race your gender the way you talk because your new you get rejected or you get made to feel uncomfortable. How would you feel? Be angry. May be wronged. I would Let's imagine the other thing though. Let's imagine that you come to the angler. Can you

come to a conference like this? When you come to an online Forum you come to a meet up and no matter who you are no matter Which races have new you are with your gender. Is anything else about you you get supported you get welcomes and you get all the help. You need to grow. I don't know if your eyes. But let's keep imagining what if you're one of these people who got welcomed and as you grew an expertise and connections the community you were able to welcome that next set of folks coming in. How did that feel? Pretty good. That's what we're after.

Largely, that's what we see. What's the worst so excited to be here with you about there's a couple things we can do though to improve our abilities to welcome people under some good talks here. I'll talk to you about a couple of them. Never one is going to talk tomorrow. And Her speech is called it's just a compliment after all and she's going to help inoculate this against making statements that would make women feel uncomfortable inadvertently easy to do if you don't know and it's super easy to avoid if you do know. And then more on why would I

want to be supportive Community? Why do I want to be involved go? See Molina's talk on Friday. She's going to talk about how texting you can change your life. Like what's in it for me. The block is also going to talk more about our values and ways that we want to engage more with all of you folks. Later. Definitely go check these two talks app. All right. I want to talk about our lives release now angular version 8 in the release Kennedy phase and we've been in release candidate for about a week. We usually give ourselves for weeks like a month

to bake out any of the final bugs. Once we think we're at release Kennedy. We're headed for a final at the end of May. And then this will be important later. Bruce we do releases every 6 months of Version 9 is going to be coming into 4. Let's talk through we've done in Bridge Nate. There's a lot more than we thought we would have never won. You can try it today in release candidate. We hope you do you can just go to update. Angular. IO for the instructions how to do it and you can get all the docks at next. Angular. IO. Once version 8 becomes the

stable version. It's just going to be the docks at angular IO that point. big feature version 8 you can make your apps all of your apps right now quite a bit smaller with this new feature called differential loading the way it works is this we have old browsers Legacy browsers that need big sets of polyphenols and they can only really handle es5 syntax. And so what we're going to do with differential Ortiz, we create two bundles one for the old Legacy browsers and then a minimal set of polyphenols and using the modern. JavaScript syntax, which is actually much

smaller. Make it served at Evergreen browsers. The cool thing about this is there's no server config to change this happens all in the client request. So there's really no reason not to use it one bonus is the if you use this your also set up to work well with the search engines if you care about SEO we tried this out on many different apps one of them that we maintain a lot would do a lot worth is our angular. IO site we saved about 41k here and from try it out in other applications. We think you're going to save somewhere between 7 and 20% It's a pretty good deal.

Definitely something to try once you get home. Turn of all, the pictures came in version 8 number one, we're extending the ability for you to customize the CLI with peach gold Builders where last year with schematics we gave you the ability to change the files that we out put now with Builders, we give you the ability to change which tools run and in which order at work is great at yourself. We have a set of features that were starting to extend or build on top of Builders giving you the ability to deploy your applications right from the angular CLI today in Mancos talk

later in this room. You'll see him demonstrate deploying from the CLI to Firebase. We have folks from the Azure team working on deploy to Azure and many other folks just starting me. We'll talk more about it later today. We added support in the sea life or web workers. So you can easily move some of the work that you're doing out of the main UI thread into a separate worker threat so can never enter up with users doing a recce using this on angular IO ourselves to move the search indexing for the online searching off into a worker thread so that

a candidate for the users are doing we made many service worker improvements or building Progressive web apps on angular. You can have a better time with a better set of apis we've a standardized the way we do lazy loading work today in English 7, you do lazy loading in the router through a special string format that we invented. an inversion ate and going forward you're going to use the standard browser import mechanism the big Important thing about this is that now instead of us having to have a special angular version of webpack a rollup or any of these other tools these tools now all just

understand the way we need to do coats wedding and you can use it out of the box without waiting for us to build a special plug in. we're still helping with folks who need to migrate from angularjs to angular and we built a compatibility layer for the router where the dollar sign location service in angularjs be emulated inside angular so that if you're doing a migration, you can use only the angular router and I could do everything to the old angularjs router did We're working on better IDE completions and we built a better d. T s roll up so

that the ideas can actually give you better information. And we also built a simplified getting started guide so that if you have friends or coworkers are other people who need to learn angular got a much easier way to do it. Thanks for all of these things in the speaker notes and we're going to give you a link to the slide deck of the end. That's the main stuff that is completely done. We have a bunch of a couple big project that you've probably heard before if you've been to one of our talks that are still a bit of a work-in-progress, but that some of us should be

using today and these are basil for doing bills and Ivy are new rendering Engine with basil basil is the core of the build systemic Google. We've been using it for over 12 years and we're now trying to bring it to the outside world. You can think of this as the thing that orchestrates how all my tools run how typescript webpack and roll up and Sass and all of these things get run to make them run as efficiently in parallel. As Distributors possible. We do a reasonable job of building, but there are Headroom limits and we

partnered with a basil team to remove those limits in the CLI. We're doing this because there's actually there's the shift that's happening where it used to be that most of the logic that I would write from applications was on the server side in Java or C sharp or some other language. morbus moving to the client because we want to build these rich immersive experiences for people when they use their applications and with it the complexity comes over to but unlike sharp and C plus plus on all these languages who have a very rich and

Integrated build environment. We haven't had that over on the side of JavaScript and that's what we're trying to bring over with basil. Big benefits Raptor number one is we want to have intramural building test. So if I make a small change to the code, I should also see it just a small rebuild time. We want to have the ability to do. Test in deployment so that if I'm building a front end and a back-end separately, we want them actually now to be able to live together in a single belt so I can guarantee my deployments are going to work together and then we want to be

able to scale better by moving those bills and tests out for my developer desktop under the clouds. They can run in parallel and reuse build artifact so that my bills can go quicker. There's a bunch of folks who are already taking advantage of this. Of course Google reviews it across all of our development environment. Everybody a Google uses this to build what we build but it hasn't yet works in the world you live in outside of our environment, but we're starting to see if there's actually a team here in Salt Lake city named lucidchart. Probably some of you have used it. They

build a beautiful diagram tool in angular on the front end with Scala on the back end and now they're able to release these front and back in bills together as a test that hole Another example. Ocean is a start-up in China and they're seeing much faster builds by just using the Builder artifacts and not having to rebuild things that have already been built. Another one is actually us on the angular team. If you remember this chart of all of the products that we build this is something that we have to guarantee to you where everything works together. They

can't be their own separate repos. And then I was having to do every permutation of testing together to make sure that they're working this drove us to start putting them into a model repo into a single location. But without basil we're not going to get the benefits of being able to run in parallel that scale with the reliability that we want. We've moved most of angular to basil and now we're starting to paralyze it by running it in the cloud on multiple machines. We've seen RCI the parts that are in Basel actually go from about an hour down to just

7.5 minutes. 7.5 minutes. This is dramatically impactful for our ability to get versions of angular out as fast as we want. Imagine having to wait 60 minutes if I had to fix a typo. Where we are today is that you can use basil in the CLI in version 8 and we got a new website at basil. Angela. I owe you can find out more. It's not going to be for everyone right now. We're working towards that. There are still a couple of rough edges, but if you want to get some of the scalability benefits that

we've been getting on the angler team and that some of these other companies definitely check it out and definitely check out Alex Eagles talk. Alex is the lead for the CLI team. He's been working on the Basel problem for a number of years, and he was going to tell you many more details about where we are and how to get started. We also have the CLI team and members from the baseball team. NG conf three different times today from 10 a.m. Till 1:30, Thursday from 1 to 3 and Friday from 10 to 1:30. You can go talk to them and see how to get started.

5e Ranger if you haven't heard about it, this is our rewrite of a rendering engine inside ankle and we have a bunch of different goals for this. Number one. We want to make it possible for you to build smaller apps much smaller. We want to give you faster compilation and like basil if you make a small change, we want to have a proportionately small rebuilt time so you can build any size application. Willing to give you simple debugging because debugging is a fact of life and it should be an easy task. We wanted to improve typing and

there's parts of our templates in angular today that we don't yet type check. And most importantly wanted to be backwards compatible so that if there's any change we have to make weed either automate them or their minimal so that everybody can come along with a journey in version 8. This is the thing that we spent the most time on. Let's see how we are. You can actually try. I be today in English version 8 you can create new apps by just setting the dash dash enable IV flag. If you want to Port your existing application on top of ivy. We got some simple

instructions here at next. Angela. IO / guide / IV. What are you going to get we've been working backwards compatibility for a longtime inside Google. We have hundreds of applications that use angular and we're now passing 97% of their test weed through down to the very long tail. This represents hundreds of thousands of tests pretty confidence going to work for a lot of you already where we think it's not going to work though. And we need some help. Is it all of the libraries that folks use outside Google that we don't use it. We don't have exposure to So if you're a

team that has very few dependencies. We think you could probably have a good time and Ivy and we love you to start using it. If you got many dependencies, we think there's going to be problems. If you can we'd love your help Talia switch things. We need to fix. So in the rest of the RC. And as we head towards Burger 9, we can fix all of those places. We have hit are simpler debugging go right now and Ivy if you put it on you get break points, and if she know I can just go in there and then it back up. You might feel worse at the break point where I can actually walk up the

stock price and see my code in a very human readable way. This is pretty cool. Smaller was one of our goals. I'll preview we're not there yet. Today in view engine which is the name for our current renderer. If you do a Hello World application get about 151 kilobytes minified but not compressed. If you turn on different the differential loading you shave off a bit. Infuse IV Shave off a bit more and Ivy plus differential. It's starting to look pretty good. And

to be clear a recommendation for everyone is certainly using we're using today with the differential loading. And we need help testing the IV in the compatible mode with a differential serving notice. I didn't say try anything without differential service. You should definitely use it. But this is not where we're headed. We made some last year. We made some charts of where we want to go because we want to make very small applications possible. And if you turn on IV with an experimental bootstrap API that we have

not ready yet. You get some very small built-in right now. It's about 14k again uncompressed. Recipe for Thrill Seekers as an Easter egg hunt for it. There are a couple of bonuses that we were able to achieve in IV. They were part of the original goals. But as we were developing ivy on the new better architecture, we found we could have used some of the things are what is we are seeing lower memory requirements and then different scenarios as different amounts, but we have an application simulation of a 100 by 100 grid. Where is 30% down? And the material unit test is 91% down. We're

seeing much faster tests are angular framework tests are 38% faster than material unit test or 80% faster. We also be able to fix a bunch of long-standing bugs things that are probably annoying you today. There are cases where teacher texting runs too often where class bindings override other classes. I've made a list of the speaker's notes. There's some good stuff for you to find there. So where did we get to? NIV today in Bruges Maids. Yes on some board about going backwards compatible lower member requirements faster tests a

bunch of bug fixes. A whole bunch you try it. There are some things that we still need to do for Virgin night. We still need to reach our overall size Gall need to get to the faster compilation goal and the improve type checking. But this is where we're going and it's Version 9 are big goals are number one to make IV the default make either the default for everybody. So everyone gets to take advantage of these benefits and over to to make sure that basil in Eli is fully future and scalable again so that everybody could take advantage of it. If you want to hear more about what we're thinking

of her Version 9 should definitely go to Friday mornings keynote with Mishka and Steven. We're going to Deep dive and all of that. I know like to bring to your Manor up on stage where he's going to talk more about our motivations and design considerations for angular and how we want to work more with everyone all of you and the community. Thank you. Hello everybody. My name is Igor. I'm at Exit on the Angela project in a friend mentioned. One of the things that I would like to share with you is some of the design considerations that go into making angular and also

how we would like to angle Community to be part of this. One good reason that shouldn't be surprised to you by now is compatible. We want Angela to be compatible so that you can rely on it. You want to build a successful ecosystem that people can rely on them because if we learned anything from the English years to English version to Adventure is that we don't want to leave people behind leaving people behind is not fun. It's not funny for you. It's no fun for us and we don't want to do this ever again. It was actually quite funny when recently we had a meeting where all the leads to on the

anglo-boer working and we're discussing the user experience experience Bill. Kristol have when they try to play with IV in the version 8 RC And we discussed in great detail as you know, what is going to look like. What is it that they will see is it going to be good what other than going to be the concerns and in about 20 minutes and somebody in the room said hey, wait a minute. How are you? Really spending this much time discussing developer experience for Optum preview for technology. That is not going to be fully ready until much later in this year. And yes, we

have I'm very proud of the team because it took a big man shift to get there. But with this Mineshaft we can provide a much better experience for all of you. But being just staple is not good enough. The web is changing to use your expectations are changing. The developer experiences are also changing. We need to keep up we need to make sure does angular doesn't stay behind and become stagnant system to be malleable and ever-evolving so that you can rely on it and you can know that all of the new things that are coming

for the web will be available and supported by angular. Every time we talk about your future one of the considerations is scale and when we talk about scale, it's not just how to skill-up. But also how to scale down. Let me show you what I mean. This is gratified roof a bunch of people on on our team where I'm trying to capture the number of users supported by single application. I'm on the y-axis and the number of applications of this kind on the Xbox on the x-axis. So there is a few very few

applications that support multiple billions of users are there. We don't have a whole lot of them. It's like Gmail Facebook and someone What us, the number of users that interact with those applications drop there is an increasing number of applications that are built of that size are all the consumer applications of Enterprise applications and all the way down to the long tail of a small applications that we just built for fun or we just need a simple submission form or will be filling out applications for the occasional purposes. When we built angularjs many years ago. We were

targeting the long-tail. We were targeting the experiences were we wanted to make sure that Angela was easy to get started with and you can be successful very quickly and Bill small applications and ceilings. We could not skill up anymore, especially as we were building big bigger and bigger Enterprise applications. This is why we decided to build English version 2 and this is what we thought we were building. We thought it's going to be amazing is going to capture everything we had with angularjs and much more. However, in reality we built something like this where angler

official version 2 was primary suitable for the Enterprise use cases where you need to scale both in terms of size of the Cove Base and number of users are number of Delaware's collaborating on the co-pays. All the years however through different versions of angular. We incrementally increase the range. We were both working on scaling up and scaling down and going forward. We have several efforts that extend the range floor. With English ivy, which is currently playing for her tonight. We would like to capture the long chain, especially with Ivy and in combination with

elements. It's perfectly suitable for use kisses for you. Don't need the single page application. You just been building something much smaller than that. Additionally. We have a project that we haven't discussed much in public. We call Angela thoughts on this is a project that is Focused on making sure the Anglican also skill up and allow us to build bigger and bigger application. There are going to be several talks much more in detail into these two efforts. Medford is going to do a talk on elements and Ivy and how that can help

with a long tail and Rob is going to talk about how no verification has to be as ba. But he's also going to cover some of this killing up efforts that we have in Works in angular. If you go to this graph one thing that you will see is there still space that is not covered. And that is the space where you really need technologies that skill up and allow you to build your normal supplications. This is not where Angela is today yet. We would love to be there. There are some people that are exploring this successful in certainly this is not the sweet spot for

Anglia. However, approximately year ago. We we got a new sibling team at Google and it's this team that is focused specifically on the segment. They build the Technologies and the designs that support the biggest applications of Google. What is the several months since we've been collaborating and operations were focused primarily on exploring whether it would be feasible to take some of these Technologies and make them accessible to the open source community in the future will update you in the future

once we have things to to share. But in the meantime, I would like to actually become the team here cuz we have several of them here. They wanted to know what the English about they are. Not smart part of the Angel Community yet, but they would like to understand us better. So if you do bump into them, please extend an extra kindness so that they get to feel what the Angel magic is all about. This thank you. This is bring us to the another design consideration, which is English

very people-oriented. I was going to talk about this but it's definitely too much better job interviewing a lot of people we played this documentary before many people came into into the room. So I encourage you to go online and watch it. It's a documentary about Angela community and its talks about our values and how we work in the most of the most is that it captures the essence which is we are here to enable creations of applications that people love to use in these applications to be built by developers that love to build them in a community that

is welcoming. community We're primarily living in the open-source world. Most of the work happens on GitHub. And this is where a lot of the open-source communication in the gagement happens. Lord of our team is actually sourced from the external Community from the open-source world and many people don't know that while we build everything on GitHub. We have this very elaborate continuous integration story with Google. Where is we merch changes to the master Branch from GitHub. We almost

immediately bring it to Google where is available to all of the developers that use angular within a few minutes or hours allows us to get a very quick feedback on how things are working. And if you're breaking anything or if you're making things better or worse, this allows us to extend higher quality assurance to the the releases that eventually make in the ship to the open source Community the head of angular and it's kind of insane. I don't have time to talk about it here, but if you are interested in this I'm happy to talk about in the hallway.

So just grab me. one of the things that came out of this this kind of process for angular team works on the boundaries between Google and the open-source is that it for exchange of information, but also Technologies between Google and open sores outside of Google. It was conceived in the open source Community pitch to The english team. We really like that and we worked on this project for this point year-and-a-half or maybe in March and in a few weeks is going to have a major impact on Google on the other hand. We haven't talked about you like

basil that is a core part of how big how Google works and Angela team is collaborating with basil team to take this very unique and scalable technology and make it accessible to the web development in the open-source world. If you look behind the curtain, what do you'll see that there is 43 or so amazing people that make up the England team and these people are organized into 5 symptoms of cross-cutting Debra Lynn documentation. And then three a product-oriented the tooling framework in components

that create the structure that supports everything we do in the angle Community special but there's one thing that does make ruler special when it comes to building angular. We just they have access to the internal systems to do so, she posed to be able to support and the buck internal applications and this makes them unique. Other than that everybody else who's collaborating on the angular and about half of the team is non googlers. Equal rights in are influential in building angular. What are the things that

has been concern to me for long time? Is that at the bottom of the pyramid which is the community contributions issues PRS keeps on growing much faster than the top of the pyramids and if you saw some of the graphs that brat shirt you understand my concern how to deal with the growth of the community in a way where the team it's not over burden and we still able to provide you with excellent support. This is why a couple months ago. We kicked off a new program occult. Angela collaborators. This is a program that is focused on enabling Angela development to

scale through Officers Club rayshun. What is essentially means is we're taking a slice from the bottom of the pyramid with taking the contributors to the angular upholstery picking the ones that has been the most useful the most impactful the ones that were with the most helpful and turning them into true collaborators with elevated privileges inviting them to meetings assigning the mentors and making them part of the team. In this way, we're able to unblock people through two different flows. The first one is through the community where we are trying to take the passion on

for if individuals and turn it into an impact and make impact on the entire Community. We want to extend an opportunity to Enterprises to invest to invest in the open up angular in exchange for having an in-house expertise having better support and also having a bility to inform the road map of the entire. Turn off the road goes behind. This one is this feeling we're trying also to increase the diversity because the more people come and join the english team, they come

from different backgrounds and that informed decision-making allows us to make better decisions. We really want think it's better with a community and bring more of the committee members to the team. We want to create the opportunities for this coming to members because they deserve it. They've been doing amazing things things for us for years and we would like to highlight them and lastly we would like to ensure a long-term success of the project because the more people invested in the future of angler the longer the future will be In the last month, we on-boarded 9

coming to collaborators. These people have been the ones that were the most active the most useful on GitHub and were amended immediately able to help us. I want to highlight especially Adam jolly and Manfred who had a big impact on many of the features that was shipped in version 8 and I'm looking forward to seeing them big contributions from the other pillow protectors in the future. The plan is to onboard more people from the community and make them part of the team with in 2019. We think we have a capacity for about 40 people just so that we

can scale the mentorship and provide good experience. But this is the plan. In the long run. What I would like to do is to make sure that the English collaborators have the prestige that the English tea to ease have Angela Gee bees a Google developer expert is a program where we highlight the most active in the most prolific and the most impactful members of the community that focused on the developer relations and Outreach to the community. The angel lover is program is focused on actually building the product and it's not just building the code is also bother coming Tatian

triaging a surfboard design user experience research. And so At this point you might be wondering how do I join and that's valid question. Very many people excited when I when I talked about this opportunity for now. All I can tell you is if your Community member just be awesome contributor help us with finding good as she has helped us with sending a high-quality who requests and help us each rate on this particular we can merge them and we will be picking the most active ones in the most impactful ones for the next round of the decisions. If you are Enterprise

and want to invest in building angular, please contact Debra Lynn English and will be discussing this with you. We discussed many things that influence how we think about angular and how to build it. We talked about compatibility how we don't want people to people behind we talked about scalability. I'm not just feeling up but also Skilling down. We wanted to know we talked about how angular is Evergreen we want to keep up with the changes in technology with expectations. We talked about how we are people are into it because losing focus of people would turn anger

into something it's not and I'll be shamed and lastly we talked about all the conservations. We're making tomato open system operation successful in how we hoping that through open sores. We can actually see life hurts even more. There are two additional considerations and the actually skills that I would like to highlight and that sympathy and respect with empathy and respect you able to build better product able to have better relationships able to build better teams and better communities, and there is no better place to start practicing the skills than a 10g comb. We're all of us get

together and our goal is to make sure that not only we have good experiences, but everybody around us has a great experiences. Thank you so much, Don't be shy and come talk to us. Thank you.

Cackle comments for the website

Buy this talk

Access to the talk “Day 1 Keynote | Brad Green & Igor Minar”
Available
In cart
Free
Free
Free
Free
Free
Free
Free
Free

Access to all the recordings of the event

Get access to all videos “ng-conf 2019”
Available
In cart
Free
Free
Free
Free
Free
Free
Free
Free
Ticket

Interested in topic “IT & Technology”?

You might be interested in videos from this event

September 28, 2018
Moscow
16
177
app store, apps, development, google play, mobile, soft

Similar talks

Ely Lucas
Senior Software Engineer at Ionic.io
Available
In cart
Free
Free
Free
Free
Free
Free
Free
Free
Sani Yusuf
Founder at Haibrid
Available
In cart
Free
Free
Free
Free
Free
Free
Free
Free
Minko Gechev
Senior Developer Programs Engineer at Google
Available
In cart
Free
Free
Free
Free
Free
Free
Free
Free

Buy this video

Video

Access to the talk “Day 1 Keynote | Brad Green & Igor Minar”
Available
In cart
Free
Free
Free
Free
Free
Free
Free
Free

Conference Cast

With ConferenceCast.tv, you get access to our library of the world's best conference talks.

Conference Cast
731 conferences
30008 speakers
11213 hours of content
Igor Minar
Brad Green