WEBVTT Kind: captions Language: en 00:00:01.160 --> 00:00:06.690 align:start position:0% [Music] 00:00:06.690 --> 00:00:06.700 align:start position:0% 00:00:06.700 --> 00:00:13.829 align:start position:0% [Music] 00:00:13.829 --> 00:00:13.839 align:start position:0% 00:00:13.839 --> 00:00:16.510 align:start position:0% hi<00:00:14.839> uh<00:00:15.080> I'm<00:00:15.280> ever<00:00:15.559> hen<00:00:15.839> brand<00:00:16.160> as<00:00:16.320> was 00:00:16.510 --> 00:00:16.520 align:start position:0% hi uh I'm ever hen brand as was 00:00:16.520 --> 00:00:18.550 align:start position:0% hi uh I'm ever hen brand as was introduced<00:00:17.039> and<00:00:17.199> I'm<00:00:17.320> the<00:00:17.439> CEO<00:00:17.960> of<00:00:18.080> runtime 00:00:18.550 --> 00:00:18.560 align:start position:0% introduced and I'm the CEO of runtime 00:00:18.560 --> 00:00:20.470 align:start position:0% introduced and I'm the CEO of runtime verification<00:00:19.480> and<00:00:19.600> I'm<00:00:19.760> here<00:00:19.920> to<00:00:20.080> talk<00:00:20.240> to<00:00:20.359> you 00:00:20.470 --> 00:00:20.480 align:start position:0% verification and I'm here to talk to you 00:00:20.480 --> 00:00:22.830 align:start position:0% verification and I'm here to talk to you about<00:00:20.720> the<00:00:20.880> challenges<00:00:21.880> of<00:00:22.080> developing<00:00:22.519> open 00:00:22.830 --> 00:00:22.840 align:start position:0% about the challenges of developing open 00:00:22.840 --> 00:00:24.790 align:start position:0% about the challenges of developing open source<00:00:23.199> software<00:00:24.000> and<00:00:24.119> maintaining<00:00:24.599> it 00:00:24.790 --> 00:00:24.800 align:start position:0% source software and maintaining it 00:00:24.800 --> 00:00:27.029 align:start position:0% source software and maintaining it sustainably<00:00:25.680> not<00:00:25.960> necessarily<00:00:26.359> in<00:00:26.519> web<00:00:26.720> 3<00:00:26.960> it 00:00:27.029 --> 00:00:27.039 align:start position:0% sustainably not necessarily in web 3 it 00:00:27.039 --> 00:00:28.990 align:start position:0% sustainably not necessarily in web 3 it doesn't<00:00:27.279> really<00:00:27.480> matter<00:00:27.880> web<00:00:28.080> 3<00:00:28.320> web<00:00:28.519> 2<00:00:28.800> I<00:00:28.840> mean 00:00:28.990 --> 00:00:29.000 align:start position:0% doesn't really matter web 3 web 2 I mean 00:00:29.000 --> 00:00:30.269 align:start position:0% doesn't really matter web 3 web 2 I mean there's<00:00:29.160> some<00:00:29.359> different<00:00:29.560> challenges<00:00:30.000> in<00:00:30.080> web 00:00:30.269 --> 00:00:30.279 align:start position:0% there's some different challenges in web 00:00:30.279 --> 00:00:32.430 align:start position:0% there's some different challenges in web 3<00:00:30.480> but<00:00:30.560> a<00:00:30.640> lot<00:00:30.759> of<00:00:30.920> them<00:00:31.560> end<00:00:31.720> up<00:00:31.880> being<00:00:32.079> the 00:00:32.430 --> 00:00:32.440 align:start position:0% 3 but a lot of them end up being the 00:00:32.440 --> 00:00:37.350 align:start position:0% 3 but a lot of them end up being the same<00:00:33.800> um<00:00:34.800> so<00:00:35.399> uh<00:00:36.000> why<00:00:36.360> are<00:00:36.520> we<00:00:36.719> qualified<00:00:37.200> to 00:00:37.350 --> 00:00:37.360 align:start position:0% same um so uh why are we qualified to 00:00:37.360 --> 00:00:40.630 align:start position:0% same um so uh why are we qualified to talk<00:00:37.559> about<00:00:37.800> this<00:00:38.160> at<00:00:38.559> all<00:00:39.559> uh<00:00:39.800> we<00:00:40.000> have<00:00:40.480> you 00:00:40.630 --> 00:00:40.640 align:start position:0% talk about this at all uh we have you 00:00:40.640 --> 00:00:44.110 align:start position:0% talk about this at all uh we have you know<00:00:40.960> a<00:00:41.120> huge<00:00:41.680> GitHub<00:00:42.320> presence<00:00:42.879> 170<00:00:43.760> public 00:00:44.110 --> 00:00:44.120 align:start position:0% know a huge GitHub presence 170 public 00:00:44.120 --> 00:00:46.229 align:start position:0% know a huge GitHub presence 170 public repositories<00:00:45.120> depending<00:00:45.440> on<00:00:45.600> how<00:00:45.680> you<00:00:45.840> count 00:00:46.229 --> 00:00:46.239 align:start position:0% repositories depending on how you count 00:00:46.239 --> 00:00:50.229 align:start position:0% repositories depending on how you count 20<00:00:46.840> 12<00:00:47.239> to<00:00:47.680> 37<00:00:48.680> of<00:00:48.840> them<00:00:49.000> are<00:00:49.280> active<00:00:49.879> at<00:00:50.039> any 00:00:50.229 --> 00:00:50.239 align:start position:0% 20 12 to 37 of them are active at any 00:00:50.239 --> 00:00:52.470 align:start position:0% 20 12 to 37 of them are active at any given<00:00:50.520> time<00:00:50.960> it's<00:00:51.160> spanning<00:00:51.760> 15<00:00:52.199> different 00:00:52.470 --> 00:00:52.480 align:start position:0% given time it's spanning 15 different 00:00:52.480 --> 00:00:54.750 align:start position:0% given time it's spanning 15 different programming<00:00:53.039> languages<00:00:54.039> lots<00:00:54.199> of<00:00:54.359> external 00:00:54.750 --> 00:00:54.760 align:start position:0% programming languages lots of external 00:00:54.760 --> 00:00:57.189 align:start position:0% programming languages lots of external collaborators<00:00:55.680> obviously<00:00:56.000> the<00:00:56.199> internal 00:00:57.189 --> 00:00:57.199 align:start position:0% collaborators obviously the internal 00:00:57.199 --> 00:01:00.509 align:start position:0% collaborators obviously the internal developers<00:00:57.680> at<00:00:57.840> the<00:00:57.960> team<00:00:58.239> as<00:00:58.399> well<00:00:59.239> um<00:01:00.399> you 00:01:00.509 --> 00:01:00.519 align:start position:0% developers at the team as well um you 00:01:00.519 --> 00:01:01.990 align:start position:0% developers at the team as well um you know<00:01:00.640> we<00:01:00.719> have<00:01:00.879> dependency<00:01:01.320> chains<00:01:01.719> within 00:01:01.990 --> 00:01:02.000 align:start position:0% know we have dependency chains within 00:01:02.000 --> 00:01:05.229 align:start position:0% know we have dependency chains within that<00:01:02.199> software<00:01:03.039> that<00:01:03.160> runs<00:01:03.480> six<00:01:03.920> deep<00:01:04.920> uh<00:01:05.080> in 00:01:05.229 --> 00:01:05.239 align:start position:0% that software that runs six deep uh in 00:01:05.239 --> 00:01:07.109 align:start position:0% that software that runs six deep uh in some<00:01:05.519> cases<00:01:06.119> and<00:01:06.240> we<00:01:06.360> have<00:01:06.479> different<00:01:06.720> teams 00:01:07.109 --> 00:01:07.119 align:start position:0% some cases and we have different teams 00:01:07.119 --> 00:01:09.429 align:start position:0% some cases and we have different teams that<00:01:07.280> range<00:01:07.720> in<00:01:08.000> size<00:01:08.200> from<00:01:08.360> 1<00:01:08.520> to<00:01:08.680> 10<00:01:09.280> we've 00:01:09.429 --> 00:01:09.439 align:start position:0% that range in size from 1 to 10 we've 00:01:09.439 --> 00:01:11.830 align:start position:0% that range in size from 1 to 10 we've grown<00:01:09.840> teams<00:01:10.200> we've<00:01:10.360> shrank<00:01:10.799> teams<00:01:11.320> we've<00:01:11.720> you 00:01:11.830 --> 00:01:11.840 align:start position:0% grown teams we've shrank teams we've you 00:01:11.840 --> 00:01:12.990 align:start position:0% grown teams we've shrank teams we've you know<00:01:11.960> done<00:01:12.200> all<00:01:12.320> sorts<00:01:12.560> of<00:01:12.680> different 00:01:12.990 --> 00:01:13.000 align:start position:0% know done all sorts of different 00:01:13.000 --> 00:01:15.109 align:start position:0% know done all sorts of different projects<00:01:13.799> over<00:01:14.000> the<00:01:14.119> course<00:01:14.360> of<00:01:14.520> the<00:01:14.680> last<00:01:14.880> six 00:01:15.109 --> 00:01:15.119 align:start position:0% projects over the course of the last six 00:01:15.119 --> 00:01:16.630 align:start position:0% projects over the course of the last six years<00:01:15.560> as<00:01:15.680> I've<00:01:15.840> been<00:01:15.960> working<00:01:16.200> at<00:01:16.280> runtime 00:01:16.630 --> 00:01:16.640 align:start position:0% years as I've been working at runtime 00:01:16.640 --> 00:01:18.670 align:start position:0% years as I've been working at runtime verification<00:01:17.560> and<00:01:17.680> we<00:01:17.759> have<00:01:17.960> super<00:01:18.320> active 00:01:18.670 --> 00:01:18.680 align:start position:0% verification and we have super active 00:01:18.680 --> 00:01:23.149 align:start position:0% verification and we have super active and<00:01:18.880> super<00:01:19.479> awesome<00:01:20.479> uh<00:01:20.960> automation<00:01:21.960> with<00:01:22.119> CI 00:01:23.149 --> 00:01:23.159 align:start position:0% and super awesome uh automation with CI 00:01:23.159 --> 00:01:26.069 align:start position:0% and super awesome uh automation with CI CD<00:01:24.159> so<00:01:24.360> what<00:01:24.439> are<00:01:24.560> the<00:01:24.880> challenges<00:01:25.880> I'm<00:01:26.000> going 00:01:26.069 --> 00:01:26.079 align:start position:0% CD so what are the challenges I'm going 00:01:26.079 --> 00:01:27.749 align:start position:0% CD so what are the challenges I'm going to<00:01:26.240> start<00:01:26.479> from<00:01:26.640> the<00:01:26.759> easiest<00:01:27.280> challenge<00:01:27.600> to 00:01:27.749 --> 00:01:27.759 align:start position:0% to start from the easiest challenge to 00:01:27.759 --> 00:01:29.590 align:start position:0% to start from the easiest challenge to solve<00:01:28.040> which<00:01:28.119> is<00:01:28.240> the<00:01:28.360> technical<00:01:28.759> one<00:01:29.400> and<00:01:29.520> a 00:01:29.590 --> 00:01:29.600 align:start position:0% solve which is the technical one and a 00:01:29.600 --> 00:01:30.789 align:start position:0% solve which is the technical one and a lot<00:01:29.680> of<00:01:29.759> people<00:01:29.920> people<00:01:30.159> probably<00:01:30.400> think<00:01:30.640> oh 00:01:30.789 --> 00:01:30.799 align:start position:0% lot of people people probably think oh 00:01:30.799 --> 00:01:32.069 align:start position:0% lot of people people probably think oh this<00:01:30.920> is<00:01:31.040> the<00:01:31.119> only<00:01:31.280> challenge<00:01:31.600> the<00:01:31.720> technical 00:01:32.069 --> 00:01:32.079 align:start position:0% this is the only challenge the technical 00:01:32.079 --> 00:01:34.230 align:start position:0% this is the only challenge the technical one<00:01:32.479> and<00:01:32.840> you<00:01:32.960> know<00:01:33.200> with<00:01:33.439> the<00:01:33.680> the<00:01:33.840> technical 00:01:34.230 --> 00:01:34.240 align:start position:0% one and you know with the the technical 00:01:34.240 --> 00:01:35.990 align:start position:0% one and you know with the the technical challenge<00:01:34.640> with<00:01:34.840> managing<00:01:35.399> open-<00:01:35.680> Source 00:01:35.990 --> 00:01:36.000 align:start position:0% challenge with managing open- Source 00:01:36.000 --> 00:01:38.469 align:start position:0% challenge with managing open- Source software<00:01:36.640> is<00:01:37.240> automation<00:01:37.960> you<00:01:38.079> need<00:01:38.240> to 00:01:38.469 --> 00:01:38.479 align:start position:0% software is automation you need to 00:01:38.479 --> 00:01:41.030 align:start position:0% software is automation you need to automate<00:01:39.200> everything<00:01:40.200> uh<00:01:40.320> so<00:01:40.680> you<00:01:40.759> want<00:01:40.880> to 00:01:41.030 --> 00:01:41.040 align:start position:0% automate everything uh so you want to 00:01:41.040 --> 00:01:42.670 align:start position:0% automate everything uh so you want to enforce<00:01:41.439> as<00:01:41.560> much<00:01:41.720> as<00:01:41.960> possible<00:01:42.320> we<00:01:42.479> use 00:01:42.670 --> 00:01:42.680 align:start position:0% enforce as much as possible we use 00:01:42.680 --> 00:01:44.389 align:start position:0% enforce as much as possible we use GitHub<00:01:43.040> for<00:01:43.200> that<00:01:43.320> you<00:01:43.399> can<00:01:43.520> use<00:01:43.720> gitlab<00:01:44.159> or 00:01:44.389 --> 00:01:44.399 align:start position:0% GitHub for that you can use gitlab or 00:01:44.399 --> 00:01:47.429 align:start position:0% GitHub for that you can use gitlab or whatever<00:01:44.719> other<00:01:45.320> version<00:01:45.920> control<00:01:46.920> um<00:01:47.200> and 00:01:47.429 --> 00:01:47.439 align:start position:0% whatever other version control um and 00:01:47.439 --> 00:01:49.709 align:start position:0% whatever other version control um and publishing<00:01:48.079> software<00:01:48.479> you<00:01:48.600> want<00:01:48.719> to<00:01:48.880> use<00:01:49.600> we 00:01:49.709 --> 00:01:49.719 align:start position:0% publishing software you want to use we 00:01:49.719 --> 00:01:51.590 align:start position:0% publishing software you want to use we use<00:01:49.880> CI<00:01:50.200> for<00:01:50.360> testing<00:01:50.759> so<00:01:51.040> every<00:01:51.360> you<00:01:51.479> know 00:01:51.590 --> 00:01:51.600 align:start position:0% use CI for testing so every you know 00:01:51.600 --> 00:01:53.789 align:start position:0% use CI for testing so every you know release<00:01:51.920> is<00:01:52.119> tested<00:01:52.560> that<00:01:52.719> just<00:01:52.960> keeps<00:01:53.200> our 00:01:53.789 --> 00:01:53.799 align:start position:0% release is tested that just keeps our 00:01:53.799 --> 00:01:55.870 align:start position:0% release is tested that just keeps our you<00:01:53.960> know<00:01:54.240> Keeps<00:01:54.439> Us<00:01:54.600> sane<00:01:55.040> basically 00:01:55.870 --> 00:01:55.880 align:start position:0% you know Keeps Us sane basically 00:01:55.880 --> 00:01:57.990 align:start position:0% you know Keeps Us sane basically automated<00:01:56.360> releases<00:01:56.759> and<00:01:56.960> updates<00:01:57.439> and<00:01:57.600> so<00:01:57.840> we 00:01:57.990 --> 00:01:58.000 align:start position:0% automated releases and updates and so we 00:01:58.000 --> 00:01:59.190 align:start position:0% automated releases and updates and so we actually<00:01:58.240> have<00:01:58.399> it<00:01:58.520> you<00:01:58.640> know<00:01:58.840> that<00:01:59.000> when<00:01:59.079> we 00:01:59.190 --> 00:01:59.200 align:start position:0% actually have it you know that when we 00:01:59.200 --> 00:02:01.429 align:start position:0% actually have it you know that when we have<00:01:59.399> those<00:02:00.039> six<00:02:00.320> dependency<00:02:00.799> chains<00:02:01.200> going 00:02:01.429 --> 00:02:01.439 align:start position:0% have those six dependency chains going 00:02:01.439 --> 00:02:03.429 align:start position:0% have those six dependency chains going on<00:02:01.759> we<00:02:02.079> six<00:02:02.320> deep<00:02:02.600> dependency<00:02:03.000> chains<00:02:03.320> if 00:02:03.429 --> 00:02:03.439 align:start position:0% on we six deep dependency chains if 00:02:03.439 --> 00:02:04.709 align:start position:0% on we six deep dependency chains if there's<00:02:03.600> an<00:02:03.759> update<00:02:04.039> to<00:02:04.159> one<00:02:04.240> of<00:02:04.360> our<00:02:04.479> pieces 00:02:04.709 --> 00:02:04.719 align:start position:0% there's an update to one of our pieces 00:02:04.719 --> 00:02:06.870 align:start position:0% there's an update to one of our pieces of<00:02:04.920> software<00:02:05.640> it<00:02:05.799> automatically<00:02:06.320> pushes<00:02:06.680> down 00:02:06.870 --> 00:02:06.880 align:start position:0% of software it automatically pushes down 00:02:06.880 --> 00:02:08.469 align:start position:0% of software it automatically pushes down the<00:02:07.039> chain<00:02:07.280> to<00:02:07.439> the<00:02:07.520> next<00:02:07.719> piece<00:02:07.920> of<00:02:08.080> software 00:02:08.469 --> 00:02:08.479 align:start position:0% the chain to the next piece of software 00:02:08.479 --> 00:02:12.390 align:start position:0% the chain to the next piece of software for<00:02:08.840> us<00:02:09.840> um<00:02:10.399> and<00:02:10.560> one<00:02:10.679> of<00:02:11.120> the<00:02:12.120> kind<00:02:12.239> of 00:02:12.390 --> 00:02:12.400 align:start position:0% for us um and one of the kind of 00:02:12.400 --> 00:02:14.390 align:start position:0% for us um and one of the kind of challenges<00:02:12.920> that<00:02:13.040> you<00:02:13.200> might<00:02:13.440> notice<00:02:13.840> is<00:02:14.239> you 00:02:14.390 --> 00:02:14.400 align:start position:0% challenges that you might notice is you 00:02:14.400 --> 00:02:15.270 align:start position:0% challenges that you might notice is you know<00:02:14.519> that<00:02:14.640> software<00:02:14.959> goes<00:02:15.120> through 00:02:15.270 --> 00:02:15.280 align:start position:0% know that software goes through 00:02:15.280 --> 00:02:17.190 align:start position:0% know that software goes through different<00:02:15.519> life<00:02:15.720> cycles<00:02:16.239> right<00:02:16.400> there's<00:02:17.080> when 00:02:17.190 --> 00:02:17.200 align:start position:0% different life cycles right there's when 00:02:17.200 --> 00:02:18.589 align:start position:0% different life cycles right there's when you<00:02:17.319> first<00:02:17.519> start<00:02:17.760> developing<00:02:18.120> a<00:02:18.239> piece<00:02:18.400> of 00:02:18.589 --> 00:02:18.599 align:start position:0% you first start developing a piece of 00:02:18.599 --> 00:02:20.150 align:start position:0% you first start developing a piece of software<00:02:19.120> you're<00:02:19.239> in<00:02:19.440> Rapid<00:02:19.760> development 00:02:20.150 --> 00:02:20.160 align:start position:0% software you're in Rapid development 00:02:20.160 --> 00:02:21.670 align:start position:0% software you're in Rapid development mode<00:02:20.400> you're<00:02:20.599> prototyping<00:02:21.200> you're<00:02:21.360> trying<00:02:21.560> to 00:02:21.670 --> 00:02:21.680 align:start position:0% mode you're prototyping you're trying to 00:02:21.680 --> 00:02:23.509 align:start position:0% mode you're prototyping you're trying to move<00:02:21.920> as<00:02:22.040> quickly<00:02:22.360> as<00:02:22.599> possible<00:02:23.280> you<00:02:23.400> don't 00:02:23.509 --> 00:02:23.519 align:start position:0% move as quickly as possible you don't 00:02:23.519 --> 00:02:26.030 align:start position:0% move as quickly as possible you don't want<00:02:23.599> to<00:02:23.680> be<00:02:23.879> slowed<00:02:24.360> down<00:02:25.360> um<00:02:25.560> and<00:02:25.720> that<00:02:25.840> looks 00:02:26.030 --> 00:02:26.040 align:start position:0% want to be slowed down um and that looks 00:02:26.040 --> 00:02:29.030 align:start position:0% want to be slowed down um and that looks a<00:02:26.200> lot<00:02:26.480> different<00:02:26.959> than<00:02:27.599> when<00:02:27.959> you're<00:02:28.280> in<00:02:28.920> kind 00:02:29.030 --> 00:02:29.040 align:start position:0% a lot different than when you're in kind 00:02:29.040 --> 00:02:30.990 align:start position:0% a lot different than when you're in kind of<00:02:29.280> the<00:02:29.560> the<00:02:29.920> later<00:02:30.160> stages<00:02:30.480> of<00:02:30.560> a<00:02:30.760> project 00:02:30.990 --> 00:02:31.000 align:start position:0% of the the later stages of a project 00:02:31.000 --> 00:02:32.790 align:start position:0% of the the later stages of a project where<00:02:31.080> you're<00:02:31.200> just<00:02:31.400> evolving<00:02:32.239> the<00:02:32.400> software 00:02:32.790 --> 00:02:32.800 align:start position:0% where you're just evolving the software 00:02:32.800 --> 00:02:34.589 align:start position:0% where you're just evolving the software over<00:02:32.959> time<00:02:33.120> and<00:02:33.200> you<00:02:33.319> have<00:02:33.400> a<00:02:33.480> lot<00:02:33.599> more<00:02:33.800> tests 00:02:34.589 --> 00:02:34.599 align:start position:0% over time and you have a lot more tests 00:02:34.599 --> 00:02:37.030 align:start position:0% over time and you have a lot more tests there<00:02:34.760> to<00:02:35.000> guide<00:02:35.200> you<00:02:35.440> so<00:02:36.160> you<00:02:36.440> you<00:02:36.680> need<00:02:36.840> to 00:02:37.030 --> 00:02:37.040 align:start position:0% there to guide you so you you need to 00:02:37.040 --> 00:02:38.309 align:start position:0% there to guide you so you you need to accept<00:02:37.400> that<00:02:37.519> there<00:02:37.599> are<00:02:37.760> different<00:02:38.080> life 00:02:38.309 --> 00:02:38.319 align:start position:0% accept that there are different life 00:02:38.319 --> 00:02:39.949 align:start position:0% accept that there are different life cycles<00:02:38.640> to<00:02:38.800> software<00:02:39.159> development<00:02:39.599> and<00:02:39.760> for 00:02:39.949 --> 00:02:39.959 align:start position:0% cycles to software development and for 00:02:39.959 --> 00:02:42.509 align:start position:0% cycles to software development and for example<00:02:40.760> keep<00:02:41.080> GitHub<00:02:41.640> enforcement<00:02:42.159> turned 00:02:42.509 --> 00:02:42.519 align:start position:0% example keep GitHub enforcement turned 00:02:42.519 --> 00:02:44.949 align:start position:0% example keep GitHub enforcement turned off<00:02:42.840> at<00:02:42.959> the<00:02:43.080> beginning<00:02:43.560> of<00:02:43.800> the<00:02:44.440> development 00:02:44.949 --> 00:02:44.959 align:start position:0% off at the beginning of the development 00:02:44.959 --> 00:02:46.470 align:start position:0% off at the beginning of the development and<00:02:45.120> then<00:02:45.319> you<00:02:45.440> know<00:02:45.560> a<00:02:45.680> couple<00:02:45.959> months<00:02:46.159> in<00:02:46.319> or 00:02:46.470 --> 00:02:46.480 align:start position:0% and then you know a couple months in or 00:02:46.480 --> 00:02:48.990 align:start position:0% and then you know a couple months in or a<00:02:46.560> couple<00:02:46.800> weeks<00:02:47.040> in<00:02:47.519> turn<00:02:47.800> on<00:02:48.080> that<00:02:48.280> GitHub 00:02:48.990 --> 00:02:49.000 align:start position:0% a couple weeks in turn on that GitHub 00:02:49.000 --> 00:02:51.030 align:start position:0% a couple weeks in turn on that GitHub enforcement<00:02:50.000> the<00:02:50.120> Second<00:02:50.440> Challenge<00:02:50.840> is 00:02:51.030 --> 00:02:51.040 align:start position:0% enforcement the Second Challenge is 00:02:51.040 --> 00:02:52.750 align:start position:0% enforcement the Second Challenge is personnel<00:02:51.640> and<00:02:51.840> this<00:02:52.120> maybe<00:02:52.360> it<00:02:52.519> even 00:02:52.750 --> 00:02:52.760 align:start position:0% personnel and this maybe it even 00:02:52.760 --> 00:02:55.470 align:start position:0% personnel and this maybe it even deserves<00:02:53.120> to<00:02:53.239> be<00:02:53.319> the<00:02:53.440> third<00:02:53.840> challenge<00:02:54.840> um 00:02:55.470 --> 00:02:55.480 align:start position:0% deserves to be the third challenge um 00:02:55.480 --> 00:02:57.030 align:start position:0% deserves to be the third challenge um because<00:02:55.760> this<00:02:55.879> is<00:02:56.000> you<00:02:56.120> know<00:02:56.280> the<00:02:56.360> medium 00:02:57.030 --> 00:02:57.040 align:start position:0% because this is you know the medium 00:02:57.040 --> 00:02:58.949 align:start position:0% because this is you know the medium difficulty<00:02:57.319> challenge<00:02:58.280> but<00:02:58.440> what<00:02:58.560> I<00:02:58.680> like<00:02:58.840> to 00:02:58.949 --> 00:02:58.959 align:start position:0% difficulty challenge but what I like to 00:02:58.959 --> 00:03:01.070 align:start position:0% difficulty challenge but what I like to tell<00:02:59.200> new<00:02:59.440> hires<00:02:59.879> at<00:03:00.000> runtime<00:03:00.319> verification 00:03:01.070 --> 00:03:01.080 align:start position:0% tell new hires at runtime verification 00:03:01.080 --> 00:03:03.830 align:start position:0% tell new hires at runtime verification is<00:03:01.280> that<00:03:01.840> learning<00:03:02.200> to<00:03:02.440> program<00:03:02.800> is<00:03:03.040> easy 00:03:03.830 --> 00:03:03.840 align:start position:0% is that learning to program is easy 00:03:03.840 --> 00:03:05.949 align:start position:0% is that learning to program is easy learning<00:03:04.159> to<00:03:04.319> program<00:03:04.599> in<00:03:04.680> a<00:03:04.799> group<00:03:05.040> is<00:03:05.239> hard 00:03:05.949 --> 00:03:05.959 align:start position:0% learning to program in a group is hard 00:03:05.959 --> 00:03:08.229 align:start position:0% learning to program in a group is hard right<00:03:06.680> and<00:03:07.120> the<00:03:07.319> key<00:03:07.519> thing<00:03:07.799> to<00:03:07.879> remember<00:03:08.159> is 00:03:08.229 --> 00:03:08.239 align:start position:0% right and the key thing to remember is 00:03:08.239 --> 00:03:09.710 align:start position:0% right and the key thing to remember is that<00:03:08.360> you<00:03:08.440> have<00:03:08.519> to<00:03:08.599> be<00:03:08.799> respectful<00:03:09.400> of<00:03:09.519> other 00:03:09.710 --> 00:03:09.720 align:start position:0% that you have to be respectful of other 00:03:09.720 --> 00:03:12.430 align:start position:0% that you have to be respectful of other people's<00:03:10.080> time<00:03:10.640> right<00:03:11.519> and<00:03:11.840> uh<00:03:11.959> you<00:03:12.080> know<00:03:12.239> one 00:03:12.430 --> 00:03:12.440 align:start position:0% people's time right and uh you know one 00:03:12.440 --> 00:03:13.789 align:start position:0% people's time right and uh you know one thing<00:03:12.560> to<00:03:12.760> keep<00:03:12.879> in<00:03:13.000> mind<00:03:13.200> is<00:03:13.319> it's<00:03:13.519> always 00:03:13.789 --> 00:03:13.799 align:start position:0% thing to keep in mind is it's always 00:03:13.799 --> 00:03:15.630 align:start position:0% thing to keep in mind is it's always harder<00:03:14.040> to<00:03:14.200> read<00:03:14.480> code<00:03:14.879> than<00:03:15.000> to<00:03:15.159> write<00:03:15.400> code 00:03:15.630 --> 00:03:15.640 align:start position:0% harder to read code than to write code 00:03:15.640 --> 00:03:17.390 align:start position:0% harder to read code than to write code and<00:03:15.799> so<00:03:15.959> you're<00:03:16.080> submitting<00:03:16.480> code<00:03:16.760> changes<00:03:17.200> or 00:03:17.390 --> 00:03:17.400 align:start position:0% and so you're submitting code changes or 00:03:17.400 --> 00:03:19.430 align:start position:0% and so you're submitting code changes or something<00:03:17.720> like<00:03:17.920> that<00:03:18.680> and<00:03:18.879> it<00:03:18.959> was<00:03:19.120> easy<00:03:19.319> for 00:03:19.430 --> 00:03:19.440 align:start position:0% something like that and it was easy for 00:03:19.440 --> 00:03:20.390 align:start position:0% something like that and it was easy for you<00:03:19.519> to<00:03:19.640> read<00:03:19.799> it<00:03:19.920> because<00:03:20.120> you<00:03:20.200> have<00:03:20.319> the 00:03:20.390 --> 00:03:20.400 align:start position:0% you to read it because you have the 00:03:20.400 --> 00:03:22.350 align:start position:0% you to read it because you have the intent<00:03:20.760> in<00:03:20.879> your<00:03:21.040> mind<00:03:21.440> and<00:03:21.560> you<00:03:21.799> translated 00:03:22.350 --> 00:03:22.360 align:start position:0% intent in your mind and you translated 00:03:22.360 --> 00:03:24.350 align:start position:0% intent in your mind and you translated it<00:03:22.519> into<00:03:22.799> code<00:03:23.400> it's<00:03:23.560> much<00:03:23.720> harder<00:03:23.959> to<00:03:24.080> go<00:03:24.200> from 00:03:24.350 --> 00:03:24.360 align:start position:0% it into code it's much harder to go from 00:03:24.360 --> 00:03:25.990 align:start position:0% it into code it's much harder to go from that<00:03:24.519> code<00:03:24.720> and<00:03:24.879> translate<00:03:25.280> it<00:03:25.440> back<00:03:25.640> into<00:03:25.840> the 00:03:25.990 --> 00:03:26.000 align:start position:0% that code and translate it back into the 00:03:26.000 --> 00:03:28.429 align:start position:0% that code and translate it back into the intent<00:03:26.400> as<00:03:26.519> the<00:03:26.640> pr<00:03:26.920> reviewer<00:03:27.400> so<00:03:27.920> as<00:03:28.000> a<00:03:28.200> person 00:03:28.429 --> 00:03:28.439 align:start position:0% intent as the pr reviewer so as a person 00:03:28.439 --> 00:03:29.910 align:start position:0% intent as the pr reviewer so as a person who's<00:03:28.640> authoring<00:03:29.120> code<00:03:29.319> you<00:03:29.400> need<00:03:29.519> to<00:03:29.799> make 00:03:29.910 --> 00:03:29.920 align:start position:0% who's authoring code you need to make 00:03:29.920 --> 00:03:31.630 align:start position:0% who's authoring code you need to make sure<00:03:30.040> that<00:03:30.120> your<00:03:30.239> code<00:03:30.480> is<00:03:31.000> you<00:03:31.120> know<00:03:31.319> small 00:03:31.630 --> 00:03:31.640 align:start position:0% sure that your code is you know small 00:03:31.640 --> 00:03:33.910 align:start position:0% sure that your code is you know small changes<00:03:32.280> isolated<00:03:32.760> changes<00:03:33.159> easy<00:03:33.400> to<00:03:33.599> read 00:03:33.910 --> 00:03:33.920 align:start position:0% changes isolated changes easy to read 00:03:33.920 --> 00:03:35.869 align:start position:0% changes isolated changes easy to read well<00:03:34.159> tested<00:03:34.799> so<00:03:34.959> that<00:03:35.040> the<00:03:35.159> pr<00:03:35.400> reviewer<00:03:35.760> has 00:03:35.869 --> 00:03:35.879 align:start position:0% well tested so that the pr reviewer has 00:03:35.879 --> 00:03:38.470 align:start position:0% well tested so that the pr reviewer has an<00:03:36.080> easy<00:03:36.400> time<00:03:36.680> pressing<00:03:37.000> the<00:03:37.120> approv<00:03:37.480> button 00:03:38.470 --> 00:03:38.480 align:start position:0% an easy time pressing the approv button 00:03:38.480 --> 00:03:41.110 align:start position:0% an easy time pressing the approv button um<00:03:39.439> you<00:03:39.560> know<00:03:39.799> remote<00:03:40.360> remote<00:03:40.640> work<00:03:40.840> obviously 00:03:41.110 --> 00:03:41.120 align:start position:0% um you know remote remote work obviously 00:03:41.120 --> 00:03:42.550 align:start position:0% um you know remote remote work obviously makes<00:03:41.280> this<00:03:41.400> a<00:03:41.480> lot<00:03:41.640> harder<00:03:42.200> you<00:03:42.319> know<00:03:42.439> when 00:03:42.550 --> 00:03:42.560 align:start position:0% makes this a lot harder you know when 00:03:42.560 --> 00:03:44.470 align:start position:0% makes this a lot harder you know when you're<00:03:42.680> all<00:03:42.840> in<00:03:42.959> the<00:03:43.280> same<00:03:43.599> office<00:03:44.000> together 00:03:44.470 --> 00:03:44.480 align:start position:0% you're all in the same office together 00:03:44.480 --> 00:03:45.869 align:start position:0% you're all in the same office together you<00:03:44.599> just<00:03:44.720> turn<00:03:44.920> around<00:03:45.239> hey<00:03:45.519> like<00:03:45.760> what<00:03:45.840> do 00:03:45.869 --> 00:03:45.879 align:start position:0% you just turn around hey like what do 00:03:45.879 --> 00:03:47.270 align:start position:0% you just turn around hey like what do you<00:03:45.959> think<00:03:46.080> of<00:03:46.200> this<00:03:46.319> change<00:03:46.640> and<00:03:46.760> you<00:03:46.959> work<00:03:47.159> on 00:03:47.270 --> 00:03:47.280 align:start position:0% you think of this change and you work on 00:03:47.280 --> 00:03:49.070 align:start position:0% you think of this change and you work on the<00:03:47.400> same<00:03:47.599> screen<00:03:48.480> but<00:03:48.640> now<00:03:48.760> we're<00:03:48.879> talking 00:03:49.070 --> 00:03:49.080 align:start position:0% the same screen but now we're talking 00:03:49.080 --> 00:03:50.750 align:start position:0% the same screen but now we're talking about<00:03:49.239> different<00:03:49.560> time<00:03:49.799> zones<00:03:50.280> and<00:03:50.519> there's 00:03:50.750 --> 00:03:50.760 align:start position:0% about different time zones and there's 00:03:50.760 --> 00:03:52.390 align:start position:0% about different time zones and there's delays<00:03:51.280> associated<00:03:51.760> with<00:03:51.920> that<00:03:52.040> so<00:03:52.159> you<00:03:52.280> have 00:03:52.390 --> 00:03:52.400 align:start position:0% delays associated with that so you have 00:03:52.400 --> 00:03:53.750 align:start position:0% delays associated with that so you have to<00:03:52.519> keep<00:03:52.720> all<00:03:52.840> that<00:03:52.959> in<00:03:53.079> mind<00:03:53.280> and<00:03:53.439> actually 00:03:53.750 --> 00:03:53.760 align:start position:0% to keep all that in mind and actually 00:03:53.760 --> 00:03:55.550 align:start position:0% to keep all that in mind and actually keep<00:03:53.920> it<00:03:54.000> in<00:03:54.120> your<00:03:54.239> mental<00:03:54.560> model<00:03:55.200> for<00:03:55.400> your 00:03:55.550 --> 00:03:55.560 align:start position:0% keep it in your mental model for your 00:03:55.560 --> 00:03:58.229 align:start position:0% keep it in your mental model for your development<00:03:56.519> um<00:03:57.120> and<00:03:57.200> so<00:03:57.439> here<00:03:57.680> process<00:03:58.040> is 00:03:58.229 --> 00:03:58.239 align:start position:0% development um and so here process is 00:03:58.239 --> 00:04:00.270 align:start position:0% development um and so here process is key<00:03:58.879> example<00:03:59.159> at<00:03:59.280> runtime<00:03:59.760> verification<00:04:00.159> I 00:04:00.270 --> 00:04:00.280 align:start position:0% key example at runtime verification I 00:04:00.280 --> 00:04:01.990 align:start position:0% key example at runtime verification I let<00:04:00.439> everyone<00:04:00.760> know<00:04:01.280> you<00:04:01.400> know<00:04:01.680> beginning<00:04:01.959> of 00:04:01.990 --> 00:04:02.000 align:start position:0% let everyone know you know beginning of 00:04:02.000 --> 00:04:03.789 align:start position:0% let everyone know you know beginning of your<00:04:02.239> day<00:04:02.480> you<00:04:02.640> clear<00:04:02.879> your<00:04:02.959> slack<00:04:03.319> messages 00:04:03.789 --> 00:04:03.799 align:start position:0% your day you clear your slack messages 00:04:03.799 --> 00:04:05.550 align:start position:0% your day you clear your slack messages first<00:04:04.519> then<00:04:04.599> you<00:04:04.720> do<00:04:04.840> your<00:04:05.000> poll<00:04:05.239> request 00:04:05.550 --> 00:04:05.560 align:start position:0% first then you do your poll request 00:04:05.560 --> 00:04:07.750 align:start position:0% first then you do your poll request reviews<00:04:06.319> and<00:04:06.439> then<00:04:06.560> you<00:04:06.720> do<00:04:07.079> bulk<00:04:07.439> code 00:04:07.750 --> 00:04:07.760 align:start position:0% reviews and then you do bulk code 00:04:07.760 --> 00:04:09.270 align:start position:0% reviews and then you do bulk code development<00:04:08.120> on<00:04:08.239> new<00:04:08.519> code<00:04:08.920> and<00:04:09.040> then<00:04:09.159> you 00:04:09.270 --> 00:04:09.280 align:start position:0% development on new code and then you 00:04:09.280 --> 00:04:10.670 align:start position:0% development on new code and then you open<00:04:09.519> new<00:04:09.680> poll<00:04:09.879> requests<00:04:10.200> at<00:04:10.280> the<00:04:10.360> end<00:04:10.480> of<00:04:10.560> the 00:04:10.670 --> 00:04:10.680 align:start position:0% open new poll requests at the end of the 00:04:10.680 --> 00:04:12.470 align:start position:0% open new poll requests at the end of the day<00:04:11.120> you<00:04:11.239> do<00:04:11.360> your<00:04:11.480> poll<00:04:11.720> request<00:04:12.000> reviews 00:04:12.470 --> 00:04:12.480 align:start position:0% day you do your poll request reviews 00:04:12.480 --> 00:04:14.789 align:start position:0% day you do your poll request reviews first<00:04:12.959> because<00:04:13.239> that's<00:04:13.560> blocking<00:04:14.120> someone 00:04:14.789 --> 00:04:14.799 align:start position:0% first because that's blocking someone 00:04:14.799 --> 00:04:16.430 align:start position:0% first because that's blocking someone right<00:04:15.000> that<00:04:15.120> is<00:04:15.280> causing<00:04:15.599> a<00:04:15.760> synchronization 00:04:16.430 --> 00:04:16.440 align:start position:0% right that is causing a synchronization 00:04:16.440 --> 00:04:18.150 align:start position:0% right that is causing a synchronization point<00:04:16.680> between<00:04:16.919> you<00:04:17.040> and<00:04:17.199> someone<00:04:17.440> else<00:04:18.040> they 00:04:18.150 --> 00:04:18.160 align:start position:0% point between you and someone else they 00:04:18.160 --> 00:04:20.069 align:start position:0% point between you and someone else they might<00:04:18.320> be<00:04:18.440> on<00:04:18.560> the<00:04:18.639> other<00:04:18.840> side<00:04:18.959> of<00:04:19.079> the<00:04:19.199> world 00:04:20.069 --> 00:04:20.079 align:start position:0% might be on the other side of the world 00:04:20.079 --> 00:04:21.870 align:start position:0% might be on the other side of the world and<00:04:20.239> suddenly<00:04:20.880> if<00:04:21.000> you<00:04:21.160> don't<00:04:21.359> do<00:04:21.519> that<00:04:21.639> PO 00:04:21.870 --> 00:04:21.880 align:start position:0% and suddenly if you don't do that PO 00:04:21.880 --> 00:04:23.510 align:start position:0% and suddenly if you don't do that PO request<00:04:22.160> review<00:04:22.400> you're<00:04:22.520> delaying<00:04:22.960> them<00:04:23.199> by<00:04:23.360> a 00:04:23.510 --> 00:04:23.520 align:start position:0% request review you're delaying them by a 00:04:23.520 --> 00:04:25.150 align:start position:0% request review you're delaying them by a day<00:04:23.800> and<00:04:23.880> then<00:04:24.040> that<00:04:24.120> maybe<00:04:24.560> delays<00:04:24.840> You<00:04:25.000> by 00:04:25.150 --> 00:04:25.160 align:start position:0% day and then that maybe delays You by 00:04:25.160 --> 00:04:26.950 align:start position:0% day and then that maybe delays You by day<00:04:25.280> and<00:04:25.360> so<00:04:25.479> suddenly<00:04:26.120> you<00:04:26.240> know<00:04:26.479> some<00:04:26.680> small 00:04:26.950 --> 00:04:26.960 align:start position:0% day and so suddenly you know some small 00:04:26.960 --> 00:04:29.430 align:start position:0% day and so suddenly you know some small change<00:04:27.600> gets<00:04:27.840> delayed<00:04:28.320> two<00:04:28.680> days<00:04:28.960> maybe<00:04:29.199> 3 00:04:29.430 --> 00:04:29.440 align:start position:0% change gets delayed two days maybe 3 00:04:29.440 --> 00:04:31.310 align:start position:0% change gets delayed two days maybe 3 days<00:04:30.080> if<00:04:30.199> we're<00:04:30.320> talking<00:04:30.520> about<00:04:30.639> an<00:04:30.720> 8we 00:04:31.310 --> 00:04:31.320 align:start position:0% days if we're talking about an 8we 00:04:31.320 --> 00:04:33.590 align:start position:0% days if we're talking about an 8we project<00:04:32.080> and<00:04:32.160> you<00:04:32.280> have<00:04:32.400> a<00:04:32.600> handful<00:04:33.000> of<00:04:33.160> delays 00:04:33.590 --> 00:04:33.600 align:start position:0% project and you have a handful of delays 00:04:33.600 --> 00:04:35.550 align:start position:0% project and you have a handful of delays like<00:04:33.840> that<00:04:34.240> you've<00:04:34.479> lost<00:04:34.720> two<00:04:34.919> weeks<00:04:35.320> on<00:04:35.440> that 00:04:35.550 --> 00:04:35.560 align:start position:0% like that you've lost two weeks on that 00:04:35.560 --> 00:04:39.670 align:start position:0% like that you've lost two weeks on that 8we<00:04:36.080> project<00:04:36.600> right<00:04:36.919> it's<00:04:37.880> not<00:04:38.080> good<00:04:38.919> um 00:04:39.670 --> 00:04:39.680 align:start position:0% 8we project right it's not good um 00:04:39.680 --> 00:04:42.390 align:start position:0% 8we project right it's not good um anyway<00:04:40.680> uh<00:04:40.880> next<00:04:41.080> Slide<00:04:41.720> the<00:04:41.840> third<00:04:42.080> challenge 00:04:42.390 --> 00:04:42.400 align:start position:0% anyway uh next Slide the third challenge 00:04:42.400 --> 00:04:44.150 align:start position:0% anyway uh next Slide the third challenge is<00:04:42.560> money<00:04:43.039> and<00:04:43.240> you<00:04:43.400> know<00:04:43.639> if<00:04:43.720> you<00:04:43.840> know<00:04:43.960> how<00:04:44.039> to 00:04:44.150 --> 00:04:44.160 align:start position:0% is money and you know if you know how to 00:04:44.160 --> 00:04:47.469 align:start position:0% is money and you know if you know how to solve<00:04:44.440> this<00:04:45.280> please<00:04:45.720> let<00:04:45.840> me<00:04:46.240> know<00:04:47.240> uh<00:04:47.360> the 00:04:47.469 --> 00:04:47.479 align:start position:0% solve this please let me know uh the 00:04:47.479 --> 00:04:51.310 align:start position:0% solve this please let me know uh the solution<00:04:47.840> I<00:04:47.960> found<00:04:48.240> is<00:04:48.360> to<00:04:48.520> beg<00:04:49.400> and<00:04:50.280> the<00:04:51.199> you 00:04:51.310 --> 00:04:51.320 align:start position:0% solution I found is to beg and the you 00:04:51.320 --> 00:04:53.029 align:start position:0% solution I found is to beg and the you know<00:04:51.639> the<00:04:51.840> the<00:04:52.000> problem<00:04:52.240> with<00:04:52.479> begging<00:04:52.880> is 00:04:53.029 --> 00:04:53.039 align:start position:0% know the the problem with begging is 00:04:53.039 --> 00:04:54.749 align:start position:0% know the the problem with begging is that<00:04:53.240> everyone<00:04:53.680> starts<00:04:53.880> begging<00:04:54.560> and<00:04:54.639> you 00:04:54.749 --> 00:04:54.759 align:start position:0% that everyone starts begging and you 00:04:54.759 --> 00:04:56.390 align:start position:0% that everyone starts begging and you need<00:04:54.880> to<00:04:55.039> have<00:04:55.199> like<00:04:55.280> a<00:04:55.400> begging<00:04:55.880> process<00:04:56.240> and 00:04:56.390 --> 00:04:56.400 align:start position:0% need to have like a begging process and 00:04:56.400 --> 00:04:57.749 align:start position:0% need to have like a begging process and have<00:04:56.520> a<00:04:56.600> little<00:04:56.800> structure<00:04:57.199> to<00:04:57.360> it<00:04:57.479> and<00:04:57.560> so<00:04:57.680> you 00:04:57.749 --> 00:04:57.759 align:start position:0% have a little structure to it and so you 00:04:57.759 --> 00:04:59.909 align:start position:0% have a little structure to it and so you have<00:04:57.880> like<00:04:58.039> grants<00:04:58.400> and<00:04:58.600> retr<00:04:59.000> funding<00:04:59.720> and 00:04:59.909 --> 00:04:59.919 align:start position:0% have like grants and retr funding and 00:04:59.919 --> 00:05:01.510 align:start position:0% have like grants and retr funding and side<00:05:00.199> quests<00:05:00.560> where<00:05:00.720> you<00:05:00.800> get<00:05:00.919> people<00:05:01.080> to<00:05:01.199> fund 00:05:01.510 --> 00:05:01.520 align:start position:0% side quests where you get people to fund 00:05:01.520 --> 00:05:02.830 align:start position:0% side quests where you get people to fund one<00:05:01.720> thing<00:05:01.919> but<00:05:02.039> then<00:05:02.120> you<00:05:02.240> develop<00:05:02.600> another 00:05:02.830 --> 00:05:02.840 align:start position:0% one thing but then you develop another 00:05:02.840 --> 00:05:05.310 align:start position:0% one thing but then you develop another thing<00:05:03.039> as<00:05:03.280> well<00:05:04.280> um<00:05:04.680> and<00:05:04.800> the<00:05:04.960> problem<00:05:05.160> with 00:05:05.310 --> 00:05:05.320 align:start position:0% thing as well um and the problem with 00:05:05.320 --> 00:05:06.670 align:start position:0% thing as well um and the problem with structured<00:05:05.720> begging<00:05:06.000> is<00:05:06.120> that<00:05:06.199> it<00:05:06.280> becomes<00:05:06.520> a 00:05:06.670 --> 00:05:06.680 align:start position:0% structured begging is that it becomes a 00:05:06.680 --> 00:05:08.990 align:start position:0% structured begging is that it becomes a game<00:05:07.320> and<00:05:07.520> big<00:05:07.840> players<00:05:08.120> are<00:05:08.320> better<00:05:08.520> at<00:05:08.720> games 00:05:08.990 --> 00:05:09.000 align:start position:0% game and big players are better at games 00:05:09.000 --> 00:05:10.629 align:start position:0% game and big players are better at games than<00:05:09.199> small<00:05:09.520> players<00:05:09.919> and<00:05:10.000> so<00:05:10.199> then<00:05:10.320> the<00:05:10.440> small 00:05:10.629 --> 00:05:10.639 align:start position:0% than small players and so then the small 00:05:10.639 --> 00:05:12.189 align:start position:0% than small players and so then the small players<00:05:10.960> Resort<00:05:11.320> back<00:05:11.440> to<00:05:11.600> unstructured 00:05:12.189 --> 00:05:12.199 align:start position:0% players Resort back to unstructured 00:05:12.199 --> 00:05:13.909 align:start position:0% players Resort back to unstructured begging<00:05:12.600> and<00:05:12.759> so<00:05:13.400> I<00:05:13.479> don't<00:05:13.560> know<00:05:13.680> we're<00:05:13.800> back 00:05:13.909 --> 00:05:13.919 align:start position:0% begging and so I don't know we're back 00:05:13.919 --> 00:05:17.550 align:start position:0% begging and so I don't know we're back at<00:05:14.039> square<00:05:14.280> one<00:05:14.600> so<00:05:15.199> anyway<00:05:16.120> that's<00:05:16.440> my<00:05:16.680> talk 00:05:17.550 --> 00:05:17.560 align:start position:0% at square one so anyway that's my talk 00:05:17.560 --> 00:05:19.270 align:start position:0% at square one so anyway that's my talk uh<00:05:17.919> you<00:05:18.039> know<00:05:18.479> solve<00:05:18.800> the<00:05:18.919> technical 00:05:19.270 --> 00:05:19.280 align:start position:0% uh you know solve the technical 00:05:19.280 --> 00:05:20.950 align:start position:0% uh you know solve the technical challenges<00:05:19.759> first<00:05:20.039> prioritize<00:05:20.600> those<00:05:20.800> that's 00:05:20.950 --> 00:05:20.960 align:start position:0% challenges first prioritize those that's 00:05:20.960 --> 00:05:22.990 align:start position:0% challenges first prioritize those that's the<00:05:21.080> easiest<00:05:21.479> part<00:05:22.280> make<00:05:22.400> sure<00:05:22.600> as<00:05:22.720> you<00:05:22.840> on 00:05:22.990 --> 00:05:23.000 align:start position:0% the easiest part make sure as you on 00:05:23.000 --> 00:05:24.909 align:start position:0% the easiest part make sure as you on board<00:05:23.280> people<00:05:23.840> that<00:05:24.000> you<00:05:24.280> make<00:05:24.479> them<00:05:24.600> aware<00:05:24.840> of 00:05:24.909 --> 00:05:24.919 align:start position:0% board people that you make them aware of 00:05:24.919 --> 00:05:27.150 align:start position:0% board people that you make them aware of the<00:05:25.039> Personnel<00:05:25.520> challenges<00:05:26.479> and<00:05:26.639> then<00:05:26.960> come 00:05:27.150 --> 00:05:27.160 align:start position:0% the Personnel challenges and then come 00:05:27.160 --> 00:05:28.070 align:start position:0% the Personnel challenges and then come let<00:05:27.240> me<00:05:27.360> know<00:05:27.479> when<00:05:27.600> you<00:05:27.680> figure<00:05:27.880> out<00:05:28.000> the 00:05:28.070 --> 00:05:28.080 align:start position:0% let me know when you figure out the 00:05:28.080 --> 00:05:30.230 align:start position:0% let me know when you figure out the money<00:05:28.360> thing 00:05:30.230 --> 00:05:30.240 align:start position:0% money thing 00:05:30.240 --> 00:05:32.670 align:start position:0% money thing thanks<00:05:31.240> thank 00:05:32.670 --> 00:05:32.680 align:start position:0% thanks thank 00:05:32.680 --> 00:05:39.749 align:start position:0% thanks thank you<00:05:33.680> any 00:05:39.749 --> 00:05:39.759 align:start position:0% 00:05:39.759 --> 00:05:44.710 align:start position:0% questions<00:05:40.759> oh<00:05:40.960> there's<00:05:41.199> one 00:05:44.710 --> 00:05:44.720 align:start position:0% 00:05:44.720 --> 00:05:47.430 align:start position:0% here<00:05:45.720> great<00:05:46.000> presentation<00:05:46.880> I<00:05:47.000> just<00:05:47.120> want<00:05:47.319> to 00:05:47.430 --> 00:05:47.440 align:start position:0% here great presentation I just want to 00:05:47.440 --> 00:05:49.309 align:start position:0% here great presentation I just want to know<00:05:47.639> more<00:05:47.840> about<00:05:48.039> runtime<00:05:48.560> verification<00:05:49.199> I 00:05:49.309 --> 00:05:49.319 align:start position:0% know more about runtime verification I 00:05:49.319 --> 00:05:52.790 align:start position:0% know more about runtime verification I just<00:05:49.639> check<00:05:49.840> in<00:05:50.000> the<00:05:50.280> website<00:05:51.280> um<00:05:51.919> but<00:05:52.520> it's 00:05:52.790 --> 00:05:52.800 align:start position:0% just check in the website um but it's 00:05:52.800 --> 00:05:54.790 align:start position:0% just check in the website um but it's much<00:05:53.360> better<00:05:53.720> for<00:05:53.840> you<00:05:53.960> to<00:05:54.120> like<00:05:54.280> introduce 00:05:54.790 --> 00:05:54.800 align:start position:0% much better for you to like introduce 00:05:54.800 --> 00:05:56.670 align:start position:0% much better for you to like introduce what<00:05:54.880> you<00:05:55.039> do<00:05:55.440> and<00:05:55.840> why<00:05:55.960> are<00:05:56.080> you<00:05:56.199> working<00:05:56.440> on 00:05:56.670 --> 00:05:56.680 align:start position:0% what you do and why are you working on 00:05:56.680 --> 00:05:59.629 align:start position:0% what you do and why are you working on open<00:05:56.960> source<00:05:57.840> yeah<00:05:58.000> so<00:05:58.240> we<00:05:58.479> do<00:05:58.840> we<00:05:58.919> do<00:05:59.160> mostly 00:05:59.629 --> 00:05:59.639 align:start position:0% open source yeah so we do we do mostly 00:05:59.639 --> 00:06:00.830 align:start position:0% open source yeah so we do we do mostly formal<00:05:59.919> verification<00:06:00.440> and<00:06:00.560> formal 00:06:00.830 --> 00:06:00.840 align:start position:0% formal verification and formal 00:06:00.840 --> 00:06:02.430 align:start position:0% formal verification and formal verification<00:06:01.319> tooling<00:06:01.880> so<00:06:02.039> we<00:06:02.120> have<00:06:02.280> this 00:06:02.430 --> 00:06:02.440 align:start position:0% verification tooling so we have this 00:06:02.440 --> 00:06:03.749 align:start position:0% verification tooling so we have this project<00:06:02.680> called<00:06:02.840> the<00:06:03.000> K<00:06:03.160> framework<00:06:03.600> that's 00:06:03.749 --> 00:06:03.759 align:start position:0% project called the K framework that's 00:06:03.759 --> 00:06:05.870 align:start position:0% project called the K framework that's kind<00:06:03.880> of<00:06:04.000> our<00:06:04.120> biggest<00:06:04.600> project<00:06:05.479> that<00:06:05.639> is<00:06:05.759> a 00:06:05.870 --> 00:06:05.880 align:start position:0% kind of our biggest project that is a 00:06:05.880 --> 00:06:07.390 align:start position:0% kind of our biggest project that is a tool<00:06:06.199> that<00:06:06.360> enables<00:06:06.720> us<00:06:06.840> to<00:06:06.960> do<00:06:07.080> formal 00:06:07.390 --> 00:06:07.400 align:start position:0% tool that enables us to do formal 00:06:07.400 --> 00:06:09.430 align:start position:0% tool that enables us to do formal verification<00:06:08.080> for<00:06:08.680> any<00:06:08.960> programming 00:06:09.430 --> 00:06:09.440 align:start position:0% verification for any programming 00:06:09.440 --> 00:06:11.710 align:start position:0% verification for any programming language<00:06:10.039> basically<00:06:11.039> um<00:06:11.199> and<00:06:11.319> so<00:06:11.440> we<00:06:11.560> have 00:06:11.710 --> 00:06:11.720 align:start position:0% language basically um and so we have 00:06:11.720 --> 00:06:14.070 align:start position:0% language basically um and so we have formal<00:06:12.000> verification<00:06:12.520> tools<00:06:12.960> for<00:06:13.280> solidity 00:06:14.070 --> 00:06:14.080 align:start position:0% formal verification tools for solidity 00:06:14.080 --> 00:06:16.830 align:start position:0% formal verification tools for solidity for<00:06:14.800> web<00:06:15.039> assembly<00:06:15.599> for<00:06:15.840> rust<00:06:16.319> we<00:06:16.479> also<00:06:16.720> have 00:06:16.830 --> 00:06:16.840 align:start position:0% for web assembly for rust we also have 00:06:16.840 --> 00:06:18.670 align:start position:0% for web assembly for rust we also have for<00:06:17.000> some<00:06:17.199> other<00:06:17.400> blockchain<00:06:17.840> like<00:06:18.000> cardano 00:06:18.670 --> 00:06:18.680 align:start position:0% for some other blockchain like cardano 00:06:18.680 --> 00:06:21.749 align:start position:0% for some other blockchain like cardano and<00:06:18.960> tezos<00:06:19.560> and<00:06:19.800> stuff<00:06:20.039> like<00:06:20.199> that<00:06:20.759> so<00:06:21.560> that 00:06:21.749 --> 00:06:21.759 align:start position:0% and tezos and stuff like that so that 00:06:21.759 --> 00:06:24.070 align:start position:0% and tezos and stuff like that so that require<00:06:22.520> that's<00:06:22.599> a<00:06:22.800> big<00:06:23.280> formal<00:06:23.680> verification 00:06:24.070 --> 00:06:24.080 align:start position:0% require that's a big formal verification 00:06:24.080 --> 00:06:25.950 align:start position:0% require that's a big formal verification is<00:06:24.240> hard<00:06:24.520> software<00:06:24.960> to<00:06:25.160> develop<00:06:25.599> and<00:06:25.720> it's 00:06:25.950 --> 00:06:25.960 align:start position:0% is hard software to develop and it's 00:06:25.960 --> 00:06:27.550 align:start position:0% is hard software to develop and it's used<00:06:26.240> in<00:06:26.319> a<00:06:26.440> bunch<00:06:26.599> of<00:06:26.720> other<00:06:26.960> contexts<00:06:27.400> as 00:06:27.550 --> 00:06:27.560 align:start position:0% used in a bunch of other contexts as 00:06:27.560 --> 00:06:29.309 align:start position:0% used in a bunch of other contexts as well<00:06:27.759> and<00:06:27.919> so<00:06:28.479> we<00:06:28.599> just<00:06:28.720> end<00:06:28.880> up<00:06:29.000> having<00:06:29.160> a<00:06:29.199> lot 00:06:29.309 --> 00:06:29.319 align:start position:0% well and so we just end up having a lot 00:06:29.319 --> 00:06:31.029 align:start position:0% well and so we just end up having a lot of<00:06:29.400> different<00:06:29.759> repositories<00:06:30.440> targeting 00:06:31.029 --> 00:06:31.039 align:start position:0% of different repositories targeting 00:06:31.039 --> 00:06:33.189 align:start position:0% of different repositories targeting different<00:06:32.039> ecosystems<00:06:32.800> and<00:06:32.960> different 00:06:33.189 --> 00:06:33.199 align:start position:0% different ecosystems and different 00:06:33.199 --> 00:06:34.909 align:start position:0% different ecosystems and different programming<00:06:33.599> languages<00:06:34.039> that<00:06:34.160> we<00:06:34.280> do<00:06:34.720> that 00:06:34.909 --> 00:06:34.919 align:start position:0% programming languages that we do that 00:06:34.919 --> 00:06:36.230 align:start position:0% programming languages that we do that far<00:06:35.080> and<00:06:35.160> most<00:06:35.319> of<00:06:35.440> that<00:06:35.560> is<00:06:35.680> done<00:06:35.880> for 00:06:36.230 --> 00:06:36.240 align:start position:0% far and most of that is done for 00:06:36.240 --> 00:06:43.189 align:start position:0% far and most of that is done for security<00:06:36.639> audits<00:06:37.080> basically<00:06:38.039> so<00:06:39.039> thank<00:06:39.240> you 00:06:43.189 --> 00:06:43.199 align:start position:0% 00:06:43.199 --> 00:06:48.430 align:start position:0% MH<00:06:44.199> there's<00:06:44.400> a<00:06:44.599> question<00:06:44.919> over 00:06:48.430 --> 00:06:48.440 align:start position:0% 00:06:48.440 --> 00:06:51.589 align:start position:0% there<00:06:49.440> thanks<00:06:50.080> hi<00:06:50.840> um<00:06:51.039> because<00:06:51.160> you<00:06:51.319> already 00:06:51.589 --> 00:06:51.599 align:start position:0% there thanks hi um because you already 00:06:51.599 --> 00:06:53.550 align:start position:0% there thanks hi um because you already mentioned<00:06:52.160> uh<00:06:52.319> the<00:06:52.400> workflow<00:06:53.000> especially<00:06:53.360> at 00:06:53.550 --> 00:06:53.560 align:start position:0% mentioned uh the workflow especially at 00:06:53.560 --> 00:06:55.270 align:start position:0% mentioned uh the workflow especially at the<00:06:53.680> GitHub<00:06:54.000> pool<00:06:54.199> requests<00:06:54.720> so<00:06:54.960> I<00:06:55.039> had<00:06:55.160> a 00:06:55.270 --> 00:06:55.280 align:start position:0% the GitHub pool requests so I had a 00:06:55.280 --> 00:06:58.350 align:start position:0% the GitHub pool requests so I had a question<00:06:55.560> about<00:06:55.840> that<00:06:56.759> um<00:06:57.759> do<00:06:57.840> you<00:06:58.000> have<00:06:58.120> any 00:06:58.350 --> 00:06:58.360 align:start position:0% question about that um do you have any 00:06:58.360 --> 00:07:00.670 align:start position:0% question about that um do you have any advice<00:06:59.120> in<00:06:59.280> term<00:06:59.599> terms<00:06:59.800> of<00:06:59.919> leading<00:07:00.240> the<00:07:00.360> team 00:07:00.670 --> 00:07:00.680 align:start position:0% advice in term terms of leading the team 00:07:00.680 --> 00:07:03.309 align:start position:0% advice in term terms of leading the team and<00:07:00.960> structuring<00:07:01.520> the<00:07:01.720> pr<00:07:02.160> reviews<00:07:03.160> uh 00:07:03.309 --> 00:07:03.319 align:start position:0% and structuring the pr reviews uh 00:07:03.319 --> 00:07:04.990 align:start position:0% and structuring the pr reviews uh because<00:07:03.479> in<00:07:03.599> my<00:07:03.720> opinion<00:07:04.120> when<00:07:04.520> there<00:07:04.639> is<00:07:04.759> an 00:07:04.990 --> 00:07:05.000 align:start position:0% because in my opinion when there is an 00:07:05.000 --> 00:07:06.749 align:start position:0% because in my opinion when there is an update<00:07:05.319> or<00:07:05.440> is<00:07:05.560> a<00:07:05.680> bug<00:07:05.879> fix<00:07:06.400> it's<00:07:06.599> quite 00:07:06.749 --> 00:07:06.759 align:start position:0% update or is a bug fix it's quite 00:07:06.759 --> 00:07:08.629 align:start position:0% update or is a bug fix it's quite straightforward<00:07:07.759> it<00:07:07.919> doesn't<00:07:08.199> really<00:07:08.360> matter 00:07:08.629 --> 00:07:08.639 align:start position:0% straightforward it doesn't really matter 00:07:08.639 --> 00:07:10.309 align:start position:0% straightforward it doesn't really matter the<00:07:08.759> number<00:07:08.960> of<00:07:09.080> commits<00:07:09.800> because<00:07:09.960> you<00:07:10.199> look 00:07:10.309 --> 00:07:10.319 align:start position:0% the number of commits because you look 00:07:10.319 --> 00:07:11.150 align:start position:0% the number of commits because you look at<00:07:10.440> the<00:07:10.520> change<00:07:10.759> you<00:07:10.879> look<00:07:11.000> at<00:07:11.080> the 00:07:11.150 --> 00:07:11.160 align:start position:0% at the change you look at the 00:07:11.160 --> 00:07:12.350 align:start position:0% at the change you look at the description<00:07:11.599> you<00:07:11.720> know<00:07:11.960> kind<00:07:12.080> of<00:07:12.199> what's 00:07:12.350 --> 00:07:12.360 align:start position:0% description you know kind of what's 00:07:12.360 --> 00:07:14.670 align:start position:0% description you know kind of what's happening<00:07:13.039> but<00:07:13.240> perhaps<00:07:13.919> uh<00:07:14.000> you<00:07:14.199> have<00:07:14.479> an 00:07:14.670 --> 00:07:14.680 align:start position:0% happening but perhaps uh you have an 00:07:14.680 --> 00:07:17.350 align:start position:0% happening but perhaps uh you have an advice<00:07:15.080> on<00:07:15.319> how<00:07:15.599> to<00:07:16.319> structure<00:07:16.759> the<00:07:16.879> commits 00:07:17.350 --> 00:07:17.360 align:start position:0% advice on how to structure the commits 00:07:17.360 --> 00:07:20.350 align:start position:0% advice on how to structure the commits when<00:07:17.479> it<00:07:17.639> comes<00:07:18.319> to<00:07:18.639> a<00:07:18.800> new<00:07:19.080> change<00:07:20.080> and<00:07:20.240> when 00:07:20.350 --> 00:07:20.360 align:start position:0% when it comes to a new change and when 00:07:20.360 --> 00:07:21.950 align:start position:0% when it comes to a new change and when you<00:07:20.440> said<00:07:20.639> about<00:07:20.879> like<00:07:21.000> the<00:07:21.120> me<00:07:21.520> like<00:07:21.759> it's 00:07:21.950 --> 00:07:21.960 align:start position:0% you said about like the me like it's 00:07:21.960 --> 00:07:25.309 align:start position:0% you said about like the me like it's hard<00:07:22.560> to<00:07:23.560> construct<00:07:24.080> the<00:07:24.280> intent<00:07:24.919> by<00:07:25.080> looking 00:07:25.309 --> 00:07:25.319 align:start position:0% hard to construct the intent by looking 00:07:25.319 --> 00:07:29.070 align:start position:0% hard to construct the intent by looking at<00:07:25.440> the<00:07:25.560> changes<00:07:26.199> so<00:07:26.759> perhaps<00:07:27.759> having<00:07:28.360> more 00:07:29.070 --> 00:07:29.080 align:start position:0% at the changes so perhaps having more 00:07:29.080 --> 00:07:30.550 align:start position:0% at the changes so perhaps having more commit 00:07:30.550 --> 00:07:30.560 align:start position:0% commit 00:07:30.560 --> 00:07:32.749 align:start position:0% commit and<00:07:30.960> uh<00:07:31.240> following<00:07:31.720> them<00:07:31.919> one<00:07:32.160> by<00:07:32.319> one<00:07:32.599> would 00:07:32.749 --> 00:07:32.759 align:start position:0% and uh following them one by one would 00:07:32.759 --> 00:07:34.270 align:start position:0% and uh following them one by one would help<00:07:33.000> with<00:07:33.199> that<00:07:33.440> or<00:07:33.759> you<00:07:33.879> know<00:07:34.039> what<00:07:34.120> I'm 00:07:34.270 --> 00:07:34.280 align:start position:0% help with that or you know what I'm 00:07:34.280 --> 00:07:36.749 align:start position:0% help with that or you know what I'm asking<00:07:34.840> perhaps<00:07:35.160> have<00:07:35.400> up<00:07:35.639> there<00:07:36.120> uh<00:07:36.360> I<00:07:36.440> mean 00:07:36.749 --> 00:07:36.759 align:start position:0% asking perhaps have up there uh I mean 00:07:36.759 --> 00:07:38.189 align:start position:0% asking perhaps have up there uh I mean it's<00:07:37.000> challenging<00:07:37.520> and<00:07:37.599> it's<00:07:37.759> challenging 00:07:38.189 --> 00:07:38.199 align:start position:0% it's challenging and it's challenging 00:07:38.199 --> 00:07:39.670 align:start position:0% it's challenging and it's challenging not<00:07:38.440> because<00:07:38.680> it's<00:07:38.800> a<00:07:38.960> non-s<00:07:39.240> solved<00:07:39.479> problem 00:07:39.670 --> 00:07:39.680 align:start position:0% not because it's a non-s solved problem 00:07:39.680 --> 00:07:40.710 align:start position:0% not because it's a non-s solved problem it's<00:07:39.800> challenging<00:07:40.199> because<00:07:40.400> people<00:07:40.599> just 00:07:40.710 --> 00:07:40.720 align:start position:0% it's challenging because people just 00:07:40.720 --> 00:07:43.430 align:start position:0% it's challenging because people just don't<00:07:40.919> do<00:07:41.080> it<00:07:41.360> right<00:07:41.560> but<00:07:41.840> uh<00:07:42.360> I<00:07:42.440> mean<00:07:43.280> have 00:07:43.430 --> 00:07:43.440 align:start position:0% don't do it right but uh I mean have 00:07:43.440 --> 00:07:45.589 align:start position:0% don't do it right but uh I mean have good<00:07:43.639> commit<00:07:43.960> hygiene<00:07:44.520> try<00:07:44.680> to<00:07:44.840> make<00:07:44.960> it<00:07:45.080> so<00:07:45.479> I 00:07:45.589 --> 00:07:45.599 align:start position:0% good commit hygiene try to make it so I 00:07:45.599 --> 00:07:47.469 align:start position:0% good commit hygiene try to make it so I try<00:07:45.720> to<00:07:45.800> make<00:07:45.919> it<00:07:46.039> so<00:07:46.240> every<00:07:46.440> commit<00:07:46.759> builds<00:07:47.319> if 00:07:47.469 --> 00:07:47.479 align:start position:0% try to make it so every commit builds if 00:07:47.479 --> 00:07:48.950 align:start position:0% try to make it so every commit builds if not<00:07:47.800> passing<00:07:48.159> tests<00:07:48.520> it<00:07:48.639> might<00:07:48.800> be<00:07:48.879> that 00:07:48.950 --> 00:07:48.960 align:start position:0% not passing tests it might be that 00:07:48.960 --> 00:07:50.029 align:start position:0% not passing tests it might be that you're<00:07:49.080> going<00:07:49.199> through<00:07:49.400> refactoring<00:07:49.919> and 00:07:50.029 --> 00:07:50.039 align:start position:0% you're going through refactoring and 00:07:50.039 --> 00:07:51.430 align:start position:0% you're going through refactoring and tests<00:07:50.319> have<00:07:50.400> to<00:07:50.479> be<00:07:50.599> failing<00:07:50.919> in<00:07:51.000> the<00:07:51.080> middle 00:07:51.430 --> 00:07:51.440 align:start position:0% tests have to be failing in the middle 00:07:51.440 --> 00:07:53.029 align:start position:0% tests have to be failing in the middle there<00:07:51.800> but<00:07:51.919> every<00:07:52.120> commit<00:07:52.400> should<00:07:52.560> build<00:07:52.960> in 00:07:53.029 --> 00:07:53.039 align:start position:0% there but every commit should build in 00:07:53.039 --> 00:07:54.950 align:start position:0% there but every commit should build in my<00:07:53.199> opinion<00:07:53.639> and<00:07:53.759> so<00:07:54.240> that<00:07:54.319> should<00:07:54.520> make<00:07:54.639> it<00:07:54.759> so 00:07:54.950 --> 00:07:54.960 align:start position:0% my opinion and so that should make it so 00:07:54.960 --> 00:07:57.869 align:start position:0% my opinion and so that should make it so every<00:07:55.159> commit<00:07:55.479> you<00:07:55.560> can<00:07:56.080> review<00:07:57.080> in<00:07:57.280> isolation 00:07:57.869 --> 00:07:57.879 align:start position:0% every commit you can review in isolation 00:07:57.879 --> 00:07:59.790 align:start position:0% every commit you can review in isolation if<00:07:58.039> that's<00:07:58.280> necessary<00:07:59.080> which<00:07:59.240> is<00:07:59.560> not<00:07:59.720> the 00:07:59.790 --> 00:07:59.800 align:start position:0% if that's necessary which is not the 00:07:59.800 --> 00:08:01.309 align:start position:0% if that's necessary which is not the ideal<00:08:00.080> way<00:08:00.199> to<00:08:00.319> do<00:08:00.400> it<00:08:00.560> because<00:08:00.800> that<00:08:01.039> takes<00:08:01.240> a 00:08:01.309 --> 00:08:01.319 align:start position:0% ideal way to do it because that takes a 00:08:01.319 --> 00:08:03.070 align:start position:0% ideal way to do it because that takes a little<00:08:01.479> longer<00:08:01.759> to<00:08:01.960> review<00:08:02.639> but<00:08:02.800> then<00:08:02.960> the 00:08:03.070 --> 00:08:03.080 align:start position:0% little longer to review but then the 00:08:03.080 --> 00:08:04.790 align:start position:0% little longer to review but then the second<00:08:03.360> piece<00:08:03.560> of<00:08:03.720> advice<00:08:04.039> I'd<00:08:04.199> give<00:08:04.319> on<00:08:04.520> that 00:08:04.790 --> 00:08:04.800 align:start position:0% second piece of advice I'd give on that 00:08:04.800 --> 00:08:07.909 align:start position:0% second piece of advice I'd give on that is<00:08:05.400> as<00:08:05.520> a<00:08:05.680> poll<00:08:05.919> request<00:08:06.479> reviewer<00:08:07.479> just<00:08:07.720> be 00:08:07.909 --> 00:08:07.919 align:start position:0% is as a poll request reviewer just be 00:08:07.919 --> 00:08:09.869 align:start position:0% is as a poll request reviewer just be really<00:08:08.240> picky<00:08:08.800> you<00:08:08.960> know<00:08:09.240> if<00:08:09.360> someone<00:08:09.599> sends 00:08:09.869 --> 00:08:09.879 align:start position:0% really picky you know if someone sends 00:08:09.879 --> 00:08:11.749 align:start position:0% really picky you know if someone sends you<00:08:10.000> a<00:08:10.080> poll<00:08:10.360> request<00:08:10.840> that<00:08:10.960> is<00:08:11.080> changing<00:08:11.440> four 00:08:11.749 --> 00:08:11.759 align:start position:0% you a poll request that is changing four 00:08:11.759 --> 00:08:13.430 align:start position:0% you a poll request that is changing four different<00:08:12.080> things<00:08:12.560> and<00:08:12.680> it's<00:08:12.840> hard<00:08:13.000> to<00:08:13.159> review 00:08:13.430 --> 00:08:13.440 align:start position:0% different things and it's hard to review 00:08:13.440 --> 00:08:14.589 align:start position:0% different things and it's hard to review the<00:08:13.560> whole<00:08:13.720> thing<00:08:13.840> and<00:08:14.000> keep<00:08:14.120> it<00:08:14.240> all<00:08:14.360> in<00:08:14.440> your 00:08:14.589 --> 00:08:14.599 align:start position:0% the whole thing and keep it all in your 00:08:14.599 --> 00:08:16.629 align:start position:0% the whole thing and keep it all in your head<00:08:15.120> don't<00:08:15.479> bother<00:08:15.720> reviewing<00:08:16.120> it<00:08:16.319> just<00:08:16.479> send 00:08:16.629 --> 00:08:16.639 align:start position:0% head don't bother reviewing it just send 00:08:16.639 --> 00:08:18.070 align:start position:0% head don't bother reviewing it just send it<00:08:16.800> back<00:08:16.919> to<00:08:17.039> them<00:08:17.159> and<00:08:17.240> said<00:08:17.520> hey<00:08:17.680> you<00:08:17.800> weren't 00:08:18.070 --> 00:08:18.080 align:start position:0% it back to them and said hey you weren't 00:08:18.080 --> 00:08:19.869 align:start position:0% it back to them and said hey you weren't respectful<00:08:18.479> of<00:08:18.639> my<00:08:18.800> time<00:08:19.319> break<00:08:19.599> this<00:08:19.720> into 00:08:19.869 --> 00:08:19.879 align:start position:0% respectful of my time break this into 00:08:19.879 --> 00:08:21.629 align:start position:0% respectful of my time break this into four<00:08:20.120> poll<00:08:20.400> requests<00:08:20.919> and<00:08:21.039> I'll<00:08:21.199> review<00:08:21.520> each 00:08:21.629 --> 00:08:21.639 align:start position:0% four poll requests and I'll review each 00:08:21.639 --> 00:08:23.869 align:start position:0% four poll requests and I'll review each one<00:08:21.879> independently<00:08:22.479> because<00:08:22.720> ideally<00:08:23.639> as<00:08:23.759> a 00:08:23.869 --> 00:08:23.879 align:start position:0% one independently because ideally as a 00:08:23.879 --> 00:08:26.390 align:start position:0% one independently because ideally as a poll<00:08:24.120> request<00:08:24.720> reviewer<00:08:25.720> it's<00:08:25.919> easy<00:08:26.159> for<00:08:26.319> you 00:08:26.390 --> 00:08:26.400 align:start position:0% poll request reviewer it's easy for you 00:08:26.400 --> 00:08:28.589 align:start position:0% poll request reviewer it's easy for you to<00:08:26.520> look<00:08:26.639> at<00:08:26.720> a<00:08:26.840> poll<00:08:27.080> request<00:08:27.440> and<00:08:27.639> say<00:08:28.479> this 00:08:28.589 --> 00:08:28.599 align:start position:0% to look at a poll request and say this 00:08:28.599 --> 00:08:30.430 align:start position:0% to look at a poll request and say this is<00:08:28.720> a<00:08:28.879> good<00:08:29.039> change<00:08:29.560> I'm<00:08:29.639> gonna<00:08:29.840> hit<00:08:30.000> approve 00:08:30.430 --> 00:08:30.440 align:start position:0% is a good change I'm gonna hit approve 00:08:30.440 --> 00:08:33.350 align:start position:0% is a good change I'm gonna hit approve and<00:08:30.599> move<00:08:30.800> on<00:08:31.280> right<00:08:31.520> but<00:08:31.680> if<00:08:32.039> if<00:08:32.560> the<00:08:33.000> if<00:08:33.120> you 00:08:33.350 --> 00:08:33.360 align:start position:0% and move on right but if if the if you 00:08:33.360 --> 00:08:35.469 align:start position:0% and move on right but if if the if you can't<00:08:33.640> do<00:08:33.919> that<00:08:34.519> and<00:08:34.640> you<00:08:34.800> have<00:08:34.919> to<00:08:35.080> now 00:08:35.469 --> 00:08:35.479 align:start position:0% can't do that and you have to now 00:08:35.479 --> 00:08:37.670 align:start position:0% can't do that and you have to now dissect<00:08:36.080> what<00:08:36.200> is<00:08:36.399> this<00:08:36.560> change<00:08:36.919> doing<00:08:37.519> you're 00:08:37.670 --> 00:08:37.680 align:start position:0% dissect what is this change doing you're 00:08:37.680 --> 00:08:39.269 align:start position:0% dissect what is this change doing you're not<00:08:37.839> the<00:08:38.000> expert<00:08:38.360> on<00:08:38.479> it<00:08:38.640> you<00:08:38.719> didn't<00:08:39.000> write 00:08:39.269 --> 00:08:39.279 align:start position:0% not the expert on it you didn't write 00:08:39.279 --> 00:08:40.909 align:start position:0% not the expert on it you didn't write that<00:08:39.440> code<00:08:39.880> it's<00:08:40.080> much<00:08:40.279> easier<00:08:40.640> for<00:08:40.800> the 00:08:40.909 --> 00:08:40.919 align:start position:0% that code it's much easier for the 00:08:40.919 --> 00:08:42.630 align:start position:0% that code it's much easier for the person<00:08:41.159> who<00:08:41.399> authored<00:08:41.760> the<00:08:41.880> PO<00:08:42.120> request<00:08:42.440> to<00:08:42.519> go 00:08:42.630 --> 00:08:42.640 align:start position:0% person who authored the PO request to go 00:08:42.640 --> 00:08:44.509 align:start position:0% person who authored the PO request to go and<00:08:42.800> split<00:08:43.120> that<00:08:43.320> up<00:08:43.880> into<00:08:44.159> multiple 00:08:44.509 --> 00:08:44.519 align:start position:0% and split that up into multiple 00:08:44.519 --> 00:08:45.949 align:start position:0% and split that up into multiple different<00:08:44.720> PO<00:08:44.959> requests<00:08:45.279> than<00:08:45.360> it<00:08:45.480> is<00:08:45.640> for<00:08:45.800> you 00:08:45.949 --> 00:08:45.959 align:start position:0% different PO requests than it is for you 00:08:45.959 --> 00:08:48.150 align:start position:0% different PO requests than it is for you to<00:08:46.160> dissect<00:08:46.600> what<00:08:46.720> they<00:08:46.880> meant<00:08:47.320> right<00:08:47.519> so 00:08:48.150 --> 00:08:48.160 align:start position:0% to dissect what they meant right so 00:08:48.160 --> 00:08:49.870 align:start position:0% to dissect what they meant right so don't<00:08:48.640> you<00:08:48.800> as<00:08:48.880> a<00:08:49.000> poll<00:08:49.160> request<00:08:49.440> reviewer 00:08:49.870 --> 00:08:49.880 align:start position:0% don't you as a poll request reviewer 00:08:49.880 --> 00:08:51.750 align:start position:0% don't you as a poll request reviewer don't<00:08:50.040> be<00:08:50.200> shy<00:08:50.600> just<00:08:50.720> be<00:08:50.839> like<00:08:51.080> look<00:08:51.440> be<00:08:51.560> more 00:08:51.750 --> 00:08:51.760 align:start position:0% don't be shy just be like look be more 00:08:51.760 --> 00:08:53.870 align:start position:0% don't be shy just be like look be more respectful<00:08:52.160> of<00:08:52.279> my<00:08:52.440> time<00:08:52.680> please<00:08:53.480> go<00:08:53.640> break 00:08:53.870 --> 00:08:53.880 align:start position:0% respectful of my time please go break 00:08:53.880 --> 00:08:55.430 align:start position:0% respectful of my time please go break this<00:08:54.040> up<00:08:54.200> into<00:08:54.399> multiple<00:08:54.720> PO<00:08:54.959> requests<00:08:55.279> so<00:08:55.360> I 00:08:55.430 --> 00:08:55.440 align:start position:0% this up into multiple PO requests so I 00:08:55.440 --> 00:08:57.750 align:start position:0% this up into multiple PO requests so I can<00:08:55.519> review<00:08:55.800> each<00:08:56.440> independently<00:08:57.440> that's<00:08:57.640> my 00:08:57.750 --> 00:08:57.760 align:start position:0% can review each independently that's my 00:08:57.760 --> 00:08:58.990 align:start position:0% can review each independently that's my opinion<00:08:58.040> on<00:08:58.120> it<00:08:58.320> all<00:08:58.399> right<00:08:58.600> thank<00:08:58.720> you<00:08:58.839> very 00:08:58.990 --> 00:08:59.000 align:start position:0% opinion on it all right thank you very 00:08:59.000 --> 00:09:00.310 align:start position:0% opinion on it all right thank you very much 00:09:00.310 --> 00:09:00.320 align:start position:0% much 00:09:00.320 --> 00:09:03.389 align:start position:0% much thanks<00:09:01.279> thanks<00:09:01.519> for<00:09:01.760> the<00:09:02.160> tips<00:09:02.480> for<00:09:03.000> PR 00:09:03.389 --> 00:09:03.399 align:start position:0% thanks thanks for the tips for PR 00:09:03.399 --> 00:09:07.079 align:start position:0% thanks thanks for the tips for PR reviews<00:09:04.040> I<00:09:04.160> think<00:09:04.360> we<00:09:04.480> can<00:09:04.600> all<00:09:04.839> Ben