WEBVTT Kind: captions Language: en 00:00:00.030 --> 00:00:02.300 align:start position:0% so<00:00:00.599> we<00:00:01.050> are<00:00:01.140> gonna<00:00:01.260> give<00:00:01.500> you<00:00:01.829> a<00:00:01.860> little<00:00:02.190> bit<00:00:02.280> of 00:00:02.300 --> 00:00:02.310 align:start position:0% so we are gonna give you a little bit of 00:00:02.310 --> 00:00:04.670 align:start position:0% so we are gonna give you a little bit of an<00:00:02.460> overview<00:00:02.700> of<00:00:02.909> what<00:00:03.629> good<00:00:03.780> projects<00:00:04.290> do<00:00:04.500> in 00:00:04.670 --> 00:00:04.680 align:start position:0% an overview of what good projects do in 00:00:04.680 --> 00:00:06.320 align:start position:0% an overview of what good projects do in the<00:00:04.770> space<00:00:05.009> in<00:00:05.190> order<00:00:05.310> to<00:00:05.520> plan<00:00:05.970> and<00:00:06.240> ensure 00:00:06.320 --> 00:00:06.330 align:start position:0% the space in order to plan and ensure 00:00:06.330 --> 00:00:10.700 align:start position:0% the space in order to plan and ensure their<00:00:06.660> success<00:00:06.899> their<00:00:07.589> success<00:00:09.139> so<00:00:10.139> let's 00:00:10.700 --> 00:00:10.710 align:start position:0% their success their success so let's 00:00:10.710 --> 00:00:12.230 align:start position:0% their success their success so let's address<00:00:10.920> the<00:00:11.130> elf<00:00:11.280> in<00:00:11.429> the<00:00:11.519> room<00:00:11.730> everyone 00:00:12.230 --> 00:00:12.240 align:start position:0% address the elf in the room everyone 00:00:12.240 --> 00:00:14.390 align:start position:0% address the elf in the room everyone says<00:00:12.450> smart<00:00:12.719> contracts<00:00:13.080> are<00:00:13.230> insecure<00:00:13.530> there 00:00:14.390 --> 00:00:14.400 align:start position:0% says smart contracts are insecure there 00:00:14.400 --> 00:00:15.740 align:start position:0% says smart contracts are insecure there doesn't<00:00:14.670> seem<00:00:14.730> to<00:00:14.880> be<00:00:14.969> anything<00:00:15.210> changing 00:00:15.740 --> 00:00:15.750 align:start position:0% doesn't seem to be anything changing 00:00:15.750 --> 00:00:17.840 align:start position:0% doesn't seem to be anything changing about<00:00:15.960> it<00:00:16.139> like<00:00:16.379> like<00:00:16.740> what<00:00:16.920> can<00:00:17.010> be<00:00:17.130> done<00:00:17.340> is 00:00:17.840 --> 00:00:17.850 align:start position:0% about it like like what can be done is 00:00:17.850 --> 00:00:19.160 align:start position:0% about it like like what can be done is it<00:00:18.090> just<00:00:18.270> something<00:00:18.420> we<00:00:18.570> have<00:00:18.600> to<00:00:18.810> live<00:00:18.990> with 00:00:19.160 --> 00:00:19.170 align:start position:0% it just something we have to live with 00:00:19.170 --> 00:00:23.269 align:start position:0% it just something we have to live with or<00:00:19.380> is<00:00:19.529> it<00:00:19.680> something<00:00:20.010> that<00:00:20.060> can<00:00:21.060> be<00:00:21.240> fixed<00:00:22.279> so 00:00:23.269 --> 00:00:23.279 align:start position:0% or is it something that can be fixed so 00:00:23.279 --> 00:00:25.820 align:start position:0% or is it something that can be fixed so I<00:00:23.760> think<00:00:24.359> it<00:00:24.660> is<00:00:24.689> possible<00:00:25.140> the<00:00:25.260> design<00:00:25.470> robust 00:00:25.820 --> 00:00:25.830 align:start position:0% I think it is possible the design robust 00:00:25.830 --> 00:00:27.560 align:start position:0% I think it is possible the design robust and<00:00:26.010> secure<00:00:26.160> software<00:00:26.609> and<00:00:27.090> I<00:00:27.180> think<00:00:27.420> that 00:00:27.560 --> 00:00:27.570 align:start position:0% and secure software and I think that 00:00:27.570 --> 00:00:29.359 align:start position:0% and secure software and I think that this<00:00:27.810> comic<00:00:28.230> actually<00:00:28.619> points<00:00:28.890> it<00:00:28.949> out<00:00:29.070> a 00:00:29.359 --> 00:00:29.369 align:start position:0% this comic actually points it out a 00:00:29.369 --> 00:00:32.060 align:start position:0% this comic actually points it out a little<00:00:29.670> bit<00:00:29.880> unintentionally<00:00:30.619> so<00:00:31.619> we<00:00:31.800> built 00:00:32.060 --> 00:00:32.070 align:start position:0% little bit unintentionally so we built 00:00:32.070 --> 00:00:34.690 align:start position:0% little bit unintentionally so we built we<00:00:32.340> trust<00:00:32.910> machines<00:00:33.300> we<00:00:33.899> trust<00:00:34.170> airplanes 00:00:34.690 --> 00:00:34.700 align:start position:0% we trust machines we trust airplanes 00:00:34.700 --> 00:00:36.860 align:start position:0% we trust machines we trust airplanes elevators<00:00:35.700> all<00:00:35.910> sorts<00:00:36.180> of<00:00:36.239> machines<00:00:36.390> that<00:00:36.690> are 00:00:36.860 --> 00:00:36.870 align:start position:0% elevators all sorts of machines that are 00:00:36.870 --> 00:00:39.680 align:start position:0% elevators all sorts of machines that are actually<00:00:37.170> run<00:00:37.670> by<00:00:38.670> software<00:00:39.120> the<00:00:39.360> safety 00:00:39.680 --> 00:00:39.690 align:start position:0% actually run by software the safety 00:00:39.690 --> 00:00:42.860 align:start position:0% actually run by software the safety critical<00:00:39.809> parts<00:00:40.320> are<00:00:40.469> run<00:00:40.649> by<00:00:40.680> software<00:00:41.870> every 00:00:42.860 --> 00:00:42.870 align:start position:0% critical parts are run by software every 00:00:42.870 --> 00:00:45.049 align:start position:0% critical parts are run by software every day<00:00:43.050> and<00:00:43.410> those<00:00:44.160> those<00:00:44.460> machines<00:00:44.910> are 00:00:45.049 --> 00:00:45.059 align:start position:0% day and those those machines are 00:00:45.059 --> 00:00:47.810 align:start position:0% day and those those machines are designed<00:00:45.180> such<00:00:45.690> that<00:00:46.100> there's<00:00:47.100> there's<00:00:47.430> very 00:00:47.810 --> 00:00:47.820 align:start position:0% designed such that there's there's very 00:00:47.820 --> 00:00:49.310 align:start position:0% designed such that there's there's very little<00:00:48.030> things<00:00:48.480> that<00:00:48.570> go<00:00:48.780> wrong<00:00:48.809> that<00:00:49.230> you 00:00:49.310 --> 00:00:49.320 align:start position:0% little things that go wrong that you 00:00:49.320 --> 00:00:50.450 align:start position:0% little things that go wrong that you hear<00:00:49.500> about<00:00:49.530> I<00:00:49.739> mean<00:00:49.950> you<00:00:50.039> might<00:00:50.219> hear<00:00:50.430> about 00:00:50.450 --> 00:00:50.460 align:start position:0% hear about I mean you might hear about 00:00:50.460 --> 00:00:52.819 align:start position:0% hear about I mean you might hear about an<00:00:50.730> airplane<00:00:51.059> crash<00:00:51.300> once<00:00:51.600> a<00:00:51.719> year<00:00:51.989> you 00:00:52.819 --> 00:00:52.829 align:start position:0% an airplane crash once a year you 00:00:52.829 --> 00:00:54.680 align:start position:0% an airplane crash once a year you imagine<00:00:53.160> them<00:00:53.250> out<00:00:53.399> of<00:00:53.550> time<00:00:54.090> that<00:00:54.329> airplanes 00:00:54.680 --> 00:00:54.690 align:start position:0% imagine them out of time that airplanes 00:00:54.690 --> 00:00:56.060 align:start position:0% imagine them out of time that airplanes actually<00:00:54.870> fly<00:00:55.260> around<00:00:55.320> the<00:00:55.620> globe<00:00:55.829> that's 00:00:56.060 --> 00:00:56.070 align:start position:0% actually fly around the globe that's 00:00:56.070 --> 00:00:58.790 align:start position:0% actually fly around the globe that's pretty<00:00:56.520> amazing<00:00:57.350> so<00:00:58.350> we<00:00:58.440> have<00:00:58.559> to<00:00:58.680> ask 00:00:58.790 --> 00:00:58.800 align:start position:0% pretty amazing so we have to ask 00:00:58.800 --> 00:01:01.040 align:start position:0% pretty amazing so we have to ask ourselves<00:00:58.980> like<00:00:59.370> how<00:00:59.579> how<00:01:00.510> do<00:01:00.570> we<00:01:00.719> get<00:01:00.899> that 00:01:01.040 --> 00:01:01.050 align:start position:0% ourselves like how how do we get that 00:01:01.050 --> 00:01:03.219 align:start position:0% ourselves like how how do we get that kind<00:01:01.230> of<00:01:01.350> security<00:01:01.800> into<00:01:02.010> our<00:01:02.190> applications 00:01:03.219 --> 00:01:03.229 align:start position:0% kind of security into our applications 00:01:03.229 --> 00:01:08.780 align:start position:0% kind of security into our applications no<00:01:04.229> I<00:01:04.260> just<00:01:04.379> want<00:01:04.680> to<00:01:04.769> go<00:01:05.460> down<00:01:05.640> on<00:01:05.790> this<00:01:06.830> nope<00:01:07.830> I 00:01:08.780 --> 00:01:08.790 align:start position:0% no I just want to go down on this nope I 00:01:08.790 --> 00:01:11.469 align:start position:0% no I just want to go down on this nope I [Music] 00:01:11.469 --> 00:01:11.479 align:start position:0% [Music] 00:01:11.479 --> 00:01:16.310 align:start position:0% [Music] have<00:01:12.479> to<00:01:12.570> do<00:01:12.689> it<00:01:12.780> manually<00:01:14.869> yeah<00:01:15.869> so<00:01:16.080> we<00:01:16.200> have 00:01:16.310 --> 00:01:16.320 align:start position:0% have to do it manually yeah so we have 00:01:16.320 --> 00:01:19.039 align:start position:0% have to do it manually yeah so we have to<00:01:16.439> we<00:01:16.740> have<00:01:17.520> to<00:01:17.820> learn<00:01:17.970> like<00:01:18.330> more<00:01:18.720> from<00:01:18.930> these 00:01:19.039 --> 00:01:19.049 align:start position:0% to we have to learn like more from these 00:01:19.049 --> 00:01:22.270 align:start position:0% to we have to learn like more from these industries<00:01:19.500> how<00:01:19.680> they<00:01:20.189> make<00:01:20.340> things<00:01:20.580> so<00:01:20.880> good 00:01:22.270 --> 00:01:22.280 align:start position:0% industries how they make things so good 00:01:22.280 --> 00:01:26.480 align:start position:0% industries how they make things so good so<00:01:23.780> most<00:01:24.780> of<00:01:24.900> what<00:01:25.020> I<00:01:25.049> what<00:01:25.920> I'd<00:01:26.009> like<00:01:26.189> to<00:01:26.340> talk 00:01:26.480 --> 00:01:26.490 align:start position:0% so most of what I what I'd like to talk 00:01:26.490 --> 00:01:28.310 align:start position:0% so most of what I what I'd like to talk about<00:01:26.610> is<00:01:26.820> just<00:01:26.850> how<00:01:27.060> not<00:01:27.780> to<00:01:27.900> take<00:01:28.049> shortcuts 00:01:28.310 --> 00:01:28.320 align:start position:0% about is just how not to take shortcuts 00:01:28.320 --> 00:01:30.730 align:start position:0% about is just how not to take shortcuts how<00:01:28.650> to<00:01:28.710> plan<00:01:28.950> ahead<00:01:29.070> how<00:01:29.520> to<00:01:29.579> make<00:01:29.939> sure<00:01:30.090> that 00:01:30.730 --> 00:01:30.740 align:start position:0% how to plan ahead how to make sure that 00:01:30.740 --> 00:01:34.850 align:start position:0% how to plan ahead how to make sure that you<00:01:31.740> you<00:01:32.040> have<00:01:32.250> everything<00:01:33.439> all<00:01:34.439> your<00:01:34.619> ducks 00:01:34.850 --> 00:01:34.860 align:start position:0% you you have everything all your ducks 00:01:34.860 --> 00:01:38.899 align:start position:0% you you have everything all your ducks in<00:01:34.979> a<00:01:35.040> row<00:01:35.479> so<00:01:36.650> so<00:01:37.650> the<00:01:37.799> secret<00:01:38.130> is<00:01:38.250> is<00:01:38.520> that<00:01:38.729> the 00:01:38.899 --> 00:01:38.909 align:start position:0% in a row so so the secret is is that the 00:01:38.909 --> 00:01:40.520 align:start position:0% in a row so so the secret is is that the weakest<00:01:39.210> link<00:01:39.450> and<00:01:39.630> designing<00:01:40.020> software<00:01:40.470> is 00:01:40.520 --> 00:01:40.530 align:start position:0% weakest link and designing software is 00:01:40.530 --> 00:01:43.429 align:start position:0% weakest link and designing software is actually<00:01:40.680> humans<00:01:41.579> it's<00:01:42.090> all<00:01:42.240> of<00:01:42.329> you<00:01:42.450> guys<00:01:42.600> so 00:01:43.429 --> 00:01:43.439 align:start position:0% actually humans it's all of you guys so 00:01:43.439 --> 00:01:44.480 align:start position:0% actually humans it's all of you guys so you<00:01:43.500> have<00:01:43.680> to<00:01:43.799> figure<00:01:44.040> out<00:01:44.070> how<00:01:44.250> to<00:01:44.310> make 00:01:44.480 --> 00:01:44.490 align:start position:0% you have to figure out how to make 00:01:44.490 --> 00:01:49.179 align:start position:0% you have to figure out how to make yourselves<00:01:45.740> mitigate<00:01:46.740> against<00:01:47.100> any<00:01:47.310> risks<00:01:47.670> so 00:01:49.179 --> 00:01:49.189 align:start position:0% yourselves mitigate against any risks so 00:01:49.189 --> 00:01:51.889 align:start position:0% yourselves mitigate against any risks so the<00:01:50.189> only<00:01:50.340> the<00:01:50.700> best<00:01:50.880> way<00:01:51.030> to<00:01:51.060> do<00:01:51.299> that<00:01:51.450> is<00:01:51.659> by 00:01:51.889 --> 00:01:51.899 align:start position:0% the only the best way to do that is by 00:01:51.899 --> 00:01:54.080 align:start position:0% the only the best way to do that is by having<00:01:52.049> lots<00:01:52.920> of<00:01:53.040> layers<00:01:53.280> of<00:01:53.549> testing<00:01:53.909> not 00:01:54.080 --> 00:01:54.090 align:start position:0% having lots of layers of testing not 00:01:54.090 --> 00:01:56.899 align:start position:0% having lots of layers of testing not just<00:01:54.299> single<00:01:54.630> types<00:01:54.869> of<00:01:55.020> testing<00:01:55.549> have<00:01:56.549> really 00:01:56.899 --> 00:01:56.909 align:start position:0% just single types of testing have really 00:01:56.909 --> 00:01:58.550 align:start position:0% just single types of testing have really good<00:01:57.060> documentation<00:01:57.390> so<00:01:57.930> other<00:01:58.110> people<00:01:58.170> can 00:01:58.550 --> 00:01:58.560 align:start position:0% good documentation so other people can 00:01:58.560 --> 00:02:00.370 align:start position:0% good documentation so other people can understand<00:01:59.009> what<00:01:59.250> you're<00:01:59.340> trying<00:01:59.520> to<00:01:59.729> do<00:01:59.909> and 00:02:00.370 --> 00:02:00.380 align:start position:0% understand what you're trying to do and 00:02:00.380 --> 00:02:02.959 align:start position:0% understand what you're trying to do and get<00:02:01.380> multiple<00:02:01.680> people<00:02:01.979> to<00:02:02.070> review<00:02:02.369> your<00:02:02.490> code 00:02:02.959 --> 00:02:02.969 align:start position:0% get multiple people to review your code 00:02:02.969 --> 00:02:05.630 align:start position:0% get multiple people to review your code tests<00:02:03.420> and<00:02:03.570> assumptions<00:02:04.049> and<00:02:04.350> a<00:02:05.280> regular 00:02:05.630 --> 00:02:05.640 align:start position:0% tests and assumptions and a regular 00:02:05.640 --> 00:02:10.100 align:start position:0% tests and assumptions and a regular basis<00:02:06.060> not<00:02:06.360> just<00:02:06.630> during<00:02:06.869> an<00:02:07.049> audit<00:02:09.110> so 00:02:10.100 --> 00:02:10.110 align:start position:0% basis not just during an audit so 00:02:10.110 --> 00:02:11.690 align:start position:0% basis not just during an audit so testing<00:02:10.679> is<00:02:10.770> the<00:02:10.860> only<00:02:10.890> true<00:02:11.220> way<00:02:11.340> to<00:02:11.370> actually 00:02:11.690 --> 00:02:11.700 align:start position:0% testing is the only true way to actually 00:02:11.700 --> 00:02:12.920 align:start position:0% testing is the only true way to actually detect<00:02:12.180> inker 00:02:12.920 --> 00:02:12.930 align:start position:0% detect inker 00:02:12.930 --> 00:02:16.849 align:start position:0% detect inker behavior<00:02:13.409> in<00:02:13.590> software<00:02:14.159> I<00:02:15.680> think<00:02:16.680> a<00:02:16.739> good 00:02:16.849 --> 00:02:16.859 align:start position:0% behavior in software I think a good 00:02:16.859 --> 00:02:19.160 align:start position:0% behavior in software I think a good quote<00:02:17.069> is<00:02:17.219> that<00:02:17.400> like<00:02:17.579> you<00:02:17.700> know<00:02:17.819> software<00:02:18.719> - 00:02:19.160 --> 00:02:19.170 align:start position:0% quote is that like you know software - 00:02:19.170 --> 00:02:21.349 align:start position:0% quote is that like you know software - test<00:02:19.439> is<00:02:19.680> just<00:02:19.950> paperwork<00:02:20.310> basically<00:02:21.120> at<00:02:21.239> the 00:02:21.349 --> 00:02:21.359 align:start position:0% test is just paperwork basically at the 00:02:21.359 --> 00:02:24.860 align:start position:0% test is just paperwork basically at the end<00:02:21.480> of<00:02:21.569> day<00:02:22.549> so<00:02:23.549> multiple<00:02:24.060> layers<00:02:24.269> of<00:02:24.359> testing 00:02:24.860 --> 00:02:24.870 align:start position:0% end of day so multiple layers of testing 00:02:24.870 --> 00:02:26.809 align:start position:0% end of day so multiple layers of testing ensure<00:02:25.200> that<00:02:25.469> you<00:02:26.010> don't<00:02:26.099> have<00:02:26.250> any<00:02:26.400> single 00:02:26.809 --> 00:02:26.819 align:start position:0% ensure that you don't have any single 00:02:26.819 --> 00:02:28.459 align:start position:0% ensure that you don't have any single one<00:02:26.939> critical<00:02:27.450> vulnerability<00:02:27.989> that<00:02:28.140> goes<00:02:28.319> all 00:02:28.459 --> 00:02:28.469 align:start position:0% one critical vulnerability that goes all 00:02:28.469 --> 00:02:29.660 align:start position:0% one critical vulnerability that goes all the<00:02:28.500> way<00:02:28.560> through<00:02:28.620> and<00:02:29.010> I<00:02:29.040> like<00:02:29.189> to<00:02:29.280> illustrate 00:02:29.660 --> 00:02:29.670 align:start position:0% the way through and I like to illustrate 00:02:29.670 --> 00:02:32.629 align:start position:0% the way through and I like to illustrate that<00:02:29.730> with<00:02:30.079> blocka<00:02:31.079> Swiss<00:02:31.349> cheese<00:02:31.650> so<00:02:32.010> the 00:02:32.629 --> 00:02:32.639 align:start position:0% that with blocka Swiss cheese so the 00:02:32.639 --> 00:02:34.459 align:start position:0% that with blocka Swiss cheese so the bigger<00:02:32.819> the<00:02:32.909> box<00:02:33.180> Swiss<00:02:33.420> cheese<00:02:33.629> you<00:02:33.750> have<00:02:33.810> the 00:02:34.459 --> 00:02:34.469 align:start position:0% bigger the box Swiss cheese you have the 00:02:34.469 --> 00:02:35.869 align:start position:0% bigger the box Swiss cheese you have the less<00:02:34.680> likely<00:02:34.709> you<00:02:35.159> have<00:02:35.310> that<00:02:35.639> a<00:02:35.670> little 00:02:35.869 --> 00:02:35.879 align:start position:0% less likely you have that a little 00:02:35.879 --> 00:02:37.819 align:start position:0% less likely you have that a little bubble<00:02:36.750> ends<00:02:36.930> up<00:02:37.049> making<00:02:37.260> its<00:02:37.500> way<00:02:37.620> all<00:02:37.799> the 00:02:37.819 --> 00:02:37.829 align:start position:0% bubble ends up making its way all the 00:02:37.829 --> 00:02:40.039 align:start position:0% bubble ends up making its way all the way<00:02:37.950> through<00:02:38.040> so<00:02:39.000> if<00:02:39.120> you<00:02:39.150> have<00:02:39.329> a<00:02:39.359> big<00:02:39.569> big 00:02:40.039 --> 00:02:40.049 align:start position:0% way through so if you have a big big 00:02:40.049 --> 00:02:42.589 align:start position:0% way through so if you have a big big huge<00:02:40.680> chunk<00:02:40.950> of<00:02:41.010> Swiss<00:02:41.219> cheese<00:02:41.430> you<00:02:42.180> can<00:02:42.359> you 00:02:42.589 --> 00:02:42.599 align:start position:0% huge chunk of Swiss cheese you can you 00:02:42.599 --> 00:02:44.000 align:start position:0% huge chunk of Swiss cheese you can you can<00:02:42.780> never<00:02:43.019> see<00:02:43.319> through<00:02:43.560> it<00:02:43.650> but<00:02:43.680> if<00:02:43.829> you<00:02:43.920> have 00:02:44.000 --> 00:02:44.010 align:start position:0% can never see through it but if you have 00:02:44.010 --> 00:02:46.580 align:start position:0% can never see through it but if you have one<00:02:44.250> thin<00:02:44.459> slice<00:02:45.169> representing<00:02:46.169> one<00:02:46.290> layer<00:02:46.439> of 00:02:46.580 --> 00:02:46.590 align:start position:0% one thin slice representing one layer of 00:02:46.590 --> 00:02:48.229 align:start position:0% one thin slice representing one layer of testing<00:02:47.010> or<00:02:47.129> just<00:02:47.310> one<00:02:47.459> person<00:02:47.489> writing<00:02:48.120> the 00:02:48.229 --> 00:02:48.239 align:start position:0% testing or just one person writing the 00:02:48.239 --> 00:02:50.390 align:start position:0% testing or just one person writing the thing<00:02:48.419> you're<00:02:49.349> very<00:02:49.530> likely<00:02:49.739> to<00:02:49.889> have<00:02:50.069> lots<00:02:50.280> of 00:02:50.390 --> 00:02:50.400 align:start position:0% thing you're very likely to have lots of 00:02:50.400 --> 00:02:57.319 align:start position:0% thing you're very likely to have lots of holes<00:02:50.609> so<00:02:54.859> documentation<00:02:55.859> testing<00:02:56.310> all<00:02:56.909> helps 00:02:57.319 --> 00:02:57.329 align:start position:0% holes so documentation testing all helps 00:02:57.329 --> 00:02:59.809 align:start position:0% holes so documentation testing all helps help<00:02:57.900> you<00:02:58.019> get<00:02:58.139> through<00:02:58.290> that<00:02:58.379> and<00:02:58.819> again 00:02:59.809 --> 00:02:59.819 align:start position:0% help you get through that and again 00:02:59.819 --> 00:03:01.759 align:start position:0% help you get through that and again hitting<00:03:00.359> on<00:03:00.540> security<00:03:01.260> audits<00:03:01.530> a<00:03:01.590> lot<00:03:01.680> of 00:03:01.759 --> 00:03:01.769 align:start position:0% hitting on security audits a lot of 00:03:01.769 --> 00:03:03.830 align:start position:0% hitting on security audits a lot of people<00:03:01.950> like<00:03:02.099> to<00:03:02.129> say<00:03:02.609> security<00:03:03.299> audits<00:03:03.719> with 00:03:03.830 --> 00:03:03.840 align:start position:0% people like to say security audits with 00:03:03.840 --> 00:03:05.479 align:start position:0% people like to say security audits with gold<00:03:04.049> standard<00:03:04.379> for<00:03:04.409> security<00:03:04.829> and<00:03:04.919> in<00:03:05.010> space 00:03:05.479 --> 00:03:05.489 align:start position:0% gold standard for security and in space 00:03:05.489 --> 00:03:07.220 align:start position:0% gold standard for security and in space and<00:03:05.969> that's<00:03:06.120> just<00:03:06.299> plain<00:03:06.450> wrong<00:03:06.629> you<00:03:06.930> have<00:03:07.079> to 00:03:07.220 --> 00:03:07.230 align:start position:0% and that's just plain wrong you have to 00:03:07.230 --> 00:03:09.649 align:start position:0% and that's just plain wrong you have to have<00:03:07.799> a<00:03:07.829> lot<00:03:08.189> done<00:03:08.790> before<00:03:09.239> you<00:03:09.299> get<00:03:09.419> to<00:03:09.540> that 00:03:09.649 --> 00:03:09.659 align:start position:0% have a lot done before you get to that 00:03:09.659 --> 00:03:10.970 align:start position:0% have a lot done before you get to that point<00:03:09.870> or<00:03:10.319> else<00:03:10.439> you're<00:03:10.530> never<00:03:10.709> going<00:03:10.829> to<00:03:10.859> be 00:03:10.970 --> 00:03:10.980 align:start position:0% point or else you're never going to be 00:03:10.980 --> 00:03:12.800 align:start position:0% point or else you're never going to be successful<00:03:11.129> that<00:03:11.609> process<00:03:12.090> you're<00:03:12.689> gonna 00:03:12.800 --> 00:03:12.810 align:start position:0% successful that process you're gonna 00:03:12.810 --> 00:03:15.500 align:start position:0% successful that process you're gonna have<00:03:12.959> a<00:03:12.989> lot<00:03:13.200> of<00:03:13.939> you're<00:03:14.939> gonna<00:03:15.030> have<00:03:15.239> a<00:03:15.269> lot<00:03:15.480> of 00:03:15.500 --> 00:03:15.510 align:start position:0% have a lot of you're gonna have a lot of 00:03:15.510 --> 00:03:17.420 align:start position:0% have a lot of you're gonna have a lot of outcomes<00:03:16.469> from<00:03:16.799> the<00:03:16.949> audit<00:03:17.190> you're<00:03:17.310> gonna 00:03:17.420 --> 00:03:17.430 align:start position:0% outcomes from the audit you're gonna 00:03:17.430 --> 00:03:19.189 align:start position:0% outcomes from the audit you're gonna have<00:03:17.579> to<00:03:17.669> do<00:03:17.819> a<00:03:17.849> lot<00:03:18.090> to<00:03:18.269> fix<00:03:18.540> all<00:03:18.780> the<00:03:18.900> outcomes 00:03:19.189 --> 00:03:19.199 align:start position:0% have to do a lot to fix all the outcomes 00:03:19.199 --> 00:03:22.039 align:start position:0% have to do a lot to fix all the outcomes that<00:03:19.409> the<00:03:19.530> auditors<00:03:19.859> brought<00:03:20.069> up<00:03:20.220> and<00:03:21.049> since 00:03:22.039 --> 00:03:22.049 align:start position:0% that the auditors brought up and since 00:03:22.049 --> 00:03:23.240 align:start position:0% that the auditors brought up and since you<00:03:22.109> guys<00:03:22.229> are<00:03:22.379> innovating<00:03:22.769> in<00:03:22.829> the<00:03:22.859> space<00:03:23.099> so 00:03:23.240 --> 00:03:23.250 align:start position:0% you guys are innovating in the space so 00:03:23.250 --> 00:03:25.129 align:start position:0% you guys are innovating in the space so often<00:03:23.760> you're<00:03:24.299> going<00:03:24.389> to<00:03:24.540> have<00:03:24.629> to<00:03:24.750> redo<00:03:25.019> this 00:03:25.129 --> 00:03:25.139 align:start position:0% often you're going to have to redo this 00:03:25.139 --> 00:03:26.719 align:start position:0% often you're going to have to redo this audit<00:03:25.440> over<00:03:25.620> and<00:03:25.739> over<00:03:25.889> again<00:03:25.979> pay<00:03:26.459> a<00:03:26.489> lot<00:03:26.699> of 00:03:26.719 --> 00:03:26.729 align:start position:0% audit over and over again pay a lot of 00:03:26.729 --> 00:03:28.939 align:start position:0% audit over and over again pay a lot of money<00:03:26.879> to<00:03:27.269> get<00:03:27.389> that<00:03:27.540> into<00:03:27.870> there<00:03:28.019> it's<00:03:28.799> way 00:03:28.939 --> 00:03:28.949 align:start position:0% money to get that into there it's way 00:03:28.949 --> 00:03:30.289 align:start position:0% money to get that into there it's way more<00:03:28.979> cost-effective<00:03:29.760> for<00:03:29.849> you<00:03:30.000> to<00:03:30.120> build 00:03:30.289 --> 00:03:30.299 align:start position:0% more cost-effective for you to build 00:03:30.299 --> 00:03:33.110 align:start position:0% more cost-effective for you to build into<00:03:30.810> in<00:03:31.019> this<00:03:31.319> process<00:03:31.829> into<00:03:32.639> how<00:03:32.790> you<00:03:32.849> guys 00:03:33.110 --> 00:03:33.120 align:start position:0% into in this process into how you guys 00:03:33.120 --> 00:03:34.960 align:start position:0% into in this process into how you guys approach<00:03:33.510> smart<00:03:33.780> contract<00:03:34.169> development<00:03:34.620> and 00:03:34.960 --> 00:03:34.970 align:start position:0% approach smart contract development and 00:03:34.970 --> 00:03:38.270 align:start position:0% approach smart contract development and and<00:03:35.970> you<00:03:36.329> you<00:03:36.599> make<00:03:36.780> security<00:03:37.409> auditing<00:03:37.799> one 00:03:38.270 --> 00:03:38.280 align:start position:0% and you you make security auditing one 00:03:38.280 --> 00:03:40.159 align:start position:0% and you you make security auditing one small<00:03:38.549> part<00:03:38.819> of<00:03:39.030> how<00:03:39.150> you<00:03:39.180> ensure<00:03:39.449> the<00:03:39.720> overall 00:03:40.159 --> 00:03:40.169 align:start position:0% small part of how you ensure the overall 00:03:40.169 --> 00:03:46.460 align:start position:0% small part of how you ensure the overall development<00:03:40.439> process<00:03:41.010> is<00:03:41.189> secure<00:03:43.970> so<00:03:44.970> I<00:03:45.470> from 00:03:46.460 --> 00:03:46.470 align:start position:0% development process is secure so I from 00:03:46.470 --> 00:03:47.960 align:start position:0% development process is secure so I from aerospace<00:03:46.769> we<00:03:47.099> kind<00:03:47.549> of<00:03:47.609> had<00:03:47.699> this<00:03:47.819> like 00:03:47.960 --> 00:03:47.970 align:start position:0% aerospace we kind of had this like 00:03:47.970 --> 00:03:50.390 align:start position:0% aerospace we kind of had this like ancient<00:03:48.239> view<00:03:48.659> of<00:03:48.959> how<00:03:49.560> things<00:03:49.799> get<00:03:49.949> done<00:03:50.220> and 00:03:50.390 --> 00:03:50.400 align:start position:0% ancient view of how things get done and 00:03:50.400 --> 00:03:52.759 align:start position:0% ancient view of how things get done and we<00:03:50.489> used<00:03:50.849> to<00:03:50.939> use<00:03:51.090> this<00:03:51.269> be<00:03:51.479> model<00:03:51.900> of<00:03:52.319> software 00:03:52.759 --> 00:03:52.769 align:start position:0% we used to use this be model of software 00:03:52.769 --> 00:03:54.170 align:start position:0% we used to use this be model of software development<00:03:53.040> it's<00:03:53.220> like<00:03:53.310> way<00:03:53.459> before<00:03:53.639> agile 00:03:54.170 --> 00:03:54.180 align:start position:0% development it's like way before agile 00:03:54.180 --> 00:03:55.280 align:start position:0% development it's like way before agile and<00:03:54.299> waterfall<00:03:54.359> and<00:03:54.810> all<00:03:54.930> these<00:03:55.049> other 00:03:55.280 --> 00:03:55.290 align:start position:0% and waterfall and all these other 00:03:55.290 --> 00:03:58.309 align:start position:0% and waterfall and all these other buzzwords<00:03:56.419> but<00:03:57.419> I<00:03:57.449> actually<00:03:57.629> kind<00:03:57.810> of<00:03:57.959> like<00:03:58.139> it 00:03:58.309 --> 00:03:58.319 align:start position:0% buzzwords but I actually kind of like it 00:03:58.319 --> 00:03:59.259 align:start position:0% buzzwords but I actually kind of like it because<00:03:58.379> it<00:03:58.590> has<00:03:58.709> this<00:03:58.859> neat<00:03:59.069> little 00:03:59.259 --> 00:03:59.269 align:start position:0% because it has this neat little 00:03:59.269 --> 00:04:02.089 align:start position:0% because it has this neat little iterative<00:04:00.269> process<00:04:00.780> as<00:04:00.989> you<00:04:01.319> go<00:04:01.470> kind<00:04:01.979> of 00:04:02.089 --> 00:04:02.099 align:start position:0% iterative process as you go kind of 00:04:02.099 --> 00:04:05.030 align:start position:0% iterative process as you go kind of moving<00:04:02.970> forward<00:04:03.269> so<00:04:03.659> you<00:04:03.750> end<00:04:03.930> up<00:04:04.079> always<00:04:04.439> at<00:04:04.979> a 00:04:05.030 --> 00:04:05.040 align:start position:0% moving forward so you end up always at a 00:04:05.040 --> 00:04:07.490 align:start position:0% moving forward so you end up always at a place<00:04:05.310> you<00:04:05.489> want<00:04:05.669> to<00:04:05.729> end<00:04:05.849> up<00:04:06.000> but<00:04:06.720> you<00:04:07.079> you 00:04:07.490 --> 00:04:07.500 align:start position:0% place you want to end up but you you 00:04:07.500 --> 00:04:08.960 align:start position:0% place you want to end up but you you always<00:04:07.799> are<00:04:07.979> looking<00:04:08.220> back<00:04:08.400> and<00:04:08.609> make<00:04:08.729> sure 00:04:08.960 --> 00:04:08.970 align:start position:0% always are looking back and make sure 00:04:08.970 --> 00:04:10.849 align:start position:0% always are looking back and make sure you're<00:04:09.180> solid<00:04:09.569> on<00:04:09.659> your<00:04:09.810> foundation<00:04:10.379> before 00:04:10.849 --> 00:04:10.859 align:start position:0% you're solid on your foundation before 00:04:10.859 --> 00:04:14.449 align:start position:0% you're solid on your foundation before you<00:04:11.159> move<00:04:11.340> next<00:04:11.729> to<00:04:11.939> the<00:04:12.180> next<00:04:12.389> step<00:04:13.370> so<00:04:14.370> the 00:04:14.449 --> 00:04:14.459 align:start position:0% you move next to the next step so the 00:04:14.459 --> 00:04:15.979 align:start position:0% you move next to the next step so the first<00:04:14.669> part<00:04:14.819> is<00:04:14.970> just<00:04:15.209> having<00:04:15.389> a<00:04:15.689> really<00:04:15.900> good 00:04:15.979 --> 00:04:15.989 align:start position:0% first part is just having a really good 00:04:15.989 --> 00:04:18.020 align:start position:0% first part is just having a really good design<00:04:16.320> spec<00:04:16.789> understanding<00:04:17.789> with<00:04:17.909> the 00:04:18.020 --> 00:04:18.030 align:start position:0% design spec understanding with the 00:04:18.030 --> 00:04:20.420 align:start position:0% design spec understanding with the customers<00:04:18.449> or<00:04:18.840> or<00:04:19.560> you<00:04:19.979> know<00:04:20.070> the<00:04:20.159> business 00:04:20.420 --> 00:04:20.430 align:start position:0% customers or or you know the business 00:04:20.430 --> 00:04:22.190 align:start position:0% customers or or you know the business leaders<00:04:21.120> of<00:04:21.269> your<00:04:21.419> company<00:04:21.719> or<00:04:21.810> anyone<00:04:22.049> who 00:04:22.190 --> 00:04:22.200 align:start position:0% leaders of your company or anyone who 00:04:22.200 --> 00:04:23.990 align:start position:0% leaders of your company or anyone who has<00:04:22.289> like<00:04:22.590> the<00:04:22.830> solid<00:04:23.130> idea<00:04:23.370> like<00:04:23.580> what<00:04:23.789> it<00:04:23.909> is 00:04:23.990 --> 00:04:24.000 align:start position:0% has like the solid idea like what it is 00:04:24.000 --> 00:04:25.700 align:start position:0% has like the solid idea like what it is you're<00:04:24.180> actually<00:04:24.330> doing 00:04:25.700 --> 00:04:25.710 align:start position:0% you're actually doing 00:04:25.710 --> 00:04:27.559 align:start position:0% you're actually doing and<00:04:25.830> you'll<00:04:26.400> always<00:04:26.639> be<00:04:26.880> constantly<00:04:27.330> coming 00:04:27.559 --> 00:04:27.569 align:start position:0% and you'll always be constantly coming 00:04:27.569 --> 00:04:28.939 align:start position:0% and you'll always be constantly coming back<00:04:27.720> to<00:04:27.900> this<00:04:27.990> and<00:04:28.229> making<00:04:28.350> sure<00:04:28.590> that<00:04:28.800> you 00:04:28.939 --> 00:04:28.949 align:start position:0% back to this and making sure that you 00:04:28.949 --> 00:04:32.360 align:start position:0% back to this and making sure that you have<00:04:28.979> very<00:04:29.819> solid<00:04:30.060> firm<00:04:30.419> idea<00:04:31.169> and<00:04:31.590> grasp<00:04:32.100> on 00:04:32.360 --> 00:04:32.370 align:start position:0% have very solid firm idea and grasp on 00:04:32.370 --> 00:04:34.159 align:start position:0% have very solid firm idea and grasp on what<00:04:32.490> you're<00:04:32.610> actually<00:04:32.729> doing<00:04:32.940> if<00:04:33.870> you<00:04:33.990> don't 00:04:34.159 --> 00:04:34.169 align:start position:0% what you're actually doing if you don't 00:04:34.169 --> 00:04:36.080 align:start position:0% what you're actually doing if you don't have<00:04:34.349> this<00:04:34.590> you<00:04:34.800> end<00:04:34.949> up<00:04:35.130> in<00:04:35.340> a<00:04:35.430> position<00:04:35.550> where 00:04:36.080 --> 00:04:36.090 align:start position:0% have this you end up in a position where 00:04:36.090 --> 00:04:38.330 align:start position:0% have this you end up in a position where you're<00:04:36.870> constantly<00:04:37.169> iterating<00:04:37.590> and<00:04:37.889> you<00:04:38.069> you 00:04:38.330 --> 00:04:38.340 align:start position:0% you're constantly iterating and you you 00:04:38.340 --> 00:04:40.100 align:start position:0% you're constantly iterating and you you you<00:04:38.370> sort<00:04:38.910> of<00:04:38.940> lose<00:04:39.120> focus<00:04:39.360> of<00:04:39.569> actually<00:04:39.990> what 00:04:40.100 --> 00:04:40.110 align:start position:0% you sort of lose focus of actually what 00:04:40.110 --> 00:04:41.350 align:start position:0% you sort of lose focus of actually what you<00:04:40.199> were<00:04:40.289> trying<00:04:40.500> to<00:04:40.560> do<00:04:40.680> in<00:04:40.770> the<00:04:40.830> first<00:04:40.949> place 00:04:41.350 --> 00:04:41.360 align:start position:0% you were trying to do in the first place 00:04:41.360 --> 00:04:43.730 align:start position:0% you were trying to do in the first place and<00:04:42.360> if<00:04:42.479> you<00:04:42.660> don't<00:04:42.810> have<00:04:42.960> that<00:04:43.139> real<00:04:43.289> focus 00:04:43.730 --> 00:04:43.740 align:start position:0% and if you don't have that real focus 00:04:43.740 --> 00:04:45.650 align:start position:0% and if you don't have that real focus it's<00:04:44.310> really<00:04:44.580> hard<00:04:44.849> to<00:04:45.120> make<00:04:45.330> a<00:04:45.360> determination 00:04:45.650 --> 00:04:45.660 align:start position:0% it's really hard to make a determination 00:04:45.660 --> 00:04:48.110 align:start position:0% it's really hard to make a determination of<00:04:46.169> is<00:04:46.740> this<00:04:47.190> decision<00:04:47.580> I'm<00:04:47.699> making<00:04:47.729> the<00:04:48.030> right 00:04:48.110 --> 00:04:48.120 align:start position:0% of is this decision I'm making the right 00:04:48.120 --> 00:04:49.850 align:start position:0% of is this decision I'm making the right decision<00:04:48.180> am<00:04:48.840> I<00:04:49.470> going<00:04:49.620> in<00:04:49.740> the<00:04:49.800> right 00:04:49.850 --> 00:04:49.860 align:start position:0% decision am I going in the right 00:04:49.860 --> 00:04:53.629 align:start position:0% decision am I going in the right direction<00:04:51.289> so<00:04:52.289> from<00:04:52.500> there<00:04:52.620> you<00:04:52.770> sort<00:04:52.979> of<00:04:53.069> take 00:04:53.629 --> 00:04:53.639 align:start position:0% direction so from there you sort of take 00:04:53.639 --> 00:04:56.120 align:start position:0% direction so from there you sort of take your<00:04:53.759> design<00:04:54.030> spec<00:04:54.360> and<00:04:54.690> it<00:04:55.080> should<00:04:55.289> be<00:04:55.410> a<00:04:55.440> the 00:04:56.120 --> 00:04:56.130 align:start position:0% your design spec and it should be a the 00:04:56.130 --> 00:04:57.980 align:start position:0% your design spec and it should be a the design<00:04:56.310> spec<00:04:56.669> itself<00:04:56.970> should<00:04:57.270> be<00:04:57.389> like<00:04:57.630> human 00:04:57.980 --> 00:04:57.990 align:start position:0% design spec itself should be like human 00:04:57.990 --> 00:04:59.839 align:start position:0% design spec itself should be like human readable<00:04:58.380> something<00:04:59.130> you<00:04:59.220> can<00:04:59.340> show<00:04:59.520> somebody 00:04:59.839 --> 00:04:59.849 align:start position:0% readable something you can show somebody 00:04:59.849 --> 00:05:01.310 align:start position:0% readable something you can show somebody else<00:05:00.000> who's<00:05:00.150> non-technical<00:05:00.720> an<00:05:00.900> agent 00:05:01.310 --> 00:05:01.320 align:start position:0% else who's non-technical an agent 00:05:01.320 --> 00:05:03.050 align:start position:0% else who's non-technical an agent understand<00:05:01.770> and<00:05:01.919> get<00:05:02.009> your<00:05:02.130> project<00:05:02.550> it's 00:05:03.050 --> 00:05:03.060 align:start position:0% understand and get your project it's 00:05:03.060 --> 00:05:05.510 align:start position:0% understand and get your project it's kind<00:05:03.270> of<00:05:03.360> like<00:05:03.479> a<00:05:03.509> white<00:05:03.720> paper<00:05:03.900> almost<00:05:04.460> so<00:05:05.460> you 00:05:05.510 --> 00:05:05.520 align:start position:0% kind of like a white paper almost so you 00:05:05.520 --> 00:05:07.310 align:start position:0% kind of like a white paper almost so you take<00:05:05.759> that<00:05:05.940> and<00:05:06.180> the<00:05:06.599> next<00:05:06.840> step<00:05:06.990> you<00:05:07.110> go<00:05:07.229> is 00:05:07.310 --> 00:05:07.320 align:start position:0% take that and the next step you go is 00:05:07.320 --> 00:05:08.960 align:start position:0% take that and the next step you go is the<00:05:07.440> architecture<00:05:07.919> so<00:05:08.099> that<00:05:08.130> is<00:05:08.430> the<00:05:08.729> you<00:05:08.849> know 00:05:08.960 --> 00:05:08.970 align:start position:0% the architecture so that is the you know 00:05:08.970 --> 00:05:10.700 align:start position:0% the architecture so that is the you know the<00:05:09.479> really<00:05:09.599> solid<00:05:09.990> underpinnings<00:05:10.440> of<00:05:10.590> your 00:05:10.700 --> 00:05:10.710 align:start position:0% the really solid underpinnings of your 00:05:10.710 --> 00:05:13.159 align:start position:0% the really solid underpinnings of your project<00:05:11.070> you<00:05:11.370> start<00:05:12.000> to<00:05:12.090> design<00:05:12.240> like<00:05:12.599> what 00:05:13.159 --> 00:05:13.169 align:start position:0% project you start to design like what 00:05:13.169 --> 00:05:14.659 align:start position:0% project you start to design like what kinds<00:05:13.410> of<00:05:13.470> contracts<00:05:13.889> am<00:05:14.009> I<00:05:14.070> gonna<00:05:14.160> have<00:05:14.430> how 00:05:14.659 --> 00:05:14.669 align:start position:0% kinds of contracts am I gonna have how 00:05:14.669 --> 00:05:16.370 align:start position:0% kinds of contracts am I gonna have how it's<00:05:14.789> gonna<00:05:14.880> interact<00:05:15.240> with<00:05:16.020> all<00:05:16.139> the<00:05:16.199> other 00:05:16.370 --> 00:05:16.380 align:start position:0% it's gonna interact with all the other 00:05:16.380 --> 00:05:19.820 align:start position:0% it's gonna interact with all the other components<00:05:16.680> in<00:05:16.979> my<00:05:17.099> application<00:05:17.669> and<00:05:17.880> how<00:05:18.830> you 00:05:19.820 --> 00:05:19.830 align:start position:0% components in my application and how you 00:05:19.830 --> 00:05:20.779 align:start position:0% components in my application and how you know<00:05:19.889> what<00:05:20.070> names<00:05:20.310> I<00:05:20.490> want<00:05:20.580> to<00:05:20.669> give 00:05:20.779 --> 00:05:20.789 align:start position:0% know what names I want to give 00:05:20.789 --> 00:05:23.749 align:start position:0% know what names I want to give everything<00:05:21.000> and<00:05:21.740> and<00:05:22.740> that<00:05:23.250> really<00:05:23.280> gives<00:05:23.669> you 00:05:23.749 --> 00:05:23.759 align:start position:0% everything and and that really gives you 00:05:23.759 --> 00:05:25.249 align:start position:0% everything and and that really gives you a<00:05:23.789> solid<00:05:24.000> foundation<00:05:24.630> for<00:05:24.750> the<00:05:24.810> next<00:05:25.080> step 00:05:25.249 --> 00:05:25.259 align:start position:0% a solid foundation for the next step 00:05:25.259 --> 00:05:28.370 align:start position:0% a solid foundation for the next step which<00:05:25.440> is<00:05:25.819> designing<00:05:26.819> requirements<00:05:27.449> so<00:05:27.659> you 00:05:28.370 --> 00:05:28.380 align:start position:0% which is designing requirements so you 00:05:28.380 --> 00:05:30.080 align:start position:0% which is designing requirements so you can<00:05:28.560> go<00:05:28.710> you<00:05:29.159> know<00:05:29.280> ray<00:05:29.490> off<00:05:29.639> the<00:05:29.789> deep<00:05:29.940> end 00:05:30.080 --> 00:05:30.090 align:start position:0% can go you know ray off the deep end 00:05:30.090 --> 00:05:32.420 align:start position:0% can go you know ray off the deep end with<00:05:30.270> this<00:05:30.419> like<00:05:30.750> we<00:05:30.900> did<00:05:31.349> in<00:05:31.530> aerospace<00:05:32.130> it 00:05:32.420 --> 00:05:32.430 align:start position:0% with this like we did in aerospace it 00:05:32.430 --> 00:05:33.529 align:start position:0% with this like we did in aerospace it took<00:05:32.550> us<00:05:32.669> months<00:05:32.820> to<00:05:33.000> actually<00:05:33.389> get 00:05:33.529 --> 00:05:33.539 align:start position:0% took us months to actually get 00:05:33.539 --> 00:05:35.330 align:start position:0% took us months to actually get requirement<00:05:34.020> specs<00:05:34.229> through<00:05:34.440> the<00:05:34.530> door<00:05:34.680> or 00:05:35.330 --> 00:05:35.340 align:start position:0% requirement specs through the door or 00:05:35.340 --> 00:05:37.339 align:start position:0% requirement specs through the door or you<00:05:35.789> can<00:05:35.909> just<00:05:36.120> use<00:05:36.300> this<00:05:36.479> as<00:05:36.539> a<00:05:36.720> process<00:05:37.229> to 00:05:37.339 --> 00:05:37.349 align:start position:0% you can just use this as a process to 00:05:37.349 --> 00:05:39.320 align:start position:0% you can just use this as a process to say<00:05:37.530> like<00:05:37.740> hey<00:05:37.919> what<00:05:38.699> are<00:05:38.729> the<00:05:38.909> technical 00:05:39.320 --> 00:05:39.330 align:start position:0% say like hey what are the technical 00:05:39.330 --> 00:05:40.879 align:start position:0% say like hey what are the technical things<00:05:39.720> we<00:05:39.870> need<00:05:40.020> to<00:05:40.050> do<00:05:40.259> in<00:05:40.409> each<00:05:40.530> one<00:05:40.680> of<00:05:40.740> our 00:05:40.879 --> 00:05:40.889 align:start position:0% things we need to do in each one of our 00:05:40.889 --> 00:05:43.850 align:start position:0% things we need to do in each one of our pieces<00:05:41.159> to<00:05:41.880> make<00:05:42.000> sure<00:05:42.180> they're<00:05:42.389> like<00:05:42.780> to<00:05:43.740> the 00:05:43.850 --> 00:05:43.860 align:start position:0% pieces to make sure they're like to the 00:05:43.860 --> 00:05:45.320 align:start position:0% pieces to make sure they're like to the degree<00:05:44.099> we<00:05:44.250> want<00:05:44.490> and<00:05:44.669> you<00:05:44.729> can<00:05:44.880> write<00:05:45.000> this<00:05:45.150> in 00:05:45.320 --> 00:05:45.330 align:start position:0% degree we want and you can write this in 00:05:45.330 --> 00:05:47.330 align:start position:0% degree we want and you can write this in like<00:05:45.509> a<00:05:45.539> comet<00:05:45.930> field<00:05:46.110> at<00:05:46.770> the<00:05:46.889> top<00:05:47.099> of<00:05:47.250> each 00:05:47.330 --> 00:05:47.340 align:start position:0% like a comet field at the top of each 00:05:47.340 --> 00:05:49.670 align:start position:0% like a comet field at the top of each smart<00:05:47.639> contract<00:05:48.150> however<00:05:49.050> you<00:05:49.289> want<00:05:49.440> to<00:05:49.530> keep 00:05:49.670 --> 00:05:49.680 align:start position:0% smart contract however you want to keep 00:05:49.680 --> 00:05:51.499 align:start position:0% smart contract however you want to keep track<00:05:49.919> of<00:05:49.949> it<00:05:50.130> just<00:05:50.250> make<00:05:50.430> it<00:05:50.550> clear<00:05:50.880> and<00:05:51.030> make 00:05:51.499 --> 00:05:51.509 align:start position:0% track of it just make it clear and make 00:05:51.509 --> 00:05:52.879 align:start position:0% track of it just make it clear and make it<00:05:51.630> easy<00:05:51.780> to<00:05:51.960> understand<00:05:52.409> like<00:05:52.650> how<00:05:52.680> that 00:05:52.879 --> 00:05:52.889 align:start position:0% it easy to understand like how that 00:05:52.889 --> 00:05:55.279 align:start position:0% it easy to understand like how that links<00:05:53.460> back<00:05:53.669> to<00:05:53.729> your<00:05:53.969> idea<00:05:54.090> so<00:05:55.080> you<00:05:55.139> have<00:05:55.229> a 00:05:55.279 --> 00:05:55.289 align:start position:0% links back to your idea so you have a 00:05:55.289 --> 00:05:56.990 align:start position:0% links back to your idea so you have a clear<00:05:55.560> view<00:05:55.860> of<00:05:56.159> traceability<00:05:56.699> all 00:05:56.990 --> 00:05:57.000 align:start position:0% clear view of traceability all 00:05:57.000 --> 00:06:00.350 align:start position:0% clear view of traceability all throughout<00:05:57.210> your<00:05:57.360> application<00:05:59.090> so<00:06:00.090> from 00:06:00.350 --> 00:06:00.360 align:start position:0% throughout your application so from 00:06:00.360 --> 00:06:01.420 align:start position:0% throughout your application so from there<00:06:00.479> once<00:06:00.690> you<00:06:00.780> have<00:06:00.930> your<00:06:01.110> requirements 00:06:01.420 --> 00:06:01.430 align:start position:0% there once you have your requirements 00:06:01.430 --> 00:06:03.770 align:start position:0% there once you have your requirements you're<00:06:02.430> at<00:06:02.550> the<00:06:02.699> bottom<00:06:02.940> of<00:06:03.030> this<00:06:03.180> V<00:06:03.389> cycle 00:06:03.770 --> 00:06:03.780 align:start position:0% you're at the bottom of this V cycle 00:06:03.780 --> 00:06:05.719 align:start position:0% you're at the bottom of this V cycle here<00:06:03.960> you<00:06:04.620> start<00:06:04.860> the<00:06:04.979> code<00:06:05.190> do<00:06:05.370> you<00:06:05.430> just<00:06:05.610> do 00:06:05.719 --> 00:06:05.729 align:start position:0% here you start the code do you just do 00:06:05.729 --> 00:06:08.270 align:start position:0% here you start the code do you just do the<00:06:05.849> thing<00:06:06.060> you<00:06:06.960> have<00:06:07.169> all<00:06:07.500> this<00:06:07.710> solid 00:06:08.270 --> 00:06:08.280 align:start position:0% the thing you have all this solid 00:06:08.280 --> 00:06:09.890 align:start position:0% the thing you have all this solid underpinning<00:06:08.820> of<00:06:09.000> understanding<00:06:09.630> of<00:06:09.719> what 00:06:09.890 --> 00:06:09.900 align:start position:0% underpinning of understanding of what 00:06:09.900 --> 00:06:11.749 align:start position:0% underpinning of understanding of what well<00:06:10.409> you're<00:06:10.530> actually<00:06:10.680> building<00:06:11.219> behind<00:06:11.580> you 00:06:11.749 --> 00:06:11.759 align:start position:0% well you're actually building behind you 00:06:11.759 --> 00:06:13.640 align:start position:0% well you're actually building behind you and<00:06:11.940> you<00:06:12.509> can<00:06:12.539> iterate<00:06:12.810> on<00:06:13.020> that<00:06:13.169> as<00:06:13.500> you 00:06:13.640 --> 00:06:13.650 align:start position:0% and you can iterate on that as you 00:06:13.650 --> 00:06:16.189 align:start position:0% and you can iterate on that as you discover<00:06:13.979> new<00:06:14.190> things<00:06:14.219> in<00:06:14.520> code<00:06:14.729> and<00:06:15.030> you<00:06:15.599> you 00:06:16.189 --> 00:06:16.199 align:start position:0% discover new things in code and you you 00:06:16.199 --> 00:06:17.810 align:start position:0% discover new things in code and you you know<00:06:16.289> identify<00:06:17.039> things<00:06:17.250> you<00:06:17.370> want<00:06:17.520> to<00:06:17.580> change 00:06:17.810 --> 00:06:17.820 align:start position:0% know identify things you want to change 00:06:17.820 --> 00:06:20.749 align:start position:0% know identify things you want to change about<00:06:18.449> your<00:06:18.570> design<00:06:19.159> but<00:06:20.159> because<00:06:20.520> you<00:06:20.610> have 00:06:20.749 --> 00:06:20.759 align:start position:0% about your design but because you have 00:06:20.759 --> 00:06:23.209 align:start position:0% about your design but because you have this<00:06:20.880> solid<00:06:21.240> traceability<00:06:21.810> down<00:06:22.320> the<00:06:23.009> left 00:06:23.209 --> 00:06:23.219 align:start position:0% this solid traceability down the left 00:06:23.219 --> 00:06:25.580 align:start position:0% this solid traceability down the left side<00:06:23.400> of<00:06:23.520> the<00:06:23.610> V<00:06:23.789> you<00:06:24.060> always<00:06:24.870> understand<00:06:25.380> like 00:06:25.580 --> 00:06:25.590 align:start position:0% side of the V you always understand like 00:06:25.590 --> 00:06:27.980 align:start position:0% side of the V you always understand like well<00:06:26.280> I<00:06:26.580> just<00:06:27.030> want<00:06:27.419> to<00:06:27.449> update<00:06:27.599> this<00:06:27.810> one 00:06:27.980 --> 00:06:27.990 align:start position:0% well I just want to update this one 00:06:27.990 --> 00:06:29.839 align:start position:0% well I just want to update this one thing<00:06:28.289> and<00:06:28.590> then<00:06:29.039> you<00:06:29.130> can<00:06:29.250> analyze<00:06:29.639> the 00:06:29.839 --> 00:06:29.849 align:start position:0% thing and then you can analyze the 00:06:29.849 --> 00:06:32.029 align:start position:0% thing and then you can analyze the change<00:06:30.090> impact<00:06:30.479> that<00:06:30.719> has<00:06:30.960> you<00:06:31.740> could<00:06:31.860> say<00:06:32.009> oh 00:06:32.029 --> 00:06:32.039 align:start position:0% change impact that has you could say oh 00:06:32.039 --> 00:06:34.129 align:start position:0% change impact that has you could say oh well<00:06:32.159> this<00:06:32.729> little<00:06:33.000> piece<00:06:33.180> gets<00:06:33.479> changed<00:06:33.900> and 00:06:34.129 --> 00:06:34.139 align:start position:0% well this little piece gets changed and 00:06:34.139 --> 00:06:36.110 align:start position:0% well this little piece gets changed and I<00:06:34.289> update<00:06:34.680> this<00:06:34.830> other<00:06:35.039> piece<00:06:35.279> everything's 00:06:36.110 --> 00:06:36.120 align:start position:0% I update this other piece everything's 00:06:36.120 --> 00:06:38.410 align:start position:0% I update this other piece everything's fine 00:06:38.410 --> 00:06:38.420 align:start position:0% 00:06:38.420 --> 00:06:40.090 align:start position:0% the<00:06:38.720> really<00:06:38.900> cool<00:06:39.080> thing<00:06:39.410> is<00:06:39.440> that<00:06:39.860> because 00:06:40.090 --> 00:06:40.100 align:start position:0% the really cool thing is that because 00:06:40.100 --> 00:06:41.140 align:start position:0% the really cool thing is that because you've<00:06:40.340> gotten<00:06:40.610> requirements<00:06:41.060> and 00:06:41.140 --> 00:06:41.150 align:start position:0% you've gotten requirements and 00:06:41.150 --> 00:06:43.060 align:start position:0% you've gotten requirements and architecture<00:06:41.600> down<00:06:41.750> on<00:06:41.900> paper<00:06:42.140> you<00:06:42.800> know<00:06:42.920> what 00:06:43.060 --> 00:06:43.070 align:start position:0% architecture down on paper you know what 00:06:43.070 --> 00:06:44.290 align:start position:0% architecture down on paper you know what you're<00:06:43.190> calling<00:06:43.400> everything<00:06:43.820> you<00:06:44.060> know<00:06:44.210> what 00:06:44.290 --> 00:06:44.300 align:start position:0% you're calling everything you know what 00:06:44.300 --> 00:06:46.090 align:start position:0% you're calling everything you know what everything's<00:06:44.630> supposed<00:06:44.840> to<00:06:44.930> do<00:06:45.110> you<00:06:45.830> can<00:06:46.010> do 00:06:46.090 --> 00:06:46.100 align:start position:0% everything's supposed to do you can do 00:06:46.100 --> 00:06:48.550 align:start position:0% everything's supposed to do you can do testing<00:06:46.490> in<00:06:46.550> parallel<00:06:46.970> you<00:06:47.180> can<00:06:47.210> you<00:06:48.170> can<00:06:48.350> get 00:06:48.550 --> 00:06:48.560 align:start position:0% testing in parallel you can you can get 00:06:48.560 --> 00:06:50.530 align:start position:0% testing in parallel you can you can get a<00:06:48.590> whole<00:06:48.830> separate<00:06:49.190> team<00:06:49.370> on<00:06:49.580> board<00:06:49.790> and<00:06:50.090> have 00:06:50.530 --> 00:06:50.540 align:start position:0% a whole separate team on board and have 00:06:50.540 --> 00:06:52.180 align:start position:0% a whole separate team on board and have them<00:06:50.720> work<00:06:50.870> in<00:06:51.050> parallel<00:06:51.380> on<00:06:51.470> you<00:06:51.860> know<00:06:51.950> test 00:06:52.180 --> 00:06:52.190 align:start position:0% them work in parallel on you know test 00:06:52.190 --> 00:06:54.490 align:start position:0% them work in parallel on you know test different<00:06:52.310> Velma<00:06:52.790> processes<00:06:53.360> and<00:06:53.600> have<00:06:54.320> them 00:06:54.490 --> 00:06:54.500 align:start position:0% different Velma processes and have them 00:06:54.500 --> 00:06:56.650 align:start position:0% different Velma processes and have them start<00:06:54.770> writing<00:06:55.040> tests<00:06:55.430> that<00:06:55.580> link<00:06:56.030> to<00:06:56.210> each 00:06:56.650 --> 00:06:56.660 align:start position:0% start writing tests that link to each 00:06:56.660 --> 00:06:59.760 align:start position:0% start writing tests that link to each requirements<00:06:58.000> everything<00:06:59.000> you<00:06:59.060> want<00:06:59.240> to<00:06:59.300> do 00:06:59.760 --> 00:06:59.770 align:start position:0% requirements everything you want to do 00:06:59.770 --> 00:07:02.500 align:start position:0% requirements everything you want to do so<00:07:00.770> you<00:07:00.830> can<00:07:01.370> kind<00:07:01.610> of<00:07:01.670> save<00:07:01.880> some<00:07:02.060> time<00:07:02.300> and 00:07:02.500 --> 00:07:02.510 align:start position:0% so you can kind of save some time and 00:07:02.510 --> 00:07:04.330 align:start position:0% so you can kind of save some time and effort<00:07:02.600> from<00:07:03.230> that<00:07:03.440> by<00:07:03.710> having<00:07:04.010> two<00:07:04.130> teams 00:07:04.330 --> 00:07:04.340 align:start position:0% effort from that by having two teams 00:07:04.340 --> 00:07:05.680 align:start position:0% effort from that by having two teams working<00:07:04.550> in<00:07:04.790> parallel<00:07:05.000> instead<00:07:05.390> of<00:07:05.480> waiting 00:07:05.680 --> 00:07:05.690 align:start position:0% working in parallel instead of waiting 00:07:05.690 --> 00:07:07.030 align:start position:0% working in parallel instead of waiting for<00:07:05.810> the<00:07:05.960> code<00:07:06.110> to<00:07:06.230> be<00:07:06.260> done<00:07:06.470> before<00:07:06.680> you<00:07:06.890> write 00:07:07.030 --> 00:07:07.040 align:start position:0% for the code to be done before you write 00:07:07.040 --> 00:07:09.640 align:start position:0% for the code to be done before you write tests<00:07:07.600> usually<00:07:08.600> the<00:07:08.900> tests<00:07:09.170> come<00:07:09.320> out<00:07:09.440> better 00:07:09.640 --> 00:07:09.650 align:start position:0% tests usually the tests come out better 00:07:09.650 --> 00:07:11.620 align:start position:0% tests usually the tests come out better when<00:07:09.890> you<00:07:10.070> don't<00:07:10.190> have<00:07:10.370> the<00:07:11.090> tester<00:07:11.450> the 00:07:11.620 --> 00:07:11.630 align:start position:0% when you don't have the tester the 00:07:11.630 --> 00:07:14.260 align:start position:0% when you don't have the tester the person<00:07:11.960> designing<00:07:12.320> the<00:07:12.560> verification<00:07:13.270> going 00:07:14.260 --> 00:07:14.270 align:start position:0% person designing the verification going 00:07:14.270 --> 00:07:15.700 align:start position:0% person designing the verification going back<00:07:14.420> to<00:07:14.540> the<00:07:14.660> code<00:07:14.840> to<00:07:15.020> say<00:07:15.170> like<00:07:15.380> hey<00:07:15.530> what 00:07:15.700 --> 00:07:15.710 align:start position:0% back to the code to say like hey what 00:07:15.710 --> 00:07:17.350 align:start position:0% back to the code to say like hey what does<00:07:15.800> this<00:07:15.860> do<00:07:16.160> it<00:07:16.460> actually<00:07:17.060> makes<00:07:17.240> your 00:07:17.350 --> 00:07:17.360 align:start position:0% does this do it actually makes your 00:07:17.360 --> 00:07:18.970 align:start position:0% does this do it actually makes your documentation<00:07:17.930> more<00:07:18.290> improved<00:07:18.620> because 00:07:18.970 --> 00:07:18.980 align:start position:0% documentation more improved because 00:07:18.980 --> 00:07:20.770 align:start position:0% documentation more improved because they're<00:07:19.580> looking<00:07:19.730> at<00:07:19.940> that<00:07:20.090> to<00:07:20.300> design<00:07:20.480> the 00:07:20.770 --> 00:07:20.780 align:start position:0% they're looking at that to design the 00:07:20.780 --> 00:07:23.560 align:start position:0% they're looking at that to design the tests<00:07:20.990> instead<00:07:21.260> of<00:07:21.410> your<00:07:21.530> code<00:07:21.800> and<00:07:22.420> you<00:07:23.420> make 00:07:23.560 --> 00:07:23.570 align:start position:0% tests instead of your code and you make 00:07:23.570 --> 00:07:24.610 align:start position:0% tests instead of your code and you make sure<00:07:23.600> you<00:07:23.810> build<00:07:23.960> it<00:07:24.110> like<00:07:24.140> a<00:07:24.290> stronger 00:07:24.610 --> 00:07:24.620 align:start position:0% sure you build it like a stronger 00:07:24.620 --> 00:07:28.630 align:start position:0% sure you build it like a stronger project<00:07:24.980> out<00:07:25.220> of<00:07:25.250> the<00:07:25.400> gate<00:07:25.900> so<00:07:27.460> the<00:07:28.460> really 00:07:28.630 --> 00:07:28.640 align:start position:0% project out of the gate so the really 00:07:28.640 --> 00:07:30.760 align:start position:0% project out of the gate so the really cool<00:07:28.760> thing<00:07:29.030> is<00:07:29.060> that<00:07:29.360> as<00:07:29.540> you<00:07:29.780> go<00:07:29.900> up<00:07:30.140> the<00:07:30.380> V<00:07:30.530> on 00:07:30.760 --> 00:07:30.770 align:start position:0% cool thing is that as you go up the V on 00:07:30.770 --> 00:07:32.830 align:start position:0% cool thing is that as you go up the V on the<00:07:30.800> right<00:07:31.040> hand<00:07:31.250> side<00:07:31.370> this<00:07:32.270> is<00:07:32.420> how<00:07:32.540> you<00:07:32.600> know 00:07:32.830 --> 00:07:32.840 align:start position:0% the right hand side this is how you know 00:07:32.840 --> 00:07:34.150 align:start position:0% the right hand side this is how you know you're<00:07:33.020> getting<00:07:33.200> closer<00:07:33.410> and<00:07:33.530> closer<00:07:33.740> to<00:07:33.860> done 00:07:34.150 --> 00:07:34.160 align:start position:0% you're getting closer and closer to done 00:07:34.160 --> 00:07:35.320 align:start position:0% you're getting closer and closer to done you<00:07:34.310> can<00:07:34.430> actually<00:07:34.550> design<00:07:34.910> a<00:07:34.940> schedule 00:07:35.320 --> 00:07:35.330 align:start position:0% you can actually design a schedule 00:07:35.330 --> 00:07:39.220 align:start position:0% you can actually design a schedule around<00:07:35.420> this<00:07:35.830> so<00:07:37.720> so<00:07:38.720> once<00:07:38.900> you're<00:07:39.050> at<00:07:39.110> that 00:07:39.220 --> 00:07:39.230 align:start position:0% around this so so once you're at that 00:07:39.230 --> 00:07:40.600 align:start position:0% around this so so once you're at that bottom<00:07:39.560> point<00:07:39.680> you're<00:07:40.010> doing<00:07:40.220> code<00:07:40.430> and 00:07:40.600 --> 00:07:40.610 align:start position:0% bottom point you're doing code and 00:07:40.610 --> 00:07:42.790 align:start position:0% bottom point you're doing code and testing<00:07:40.970> you<00:07:41.090> sort<00:07:41.300> of<00:07:41.330> iterate<00:07:41.630> in<00:07:41.750> this<00:07:41.900> very 00:07:42.790 --> 00:07:42.800 align:start position:0% testing you sort of iterate in this very 00:07:42.800 --> 00:07:44.710 align:start position:0% testing you sort of iterate in this very short<00:07:42.890> loop<00:07:43.310> between<00:07:43.490> requirements<00:07:44.150> code<00:07:44.570> and 00:07:44.710 --> 00:07:44.720 align:start position:0% short loop between requirements code and 00:07:44.720 --> 00:07:47.080 align:start position:0% short loop between requirements code and testing<00:07:45.490> updating<00:07:46.490> anything<00:07:46.880> on<00:07:46.970> the 00:07:47.080 --> 00:07:47.090 align:start position:0% testing updating anything on the 00:07:47.090 --> 00:07:50.440 align:start position:0% testing updating anything on the left-hand<00:07:47.480> side<00:07:47.570> as<00:07:48.100> needed<00:07:49.100> and<00:07:49.370> until<00:07:50.150> you 00:07:50.440 --> 00:07:50.450 align:start position:0% left-hand side as needed and until you 00:07:50.450 --> 00:07:52.690 align:start position:0% left-hand side as needed and until you finish<00:07:50.840> testing<00:07:51.470> you<00:07:51.710> get<00:07:51.830> all<00:07:51.980> greens<00:07:52.370> on 00:07:52.690 --> 00:07:52.700 align:start position:0% finish testing you get all greens on 00:07:52.700 --> 00:07:55.120 align:start position:0% finish testing you get all greens on your<00:07:52.850> huge<00:07:53.150> test<00:07:53.419> suite<00:07:53.710> from<00:07:54.710> there<00:07:54.890> you<00:07:55.010> move 00:07:55.120 --> 00:07:55.130 align:start position:0% your huge test suite from there you move 00:07:55.130 --> 00:07:56.500 align:start position:0% your huge test suite from there you move integration<00:07:55.760> you<00:07:55.880> kind<00:07:56.060> of<00:07:56.090> integrate<00:07:56.390> with 00:07:56.500 --> 00:07:56.510 align:start position:0% integration you kind of integrate with 00:07:56.510 --> 00:07:58.659 align:start position:0% integration you kind of integrate with the<00:07:56.600> rest<00:07:56.780> of<00:07:56.930> the<00:07:57.050> application<00:07:57.950> whether<00:07:58.520> it 00:07:58.659 --> 00:07:58.669 align:start position:0% the rest of the application whether it 00:07:58.669 --> 00:08:00.940 align:start position:0% the rest of the application whether it be<00:07:58.760> you<00:07:59.000> know<00:07:59.090> the<00:07:59.300> front<00:07:59.510> end<00:07:59.720> or<00:08:00.020> any<00:08:00.650> sort<00:08:00.919> of 00:08:00.940 --> 00:08:00.950 align:start position:0% be you know the front end or any sort of 00:08:00.950 --> 00:08:03.010 align:start position:0% be you know the front end or any sort of Damons<00:08:01.280> you<00:08:01.370> guys<00:08:01.520> written<00:08:01.850> or<00:08:02.060> networks<00:08:02.720> or 00:08:03.010 --> 00:08:03.020 align:start position:0% Damons you guys written or networks or 00:08:03.020 --> 00:08:04.659 align:start position:0% Damons you guys written or networks or you<00:08:03.530> know<00:08:03.590> plows<00:08:03.860> for<00:08:04.070> frame<00:08:04.250> Ericsson<00:08:04.640> and 00:08:04.659 --> 00:08:04.669 align:start position:0% you know plows for frame Ericsson and 00:08:04.669 --> 00:08:06.850 align:start position:0% you know plows for frame Ericsson and anything<00:08:05.180> you<00:08:05.300> guys<00:08:05.470> imagine<00:08:06.470> that<00:08:06.590> kind<00:08:06.800> of 00:08:06.850 --> 00:08:06.860 align:start position:0% anything you guys imagine that kind of 00:08:06.860 --> 00:08:08.290 align:start position:0% anything you guys imagine that kind of exists<00:08:07.250> outside<00:08:07.370> of<00:08:07.610> the<00:08:07.820> hypercritical 00:08:08.290 --> 00:08:08.300 align:start position:0% exists outside of the hypercritical 00:08:08.300 --> 00:08:10.120 align:start position:0% exists outside of the hypercritical design<00:08:09.230> you're<00:08:09.380> doing<00:08:09.680> with<00:08:09.800> the<00:08:09.890> smart 00:08:10.120 --> 00:08:10.130 align:start position:0% design you're doing with the smart 00:08:10.130 --> 00:08:12.460 align:start position:0% design you're doing with the smart contracts<00:08:10.669> and<00:08:11.660> this<00:08:11.900> works<00:08:12.110> for<00:08:12.230> anything 00:08:12.460 --> 00:08:12.470 align:start position:0% contracts and this works for anything 00:08:12.470 --> 00:08:15.240 align:start position:0% contracts and this works for anything not<00:08:12.830> even<00:08:13.310> just<00:08:13.400> smart<00:08:13.640> contracts<00:08:14.000> but 00:08:15.240 --> 00:08:15.250 align:start position:0% not even just smart contracts but 00:08:15.250 --> 00:08:16.480 align:start position:0% not even just smart contracts but hypercritical 00:08:16.480 --> 00:08:16.490 align:start position:0% hypercritical 00:08:16.490 --> 00:08:18.520 align:start position:0% hypercritical smart<00:08:17.450> contracts<00:08:17.780> are<00:08:17.870> hyper<00:08:18.020> critical<00:08:18.440> so 00:08:18.520 --> 00:08:18.530 align:start position:0% smart contracts are hyper critical so 00:08:18.530 --> 00:08:21.250 align:start position:0% smart contracts are hyper critical so that's<00:08:18.680> why<00:08:18.800> I<00:08:18.830> point<00:08:19.070> them<00:08:19.190> out<00:08:20.169> once<00:08:21.169> you're 00:08:21.250 --> 00:08:21.260 align:start position:0% that's why I point them out once you're 00:08:21.260 --> 00:08:22.750 align:start position:0% that's why I point them out once you're at<00:08:21.380> that<00:08:21.560> point<00:08:21.860> and<00:08:22.040> you<00:08:22.250> may<00:08:22.370> have<00:08:22.580> some 00:08:22.750 --> 00:08:22.760 align:start position:0% at that point and you may have some 00:08:22.760 --> 00:08:24.490 align:start position:0% at that point and you may have some iteration<00:08:23.330> in<00:08:23.450> this<00:08:23.630> cycle<00:08:23.930> tool<00:08:24.110> back<00:08:24.350> to 00:08:24.490 --> 00:08:24.500 align:start position:0% iteration in this cycle tool back to 00:08:24.500 --> 00:08:26.290 align:start position:0% iteration in this cycle tool back to your<00:08:24.590> architecture<00:08:25.190> because<00:08:25.850> you<00:08:25.970> made<00:08:26.090> some 00:08:26.290 --> 00:08:26.300 align:start position:0% your architecture because you made some 00:08:26.300 --> 00:08:27.790 align:start position:0% your architecture because you made some fundamental<00:08:26.560> misunderstandings<00:08:27.560> of<00:08:27.650> how<00:08:27.740> the 00:08:27.790 --> 00:08:27.800 align:start position:0% fundamental misunderstandings of how the 00:08:27.800 --> 00:08:30.010 align:start position:0% fundamental misunderstandings of how the tech<00:08:27.980> would<00:08:28.100> work<00:08:28.360> you're<00:08:29.360> basically<00:08:29.660> done<00:08:29.840> at 00:08:30.010 --> 00:08:30.020 align:start position:0% tech would work you're basically done at 00:08:30.020 --> 00:08:31.270 align:start position:0% tech would work you're basically done at this<00:08:30.140> point<00:08:30.380> you're<00:08:30.530> ready<00:08:30.560> to<00:08:30.830> go<00:08:30.950> to<00:08:31.010> demo 00:08:31.270 --> 00:08:31.280 align:start position:0% this point you're ready to go to demo 00:08:31.280 --> 00:08:34.870 align:start position:0% this point you're ready to go to demo and<00:08:31.520> test<00:08:31.760> and<00:08:32.140> release<00:08:33.190> so<00:08:34.190> you<00:08:34.219> create<00:08:34.700> your 00:08:34.870 --> 00:08:34.880 align:start position:0% and test and release so you create your 00:08:34.880 --> 00:08:37.810 align:start position:0% and test and release so you create your demo<00:08:35.770> you<00:08:36.770> you<00:08:37.099> probably<00:08:37.339> want<00:08:37.520> to<00:08:37.550> show<00:08:37.700> off 00:08:37.810 --> 00:08:37.820 align:start position:0% demo you you probably want to show off 00:08:37.820 --> 00:08:40.120 align:start position:0% demo you you probably want to show off on<00:08:38.060> a<00:08:38.120> test<00:08:38.479> and<00:08:38.839> then<00:08:38.930> start<00:08:39.289> bumping<00:08:39.830> it<00:08:40.039> up 00:08:40.120 --> 00:08:40.130 align:start position:0% on a test and then start bumping it up 00:08:40.130 --> 00:08:41.920 align:start position:0% on a test and then start bumping it up as<00:08:40.339> you<00:08:40.520> grow<00:08:40.760> more<00:08:40.789> and<00:08:41.150> more<00:08:41.300> confident 00:08:41.920 --> 00:08:41.930 align:start position:0% as you grow more and more confident 00:08:41.930 --> 00:08:44.290 align:start position:0% as you grow more and more confident under<00:08:42.289> what<00:08:42.710> what<00:08:43.219> you've<00:08:43.339> made<00:08:43.580> until<00:08:44.030> you're 00:08:44.290 --> 00:08:44.300 align:start position:0% under what what you've made until you're 00:08:44.300 --> 00:08:46.420 align:start position:0% under what what you've made until you're you<00:08:44.510> know<00:08:44.600> pushing<00:08:44.870> on<00:08:45.020> the<00:08:45.110> main<00:08:45.260> to<00:08:45.500> main<00:08:45.800> net 00:08:46.420 --> 00:08:46.430 align:start position:0% you know pushing on the main to main net 00:08:46.430 --> 00:08:48.610 align:start position:0% you know pushing on the main to main net and<00:08:46.640> starting<00:08:47.630> to<00:08:47.720> work<00:08:47.870> with<00:08:47.900> real<00:08:48.320> user 00:08:48.610 --> 00:08:48.620 align:start position:0% and starting to work with real user 00:08:48.620 --> 00:08:50.250 align:start position:0% and starting to work with real user fonts<00:08:49.060> so 00:08:50.250 --> 00:08:50.260 align:start position:0% fonts so 00:08:50.260 --> 00:08:51.690 align:start position:0% fonts so the<00:08:50.380> important<00:08:50.740> part<00:08:50.830> you<00:08:51.010> got<00:08:51.100> a<00:08:51.130> cert<00:08:51.340> small 00:08:51.690 --> 00:08:51.700 align:start position:0% the important part you got a cert small 00:08:51.700 --> 00:08:53.910 align:start position:0% the important part you got a cert small here<00:08:51.970> you<00:08:52.900> got<00:08:53.020> to<00:08:53.110> grow<00:08:53.290> that<00:08:53.560> as<00:08:53.710> you<00:08:53.800> grow 00:08:53.910 --> 00:08:53.920 align:start position:0% here you got to grow that as you grow 00:08:53.920 --> 00:08:55.650 align:start position:0% here you got to grow that as you grow confidence<00:08:54.520> and<00:08:54.820> make<00:08:55.000> sure<00:08:55.150> that<00:08:55.390> you're 00:08:55.650 --> 00:08:55.660 align:start position:0% confidence and make sure that you're 00:08:55.660 --> 00:08:58.290 align:start position:0% confidence and make sure that you're able<00:08:55.810> to<00:08:56.050> cover<00:08:56.230> any<00:08:56.470> losses<00:08:56.860> that<00:08:57.670> happen<00:08:58.060> so 00:08:58.290 --> 00:08:58.300 align:start position:0% able to cover any losses that happen so 00:08:58.300 --> 00:08:59.730 align:start position:0% able to cover any losses that happen so like<00:08:58.450> the<00:08:58.600> recent<00:08:58.870> spank<00:08:59.080> chain<00:08:59.260> hack<00:08:59.470> I 00:08:59.730 --> 00:08:59.740 align:start position:0% like the recent spank chain hack I 00:08:59.740 --> 00:09:01.560 align:start position:0% like the recent spank chain hack I actually<00:09:00.490> like<00:09:00.790> the<00:09:00.910> pointed<00:09:01.150> I<00:09:01.240> was<00:09:01.360> a<00:09:01.390> really 00:09:01.560 --> 00:09:01.570 align:start position:0% actually like the pointed I was a really 00:09:01.570 --> 00:09:03.540 align:start position:0% actually like the pointed I was a really cool<00:09:01.720> thing<00:09:01.780> that<00:09:01.990> they<00:09:02.320> didn't<00:09:02.590> over<00:09:03.190> exceed 00:09:03.540 --> 00:09:03.550 align:start position:0% cool thing that they didn't over exceed 00:09:03.550 --> 00:09:05.400 align:start position:0% cool thing that they didn't over exceed their<00:09:03.700> ability<00:09:04.060> to<00:09:04.090> pay<00:09:04.360> for<00:09:04.390> any<00:09:04.690> any<00:09:04.990> issues 00:09:05.400 --> 00:09:05.410 align:start position:0% their ability to pay for any any issues 00:09:05.410 --> 00:09:07.320 align:start position:0% their ability to pay for any any issues that<00:09:05.440> arise<00:09:05.770> I<00:09:06.220> don't<00:09:06.820> think<00:09:06.970> they<00:09:07.030> planned 00:09:07.320 --> 00:09:07.330 align:start position:0% that arise I don't think they planned 00:09:07.330 --> 00:09:08.700 align:start position:0% that arise I don't think they planned for<00:09:07.420> it<00:09:07.690> but<00:09:07.870> I<00:09:07.900> think<00:09:07.990> now<00:09:08.320> that<00:09:08.350> they<00:09:08.650> see 00:09:08.700 --> 00:09:08.710 align:start position:0% for it but I think now that they see 00:09:08.710 --> 00:09:10.920 align:start position:0% for it but I think now that they see that<00:09:08.890> they<00:09:09.280> understand<00:09:10.120> that<00:09:10.210> like<00:09:10.510> you<00:09:10.840> know 00:09:10.920 --> 00:09:10.930 align:start position:0% that they understand that like you know 00:09:10.930 --> 00:09:12.600 align:start position:0% that they understand that like you know this<00:09:11.110> is<00:09:11.260> all<00:09:11.350> new<00:09:11.500> technology<00:09:12.040> bad<00:09:12.400> things 00:09:12.600 --> 00:09:12.610 align:start position:0% this is all new technology bad things 00:09:12.610 --> 00:09:14.340 align:start position:0% this is all new technology bad things gonna<00:09:12.790> happen<00:09:12.850> but<00:09:13.600> as<00:09:13.690> long<00:09:13.840> as<00:09:13.900> I<00:09:14.020> keep<00:09:14.170> that 00:09:14.340 --> 00:09:14.350 align:start position:0% gonna happen but as long as I keep that 00:09:14.350 --> 00:09:16.110 align:start position:0% gonna happen but as long as I keep that expectation<00:09:15.100> below<00:09:15.310> my<00:09:15.460> risk<00:09:15.670> level 00:09:16.110 --> 00:09:16.120 align:start position:0% expectation below my risk level 00:09:16.120 --> 00:09:19.950 align:start position:0% expectation below my risk level I'll<00:09:16.720> be<00:09:16.930> fine<00:09:18.510> so<00:09:19.510> once<00:09:19.660> you<00:09:19.720> get<00:09:19.870> through 00:09:19.950 --> 00:09:19.960 align:start position:0% I'll be fine so once you get through 00:09:19.960 --> 00:09:21.090 align:start position:0% I'll be fine so once you get through that<00:09:20.050> and<00:09:20.170> everything<00:09:20.680> goes<00:09:20.800> well<00:09:20.980> on<00:09:21.010> your 00:09:21.090 --> 00:09:21.100 align:start position:0% that and everything goes well on your 00:09:21.100 --> 00:09:23.160 align:start position:0% that and everything goes well on your demos<00:09:21.460> and<00:09:21.640> everything's<00:09:22.000> happy<00:09:22.360> you're<00:09:22.930> sort 00:09:23.160 --> 00:09:23.170 align:start position:0% demos and everything's happy you're sort 00:09:23.170 --> 00:09:25.830 align:start position:0% demos and everything's happy you're sort of<00:09:23.200> in<00:09:23.350> this<00:09:23.500> release<00:09:24.040> cycle<00:09:24.460> and<00:09:24.580> now<00:09:24.700> you<00:09:25.630> let 00:09:25.830 --> 00:09:25.840 align:start position:0% of in this release cycle and now you let 00:09:25.840 --> 00:09:27.330 align:start position:0% of in this release cycle and now you let it<00:09:25.960> that<00:09:26.080> sit<00:09:26.320> out<00:09:26.470> there<00:09:26.710> in<00:09:26.830> the<00:09:26.920> world<00:09:27.070> and 00:09:27.330 --> 00:09:27.340 align:start position:0% it that sit out there in the world and 00:09:27.340 --> 00:09:29.190 align:start position:0% it that sit out there in the world and you<00:09:27.490> just<00:09:27.670> you<00:09:28.540> know<00:09:28.600> gather<00:09:28.870> use<00:09:29.080> your 00:09:29.190 --> 00:09:29.200 align:start position:0% you just you know gather use your 00:09:29.200 --> 00:09:30.690 align:start position:0% you just you know gather use your feedback<00:09:29.620> and<00:09:29.830> you<00:09:29.920> may<00:09:30.040> be<00:09:30.100> working<00:09:30.340> on<00:09:30.580> the 00:09:30.690 --> 00:09:30.700 align:start position:0% feedback and you may be working on the 00:09:30.700 --> 00:09:32.670 align:start position:0% feedback and you may be working on the next<00:09:30.880> iteration<00:09:31.030> of<00:09:31.360> the<00:09:31.420> design<00:09:31.720> but<00:09:32.500> you're 00:09:32.670 --> 00:09:32.680 align:start position:0% next iteration of the design but you're 00:09:32.680 --> 00:09:34.710 align:start position:0% next iteration of the design but you're also<00:09:32.800> maintaining<00:09:33.400> that<00:09:33.490> code<00:09:33.760> watching 00:09:34.710 --> 00:09:34.720 align:start position:0% also maintaining that code watching 00:09:34.720 --> 00:09:35.730 align:start position:0% also maintaining that code watching things<00:09:34.900> out<00:09:35.050> there<00:09:35.200> in<00:09:35.290> the<00:09:35.350> world<00:09:35.500> and 00:09:35.730 --> 00:09:35.740 align:start position:0% things out there in the world and 00:09:35.740 --> 00:09:38.190 align:start position:0% things out there in the world and understanding<00:09:36.450> you<00:09:37.450> know<00:09:37.570> what<00:09:37.840> you<00:09:37.930> want<00:09:38.110> to 00:09:38.190 --> 00:09:38.200 align:start position:0% understanding you know what you want to 00:09:38.200 --> 00:09:39.690 align:start position:0% understanding you know what you want to do<00:09:38.320> next<00:09:38.530> and<00:09:38.890> how<00:09:38.950> you're<00:09:39.250> gonna<00:09:39.310> support 00:09:39.690 --> 00:09:39.700 align:start position:0% do next and how you're gonna support 00:09:39.700 --> 00:09:41.400 align:start position:0% do next and how you're gonna support what<00:09:39.880> you<00:09:40.000> did<00:09:40.180> and<00:09:40.420> it's<00:09:40.840> very<00:09:40.990> important<00:09:41.350> to 00:09:41.400 --> 00:09:41.410 align:start position:0% what you did and it's very important to 00:09:41.410 --> 00:09:43.620 align:start position:0% what you did and it's very important to sports<00:09:41.650> what<00:09:41.860> you<00:09:41.980> did<00:09:42.160> I<00:09:42.190> think<00:09:42.580> in<00:09:43.480> this 00:09:43.620 --> 00:09:43.630 align:start position:0% sports what you did I think in this 00:09:43.630 --> 00:09:45.870 align:start position:0% sports what you did I think in this space<00:09:43.870> there's<00:09:44.170> this<00:09:44.290> idea<00:09:44.680> that<00:09:44.980> you<00:09:45.790> know 00:09:45.870 --> 00:09:45.880 align:start position:0% space there's this idea that you know 00:09:45.880 --> 00:09:47.100 align:start position:0% space there's this idea that you know once<00:09:46.060> you<00:09:46.150> release<00:09:46.390> about<00:09:46.600> the<00:09:46.660> main<00:09:46.930> that 00:09:47.100 --> 00:09:47.110 align:start position:0% once you release about the main that 00:09:47.110 --> 00:09:48.660 align:start position:0% once you release about the main that it's<00:09:47.380> all<00:09:47.500> mutable<00:09:47.920> you<00:09:48.040> can't<00:09:48.220> change<00:09:48.340> in<00:09:48.520> any 00:09:48.660 --> 00:09:48.670 align:start position:0% it's all mutable you can't change in any 00:09:48.670 --> 00:09:50.430 align:start position:0% it's all mutable you can't change in any way<00:09:48.760> there's<00:09:49.360> nothing<00:09:49.720> I<00:09:49.780> can<00:09:49.960> do<00:09:50.050> about<00:09:50.170> it 00:09:50.430 --> 00:09:50.440 align:start position:0% way there's nothing I can do about it 00:09:50.440 --> 00:09:53.130 align:start position:0% way there's nothing I can do about it after<00:09:50.710> that<00:09:50.740> point<00:09:51.040> that's<00:09:51.790> false<00:09:52.150> there<00:09:53.020> are 00:09:53.130 --> 00:09:53.140 align:start position:0% after that point that's false there are 00:09:53.140 --> 00:09:54.960 align:start position:0% after that point that's false there are things<00:09:53.440> you<00:09:53.560> can<00:09:53.710> do<00:09:53.890> in<00:09:54.160> order<00:09:54.370> to<00:09:54.430> respond<00:09:54.850> to 00:09:54.960 --> 00:09:54.970 align:start position:0% things you can do in order to respond to 00:09:54.970 --> 00:09:56.850 align:start position:0% things you can do in order to respond to react<00:09:55.180> to<00:09:55.210> events<00:09:55.480> it<00:09:56.200> may<00:09:56.320> not<00:09:56.530> be<00:09:56.620> with<00:09:56.800> that 00:09:56.850 --> 00:09:56.860 align:start position:0% react to events it may not be with that 00:09:56.860 --> 00:09:58.950 align:start position:0% react to events it may not be with that smart<00:09:57.130> contract<00:09:57.520> itself<00:09:57.850> but<00:09:58.570> having<00:09:58.840> an 00:09:58.950 --> 00:09:58.960 align:start position:0% smart contract itself but having an 00:09:58.960 --> 00:10:00.750 align:start position:0% smart contract itself but having an accurate<00:09:59.110> plan<00:09:59.590> beforehand<00:10:00.370> of<00:10:00.490> what<00:10:00.640> you're 00:10:00.750 --> 00:10:00.760 align:start position:0% accurate plan beforehand of what you're 00:10:00.760 --> 00:10:04.170 align:start position:0% accurate plan beforehand of what you're going<00:10:00.970> to<00:10:01.090> do<00:10:01.270> I<00:10:01.800> following<00:10:02.800> any<00:10:03.070> sort<00:10:03.340> of<00:10:03.370> hack 00:10:04.170 --> 00:10:04.180 align:start position:0% going to do I following any sort of hack 00:10:04.180 --> 00:10:06.720 align:start position:0% going to do I following any sort of hack like<00:10:04.450> you<00:10:05.140> know<00:10:05.230> build<00:10:06.130> a<00:10:06.250> whole<00:10:06.370> new<00:10:06.400> token 00:10:06.720 --> 00:10:06.730 align:start position:0% like you know build a whole new token 00:10:06.730 --> 00:10:08.070 align:start position:0% like you know build a whole new token contract<00:10:07.270> and<00:10:07.420> poured<00:10:07.600> all<00:10:07.690> the<00:10:07.720> token 00:10:08.070 --> 00:10:08.080 align:start position:0% contract and poured all the token 00:10:08.080 --> 00:10:10.020 align:start position:0% contract and poured all the token balances<00:10:08.470> over<00:10:08.770> just<00:10:09.490> have<00:10:09.640> a<00:10:09.700> really<00:10:09.850> good 00:10:10.020 --> 00:10:10.030 align:start position:0% balances over just have a really good 00:10:10.030 --> 00:10:11.190 align:start position:0% balances over just have a really good plan<00:10:10.180> of<00:10:10.450> how<00:10:10.510> you're<00:10:10.660> gonna<00:10:10.720> handle<00:10:10.930> most 00:10:11.190 --> 00:10:11.200 align:start position:0% plan of how you're gonna handle most 00:10:11.200 --> 00:10:14.490 align:start position:0% plan of how you're gonna handle most situation<00:10:11.740> that<00:10:11.890> you<00:10:12.010> think<00:10:12.190> will<00:10:12.370> arise<00:10:13.500> and 00:10:14.490 --> 00:10:14.500 align:start position:0% situation that you think will arise and 00:10:14.500 --> 00:10:19.020 align:start position:0% situation that you think will arise and then<00:10:14.680> you<00:10:14.770> get<00:10:14.890> Lambos<00:10:15.220> of<00:10:15.370> course<00:10:17.520> so<00:10:18.520> a 00:10:19.020 --> 00:10:19.030 align:start position:0% then you get Lambos of course so a 00:10:19.030 --> 00:10:22.170 align:start position:0% then you get Lambos of course so a little<00:10:19.360> bit<00:10:19.480> requirements<00:10:20.380> so<00:10:20.670> this<00:10:21.670> this<00:10:22.000> was 00:10:22.170 --> 00:10:22.180 align:start position:0% little bit requirements so this this was 00:10:22.180 --> 00:10:24.110 align:start position:0% little bit requirements so this this was pain<00:10:22.420> for<00:10:22.660> me<00:10:22.780> for<00:10:23.020> like<00:10:23.230> five<00:10:23.290> years<00:10:23.800> but 00:10:24.110 --> 00:10:24.120 align:start position:0% pain for me for like five years but 00:10:24.120 --> 00:10:26.910 align:start position:0% pain for me for like five years but there's<00:10:25.120> a<00:10:25.180> lot<00:10:25.300> of<00:10:25.450> truth<00:10:25.570> in<00:10:25.810> this<00:10:26.200> defining 00:10:26.910 --> 00:10:26.920 align:start position:0% there's a lot of truth in this defining 00:10:26.920 --> 00:10:29.520 align:start position:0% there's a lot of truth in this defining good<00:10:27.010> requirements<00:10:27.550> is<00:10:27.640> really<00:10:27.940> an<00:10:28.270> art<00:10:28.530> and 00:10:29.520 --> 00:10:29.530 align:start position:0% good requirements is really an art and 00:10:29.530 --> 00:10:31.470 align:start position:0% good requirements is really an art and it<00:10:29.620> helps<00:10:29.890> your<00:10:30.520> testers<00:10:30.970> your<00:10:31.150> your 00:10:31.470 --> 00:10:31.480 align:start position:0% it helps your testers your your 00:10:31.480 --> 00:10:33.540 align:start position:0% it helps your testers your your implementers<00:10:31.990> your<00:10:32.260> coders<00:10:32.620> everyone<00:10:33.490> to 00:10:33.540 --> 00:10:33.550 align:start position:0% implementers your coders everyone to 00:10:33.550 --> 00:10:34.830 align:start position:0% implementers your coders everyone to understand<00:10:33.910> what<00:10:34.000> the<00:10:34.090> process<00:10:34.270> is<00:10:34.570> very 00:10:34.830 --> 00:10:34.840 align:start position:0% understand what the process is very 00:10:34.840 --> 00:10:36.630 align:start position:0% understand what the process is very succinctly<00:10:35.260> and<00:10:35.500> very<00:10:35.650> well 00:10:36.630 --> 00:10:36.640 align:start position:0% succinctly and very well 00:10:36.640 --> 00:10:38.160 align:start position:0% succinctly and very well so<00:10:36.970> there's<00:10:37.150> five<00:10:37.360> aspects<00:10:37.840> of<00:10:37.990> good 00:10:38.160 --> 00:10:38.170 align:start position:0% so there's five aspects of good 00:10:38.170 --> 00:10:40.860 align:start position:0% so there's five aspects of good requirements<00:10:38.830> they<00:10:39.340> are<00:10:39.520> smart<00:10:40.030> quote 00:10:40.860 --> 00:10:40.870 align:start position:0% requirements they are smart quote 00:10:40.870 --> 00:10:44.940 align:start position:0% requirements they are smart quote unquote<00:10:41.400> so<00:10:42.900> specific<00:10:43.900> means<00:10:44.080> each 00:10:44.940 --> 00:10:44.950 align:start position:0% unquote so specific means each 00:10:44.950 --> 00:10:46.770 align:start position:0% unquote so specific means each requirement<00:10:45.520> decides<00:10:46.030> a<00:10:46.240> very<00:10:46.510> specific 00:10:46.770 --> 00:10:46.780 align:start position:0% requirement decides a very specific 00:10:46.780 --> 00:10:49.230 align:start position:0% requirement decides a very specific logical<00:10:47.410> functionality<00:10:47.980> and<00:10:48.160> it<00:10:48.940> should<00:10:49.180> be 00:10:49.230 --> 00:10:49.240 align:start position:0% logical functionality and it should be 00:10:49.240 --> 00:10:52.770 align:start position:0% logical functionality and it should be unique<00:10:49.600> to<00:10:49.630> what<00:10:49.930> is<00:10:50.050> describing<00:10:51.780> measurable 00:10:52.770 --> 00:10:52.780 align:start position:0% unique to what is describing measurable 00:10:52.780 --> 00:10:54.780 align:start position:0% unique to what is describing measurable means<00:10:52.990> that<00:10:53.320> it<00:10:53.560> should<00:10:53.830> be<00:10:53.950> quantitatively 00:10:54.780 --> 00:10:54.790 align:start position:0% means that it should be quantitatively 00:10:54.790 --> 00:10:58.710 align:start position:0% means that it should be quantitatively measurable<00:10:55.710> ie<00:10:56.710> the<00:10:57.040> you<00:10:57.700> know<00:10:57.790> the<00:10:58.090> the<00:10:58.390> token 00:10:58.710 --> 00:10:58.720 align:start position:0% measurable ie the you know the the token 00:10:58.720 --> 00:10:59.970 align:start position:0% measurable ie the you know the the token shall<00:10:58.900> be<00:10:58.990> transferable<00:10:59.530> only<00:10:59.770> if<00:10:59.860> the 00:10:59.970 --> 00:10:59.980 align:start position:0% shall be transferable only if the 00:10:59.980 --> 00:11:01.470 align:start position:0% shall be transferable only if the balance<00:11:00.220> meets<00:11:00.430> or<00:11:00.550> exceeds<00:11:00.580> this<00:11:01.240> amount 00:11:01.470 --> 00:11:01.480 align:start position:0% balance meets or exceeds this amount 00:11:01.480 --> 00:11:03.059 align:start position:0% balance meets or exceeds this amount blah<00:11:01.720> blah<00:11:01.840> blah 00:11:03.059 --> 00:11:03.069 align:start position:0% blah blah blah 00:11:03.069 --> 00:11:06.699 align:start position:0% blah blah blah they<00:11:04.069> should<00:11:04.220> be<00:11:04.309> attainable<00:11:04.759> I<00:11:05.709> describe 00:11:06.699 --> 00:11:06.709 align:start position:0% they should be attainable I describe 00:11:06.709 --> 00:11:08.290 align:start position:0% they should be attainable I describe functionality<00:11:07.579> that<00:11:07.730> the<00:11:07.850> software<00:11:08.180> can 00:11:08.290 --> 00:11:08.300 align:start position:0% functionality that the software can 00:11:08.300 --> 00:11:10.239 align:start position:0% functionality that the software can actually<00:11:08.749> implement<00:11:08.990> not<00:11:09.769> something<00:11:10.160> like 00:11:10.239 --> 00:11:10.249 align:start position:0% actually implement not something like 00:11:10.249 --> 00:11:13.090 align:start position:0% actually implement not something like the<00:11:10.399> economics<00:11:11.029> of<00:11:11.209> the<00:11:11.540> platform<00:11:12.019> or<00:11:12.259> some 00:11:13.090 --> 00:11:13.100 align:start position:0% the economics of the platform or some 00:11:13.100 --> 00:11:15.720 align:start position:0% the economics of the platform or some sort<00:11:13.490> of<00:11:13.550> loose<00:11:13.819> UX<00:11:14.809> experience<00:11:14.990> that's 00:11:15.720 --> 00:11:15.730 align:start position:0% sort of loose UX experience that's 00:11:15.730 --> 00:11:17.859 align:start position:0% sort of loose UX experience that's desired<00:11:16.730> it<00:11:17.029> should<00:11:17.269> be<00:11:17.360> really<00:11:17.629> tightly 00:11:17.859 --> 00:11:17.869 align:start position:0% desired it should be really tightly 00:11:17.869 --> 00:11:19.150 align:start position:0% desired it should be really tightly coupled<00:11:18.170> to<00:11:18.379> something<00:11:18.709> that's<00:11:18.829> achievable 00:11:19.150 --> 00:11:19.160 align:start position:0% coupled to something that's achievable 00:11:19.160 --> 00:11:22.900 align:start position:0% coupled to something that's achievable and<00:11:19.429> practice<00:11:21.249> relevant<00:11:22.249> kind<00:11:22.429> of<00:11:22.519> describes 00:11:22.900 --> 00:11:22.910 align:start position:0% and practice relevant kind of describes 00:11:22.910 --> 00:11:24.879 align:start position:0% and practice relevant kind of describes that<00:11:23.059> same<00:11:23.329> thing<00:11:23.600> not<00:11:24.410> describing 00:11:24.879 --> 00:11:24.889 align:start position:0% that same thing not describing 00:11:24.889 --> 00:11:27.040 align:start position:0% that same thing not describing extraneous<00:11:25.339> functionality<00:11:25.999> is<00:11:26.149> very<00:11:26.240> it's 00:11:27.040 --> 00:11:27.050 align:start position:0% extraneous functionality is very it's 00:11:27.050 --> 00:11:29.019 align:start position:0% extraneous functionality is very it's all<00:11:27.230> very<00:11:27.470> core<00:11:27.860> to<00:11:28.009> the<00:11:28.100> application<00:11:28.790> and 00:11:29.019 --> 00:11:29.029 align:start position:0% all very core to the application and 00:11:29.029 --> 00:11:30.850 align:start position:0% all very core to the application and isn't<00:11:29.689> kind<00:11:29.839> of<00:11:29.959> outside<00:11:30.350> the<00:11:30.499> realm<00:11:30.679> of<00:11:30.800> what 00:11:30.850 --> 00:11:30.860 align:start position:0% isn't kind of outside the realm of what 00:11:30.860 --> 00:11:33.160 align:start position:0% isn't kind of outside the realm of what you<00:11:31.040> can<00:11:31.189> do<00:11:31.339> with<00:11:31.490> the<00:11:31.579> software<00:11:32.170> and 00:11:33.160 --> 00:11:33.170 align:start position:0% you can do with the software and 00:11:33.170 --> 00:11:35.259 align:start position:0% you can do with the software and time-bound<00:11:33.740> is<00:11:33.980> last<00:11:34.249> it<00:11:34.910> basically 00:11:35.259 --> 00:11:35.269 align:start position:0% time-bound is last it basically 00:11:35.269 --> 00:11:37.480 align:start position:0% time-bound is last it basically describes<00:11:35.629> things<00:11:35.839> that<00:11:36.170> are<00:11:36.470> like<00:11:37.100> very 00:11:37.480 --> 00:11:37.490 align:start position:0% describes things that are like very 00:11:37.490 --> 00:11:39.669 align:start position:0% describes things that are like very specific<00:11:37.999> in<00:11:38.119> time<00:11:38.389> they<00:11:38.990> shouldn't<00:11:39.379> be<00:11:39.470> like 00:11:39.669 --> 00:11:39.679 align:start position:0% specific in time they shouldn't be like 00:11:39.679 --> 00:11:41.499 align:start position:0% specific in time they shouldn't be like oh<00:11:39.889> well<00:11:40.189> eventually<00:11:40.759> it's<00:11:40.939> going<00:11:41.089> to<00:11:41.179> do<00:11:41.360> this 00:11:41.499 --> 00:11:41.509 align:start position:0% oh well eventually it's going to do this 00:11:41.509 --> 00:11:43.809 align:start position:0% oh well eventually it's going to do this or<00:11:41.869> you<00:11:42.559> know<00:11:42.649> at<00:11:42.829> some<00:11:43.100> time<00:11:43.429> it<00:11:43.579> should<00:11:43.759> be 00:11:43.809 --> 00:11:43.819 align:start position:0% or you know at some time it should be 00:11:43.819 --> 00:11:46.689 align:start position:0% or you know at some time it should be like<00:11:43.999> X<00:11:44.480> seconds<00:11:45.019> or<00:11:45.139> Y<00:11:45.259> seconds<00:11:45.800> or<00:11:45.949> weeks<00:11:46.459> or 00:11:46.689 --> 00:11:46.699 align:start position:0% like X seconds or Y seconds or weeks or 00:11:46.699 --> 00:11:48.400 align:start position:0% like X seconds or Y seconds or weeks or months<00:11:46.970> or<00:11:47.119> whatever<00:11:47.269> you<00:11:47.929> should<00:11:47.959> have<00:11:48.259> very 00:11:48.400 --> 00:11:48.410 align:start position:0% months or whatever you should have very 00:11:48.410 --> 00:11:50.949 align:start position:0% months or whatever you should have very tight<00:11:48.709> requirements<00:11:49.309> around<00:11:49.399> time<00:11:50.179> to<00:11:50.839> make 00:11:50.949 --> 00:11:50.959 align:start position:0% tight requirements around time to make 00:11:50.959 --> 00:11:56.590 align:start position:0% tight requirements around time to make it<00:11:51.079> easier<00:11:51.379> to<00:11:51.439> understand<00:11:55.119> so<00:11:56.119> traceability 00:11:56.590 --> 00:11:56.600 align:start position:0% it easier to understand so traceability 00:11:56.600 --> 00:11:58.499 align:start position:0% it easier to understand so traceability is<00:11:56.839> another<00:11:57.110> thing<00:11:57.319> I<00:11:57.410> think<00:11:57.559> a<00:11:57.829> lot<00:11:58.009> of<00:11:58.040> people 00:11:58.499 --> 00:11:58.509 align:start position:0% is another thing I think a lot of people 00:11:58.509 --> 00:12:01.689 align:start position:0% is another thing I think a lot of people haven't<00:11:59.509> had<00:11:59.629> a<00:11:59.689> lot<00:11:59.809> of<00:11:59.929> exposure<00:12:00.230> to<00:12:00.559> so<00:12:00.920> the 00:12:01.689 --> 00:12:01.699 align:start position:0% haven't had a lot of exposure to so the 00:12:01.699 --> 00:12:03.340 align:start position:0% haven't had a lot of exposure to so the idea<00:12:01.970> is<00:12:02.209> is<00:12:02.600> if<00:12:02.779> you<00:12:02.929> go<00:12:03.050> through<00:12:03.199> this 00:12:03.340 --> 00:12:03.350 align:start position:0% idea is is if you go through this 00:12:03.350 --> 00:12:04.749 align:start position:0% idea is is if you go through this process<00:12:03.589> and<00:12:03.980> yeah<00:12:04.100> it's<00:12:04.279> a<00:12:04.339> little<00:12:04.459> bit<00:12:04.579> more 00:12:04.749 --> 00:12:04.759 align:start position:0% process and yeah it's a little bit more 00:12:04.759 --> 00:12:07.509 align:start position:0% process and yeah it's a little bit more upfront<00:12:05.059> work<00:12:05.329> you<00:12:06.139> can<00:12:06.259> actually<00:12:06.529> use<00:12:07.309> some 00:12:07.509 --> 00:12:07.519 align:start position:0% upfront work you can actually use some 00:12:07.519 --> 00:12:10.030 align:start position:0% upfront work you can actually use some really<00:12:07.759> cool<00:12:07.910> things<00:12:08.209> to<00:12:09.019> get<00:12:09.470> a<00:12:09.529> really<00:12:09.920> good 00:12:10.030 --> 00:12:10.040 align:start position:0% really cool things to get a really good 00:12:10.040 --> 00:12:11.699 align:start position:0% really cool things to get a really good picture<00:12:10.189> of<00:12:10.459> whether<00:12:10.639> or<00:12:10.730> not<00:12:10.879> you're<00:12:11.089> done 00:12:11.699 --> 00:12:11.709 align:start position:0% picture of whether or not you're done 00:12:11.709 --> 00:12:16.150 align:start position:0% picture of whether or not you're done and<00:12:12.709> that's<00:12:12.920> pretty<00:12:13.160> cool<00:12:14.079> so<00:12:15.079> if<00:12:15.800> you<00:12:16.009> have 00:12:16.150 --> 00:12:16.160 align:start position:0% and that's pretty cool so if you have 00:12:16.160 --> 00:12:17.470 align:start position:0% and that's pretty cool so if you have the<00:12:16.279> requirements<00:12:16.850> you<00:12:16.910> kind<00:12:17.149> of<00:12:17.240> link<00:12:17.389> them 00:12:17.470 --> 00:12:17.480 align:start position:0% the requirements you kind of link them 00:12:17.480 --> 00:12:19.929 align:start position:0% the requirements you kind of link them to<00:12:17.629> these<00:12:17.749> numbers<00:12:18.139> I<00:12:18.529> had<00:12:18.949> an<00:12:19.040> idea<00:12:19.129> to<00:12:19.339> you 00:12:19.929 --> 00:12:19.939 align:start position:0% to these numbers I had an idea to you 00:12:19.939 --> 00:12:21.340 align:start position:0% to these numbers I had an idea to you know<00:12:19.970> like<00:12:20.179> hatch<00:12:20.389> the<00:12:20.569> requirement<00:12:21.050> tax<00:12:21.230> to 00:12:21.340 --> 00:12:21.350 align:start position:0% know like hatch the requirement tax to 00:12:21.350 --> 00:12:23.199 align:start position:0% know like hatch the requirement tax to have<00:12:21.439> a<00:12:21.470> unique<00:12:22.069> ID<00:12:22.279> hash<00:12:22.579> so<00:12:22.850> you<00:12:22.910> can<00:12:23.059> tell 00:12:23.199 --> 00:12:23.209 align:start position:0% have a unique ID hash so you can tell 00:12:23.209 --> 00:12:25.419 align:start position:0% have a unique ID hash so you can tell when<00:12:23.360> things<00:12:23.509> change<00:12:23.839> you<00:12:24.829> can<00:12:24.949> do<00:12:25.040> it<00:12:25.129> any<00:12:25.339> way 00:12:25.419 --> 00:12:25.429 align:start position:0% when things change you can do it any way 00:12:25.429 --> 00:12:25.929 align:start position:0% when things change you can do it any way you<00:12:25.459> want 00:12:25.929 --> 00:12:25.939 align:start position:0% you want 00:12:25.939 --> 00:12:27.669 align:start position:0% you want you<00:12:26.300> basically<00:12:26.449> link<00:12:26.870> your<00:12:26.990> requirement<00:12:27.499> to 00:12:27.669 --> 00:12:27.679 align:start position:0% you basically link your requirement to 00:12:27.679 --> 00:12:30.220 align:start position:0% you basically link your requirement to you<00:12:28.100> know<00:12:28.160> a<00:12:28.189> specific<00:12:28.670> identifier<00:12:29.179> you<00:12:30.079> might 00:12:30.220 --> 00:12:30.230 align:start position:0% you know a specific identifier you might 00:12:30.230 --> 00:12:32.860 align:start position:0% you know a specific identifier you might use<00:12:30.499> like<00:12:30.769> a<00:12:30.800> like<00:12:31.429> a<00:12:31.459> NAT<00:12:31.759> spec<00:12:31.999> comment<00:12:32.420> link 00:12:32.860 --> 00:12:32.870 align:start position:0% use like a like a NAT spec comment link 00:12:32.870 --> 00:12:34.600 align:start position:0% use like a like a NAT spec comment link in<00:12:33.019> your<00:12:33.079> code<00:12:33.319> be<00:12:33.559> like<00:12:33.709> hey<00:12:33.889> this<00:12:34.069> implements 00:12:34.600 --> 00:12:34.610 align:start position:0% in your code be like hey this implements 00:12:34.610 --> 00:12:36.460 align:start position:0% in your code be like hey this implements requirement<00:12:35.480> number<00:12:35.629> one<00:12:35.839> or<00:12:36.079> something<00:12:36.350> like 00:12:36.460 --> 00:12:36.470 align:start position:0% requirement number one or something like 00:12:36.470 --> 00:12:38.259 align:start position:0% requirement number one or something like that<00:12:36.529> and<00:12:36.920> the<00:12:37.579> same<00:12:37.730> thing<00:12:37.879> in<00:12:37.970> your<00:12:38.059> test 00:12:38.259 --> 00:12:38.269 align:start position:0% that and the same thing in your test 00:12:38.269 --> 00:12:40.720 align:start position:0% that and the same thing in your test case<00:12:38.449> you<00:12:38.720> you<00:12:39.079> know<00:12:39.199> use<00:12:39.470> Nats<00:12:40.129> textile 00:12:40.720 --> 00:12:40.730 align:start position:0% case you you know use Nats textile 00:12:40.730 --> 00:12:42.790 align:start position:0% case you you know use Nats textile comments<00:12:41.240> in<00:12:41.329> your<00:12:41.420> test<00:12:41.660> cases<00:12:41.839> and<00:12:42.230> then 00:12:42.790 --> 00:12:42.800 align:start position:0% comments in your test cases and then 00:12:42.800 --> 00:12:44.410 align:start position:0% comments in your test cases and then once<00:12:43.339> you<00:12:43.459> have<00:12:43.610> all<00:12:43.730> these<00:12:43.879> things<00:12:44.120> in<00:12:44.300> place 00:12:44.410 --> 00:12:44.420 align:start position:0% once you have all these things in place 00:12:44.420 --> 00:12:46.119 align:start position:0% once you have all these things in place we<00:12:44.720> can<00:12:44.839> build<00:12:44.959> tools<00:12:45.170> that<00:12:45.499> link<00:12:45.980> it<00:12:46.040> all 00:12:46.119 --> 00:12:46.129 align:start position:0% we can build tools that link it all 00:12:46.129 --> 00:12:47.410 align:start position:0% we can build tools that link it all together<00:12:46.309> and<00:12:46.610> you<00:12:46.699> can<00:12:46.819> get<00:12:46.939> a<00:12:46.970> really<00:12:47.179> full 00:12:47.410 --> 00:12:47.420 align:start position:0% together and you can get a really full 00:12:47.420 --> 00:12:48.970 align:start position:0% together and you can get a really full picture<00:12:47.660> of<00:12:48.019> your<00:12:48.470> entire<00:12:48.709> application 00:12:48.970 --> 00:12:48.980 align:start position:0% picture of your entire application 00:12:48.980 --> 00:12:50.499 align:start position:0% picture of your entire application linking<00:12:49.790> all<00:12:49.910> the<00:12:49.999> way<00:12:50.059> back<00:12:50.240> to<00:12:50.420> the 00:12:50.499 --> 00:12:50.509 align:start position:0% linking all the way back to the 00:12:50.509 --> 00:12:52.600 align:start position:0% linking all the way back to the specification<00:12:51.259> the<00:12:51.740> human<00:12:52.069> readable<00:12:52.249> thing 00:12:52.600 --> 00:12:52.610 align:start position:0% specification the human readable thing 00:12:52.610 --> 00:12:53.980 align:start position:0% specification the human readable thing that<00:12:52.759> you<00:12:52.850> guys<00:12:52.999> all<00:12:53.240> agreed<00:12:53.509> on<00:12:53.660> before<00:12:53.839> you 00:12:53.980 --> 00:12:53.990 align:start position:0% that you guys all agreed on before you 00:12:53.990 --> 00:12:55.960 align:start position:0% that you guys all agreed on before you started<00:12:54.259> the<00:12:54.319> project<00:12:54.499> by<00:12:55.370> using<00:12:55.579> tools<00:12:55.879> like 00:12:55.960 --> 00:12:55.970 align:start position:0% started the project by using tools like 00:12:55.970 --> 00:12:57.910 align:start position:0% started the project by using tools like this<00:12:56.269> and<00:12:56.569> you<00:12:56.689> can<00:12:56.839> you<00:12:57.049> can<00:12:57.079> identify<00:12:57.379> holes 00:12:57.910 --> 00:12:57.920 align:start position:0% this and you can you can identify holes 00:12:57.920 --> 00:13:00.429 align:start position:0% this and you can you can identify holes in<00:12:58.220> the<00:12:58.309> approach<00:12:58.579> you<00:12:59.299> can<00:12:59.420> look<00:12:59.600> for<00:12:59.839> places 00:13:00.429 --> 00:13:00.439 align:start position:0% in the approach you can look for places 00:13:00.439 --> 00:13:02.289 align:start position:0% in the approach you can look for places that<00:13:00.799> things<00:13:01.579> weren't<00:13:01.790> implemented 00:13:02.289 --> 00:13:02.299 align:start position:0% that things weren't implemented 00:13:02.299 --> 00:13:04.509 align:start position:0% that things weren't implemented correctly<00:13:02.420> or<00:13:02.779> missing<00:13:03.290> and<00:13:03.529> make<00:13:04.160> sure<00:13:04.309> that 00:13:04.509 --> 00:13:04.519 align:start position:0% correctly or missing and make sure that 00:13:04.519 --> 00:13:06.129 align:start position:0% correctly or missing and make sure that you<00:13:04.670> guys<00:13:04.850> are<00:13:04.999> like<00:13:05.119> truly<00:13:05.569> done<00:13:05.779> with<00:13:06.019> your 00:13:06.129 --> 00:13:06.139 align:start position:0% you guys are like truly done with your 00:13:06.139 --> 00:13:07.419 align:start position:0% you guys are like truly done with your application<00:13:06.649> before<00:13:06.799> you're<00:13:07.069> ready<00:13:07.220> for<00:13:07.339> the 00:13:07.419 --> 00:13:07.429 align:start position:0% application before you're ready for the 00:13:07.429 --> 00:13:09.309 align:start position:0% application before you're ready for the next<00:13:07.459> step<00:13:07.910> if<00:13:08.569> you<00:13:08.749> bring<00:13:08.899> this<00:13:09.049> to<00:13:09.230> an 00:13:09.309 --> 00:13:09.319 align:start position:0% next step if you bring this to an 00:13:09.319 --> 00:13:10.989 align:start position:0% next step if you bring this to an auditor<00:13:09.679> your<00:13:09.889> honor<00:13:10.040> it<00:13:10.189> would<00:13:10.429> be<00:13:10.579> like<00:13:10.819> half 00:13:10.989 --> 00:13:10.999 align:start position:0% auditor your honor it would be like half 00:13:10.999 --> 00:13:12.789 align:start position:0% auditor your honor it would be like half the<00:13:11.149> cost<00:13:11.360> no<00:13:12.290> joke 00:13:12.789 --> 00:13:12.799 align:start position:0% the cost no joke 00:13:12.799 --> 00:13:14.739 align:start position:0% the cost no joke when<00:13:13.639> I<00:13:13.730> was<00:13:13.850> shopping<00:13:14.029> around<00:13:14.149> for<00:13:14.449> audits 00:13:14.739 --> 00:13:14.749 align:start position:0% when I was shopping around for audits 00:13:14.749 --> 00:13:16.600 align:start position:0% when I was shopping around for audits all<00:13:15.559> the<00:13:15.740> auditors<00:13:16.069> were<00:13:16.189> really 00:13:16.600 --> 00:13:16.610 align:start position:0% all the auditors were really 00:13:16.610 --> 00:13:17.800 align:start position:0% all the auditors were really prai's<00:13:16.760> that<00:13:17.000> I<00:13:17.060> was<00:13:17.209> doing<00:13:17.450> this<00:13:17.570> in<00:13:17.720> my 00:13:17.800 --> 00:13:17.810 align:start position:0% prai's that I was doing this in my 00:13:17.810 --> 00:13:24.490 align:start position:0% prai's that I was doing this in my application<00:13:21.339> okay<00:13:22.339> so<00:13:23.029> I'm<00:13:23.540> Creole<00:13:23.899> and<00:13:24.200> I 00:13:24.490 --> 00:13:24.500 align:start position:0% application okay so I'm Creole and I 00:13:24.500 --> 00:13:26.730 align:start position:0% application okay so I'm Creole and I will<00:13:24.649> be<00:13:24.800> more<00:13:25.100> pragmatic<00:13:25.310> part<00:13:25.940> of<00:13:26.089> this<00:13:26.149> talk 00:13:26.730 --> 00:13:26.740 align:start position:0% will be more pragmatic part of this talk 00:13:26.740 --> 00:13:29.110 align:start position:0% will be more pragmatic part of this talk pragmatic<00:13:27.740> enough<00:13:28.100> that<00:13:28.430> you<00:13:28.550> will<00:13:28.670> feel<00:13:28.880> like 00:13:29.110 --> 00:13:29.120 align:start position:0% pragmatic enough that you will feel like 00:13:29.120 --> 00:13:31.449 align:start position:0% pragmatic enough that you will feel like a<00:13:29.180> motivational<00:13:30.079> speaker<00:13:30.320> not<00:13:30.620> some<00:13:31.070> sort<00:13:31.310> of 00:13:31.449 --> 00:13:31.459 align:start position:0% a motivational speaker not some sort of 00:13:31.459 --> 00:13:33.940 align:start position:0% a motivational speaker not some sort of the<00:13:31.610> engineer<00:13:32.120> and<00:13:32.269> this<00:13:33.170> first<00:13:33.440> thing<00:13:33.680> I'm 00:13:33.940 --> 00:13:33.950 align:start position:0% the engineer and this first thing I'm 00:13:33.950 --> 00:13:35.940 align:start position:0% the engineer and this first thing I'm going<00:13:34.100> to<00:13:34.220> talk<00:13:34.370> to<00:13:35.060> you<00:13:35.180> about<00:13:35.300> is 00:13:35.940 --> 00:13:35.950 align:start position:0% going to talk to you about is 00:13:35.950 --> 00:13:38.620 align:start position:0% going to talk to you about is test-driven<00:13:36.950> development<00:13:37.250> because<00:13:38.089> everyone 00:13:38.620 --> 00:13:38.630 align:start position:0% test-driven development because everyone 00:13:38.630 --> 00:13:40.120 align:start position:0% test-driven development because everyone knows<00:13:38.839> that<00:13:38.870> you<00:13:39.290> probably<00:13:39.649> should<00:13:39.950> be<00:13:40.100> doing 00:13:40.120 --> 00:13:40.130 align:start position:0% knows that you probably should be doing 00:13:40.130 --> 00:13:42.970 align:start position:0% knows that you probably should be doing the<00:13:40.459> ads<00:13:40.579> no<00:13:41.390> one<00:13:41.540> understands<00:13:42.019> why<00:13:42.230> like<00:13:42.950> I 00:13:42.970 --> 00:13:42.980 align:start position:0% the ads no one understands why like I 00:13:42.980 --> 00:13:44.670 align:start position:0% the ads no one understands why like I was<00:13:43.160> like<00:13:43.250> I<00:13:43.399> asked<00:13:43.700> and<00:13:44.089> people<00:13:44.510> to<00:13:44.600> earn 00:13:44.670 --> 00:13:44.680 align:start position:0% was like I asked and people to earn 00:13:44.680 --> 00:13:48.100 align:start position:0% was like I asked and people to earn because<00:13:45.680> I<00:13:45.890> need<00:13:46.339> 100%<00:13:47.240> coverage<00:13:47.630> or 00:13:48.100 --> 00:13:48.110 align:start position:0% because I need 100% coverage or 00:13:48.110 --> 00:13:49.990 align:start position:0% because I need 100% coverage or something<00:13:48.440> like<00:13:48.529> that 00:13:49.990 --> 00:13:50.000 align:start position:0% something like that 00:13:50.000 --> 00:13:53.410 align:start position:0% something like that the<00:13:50.300> actual<00:13:50.750> answer<00:13:51.200> is<00:13:51.410> that<00:13:52.339> your<00:13:52.820> tests<00:13:53.300> a 00:13:53.410 --> 00:13:53.420 align:start position:0% the actual answer is that your tests a 00:13:53.420 --> 00:13:56.980 align:start position:0% the actual answer is that your tests a code<00:13:53.779> and<00:13:54.579> you<00:13:55.579> need<00:13:55.820> to<00:13:55.970> verify<00:13:56.209> that<00:13:56.690> your 00:13:56.980 --> 00:13:56.990 align:start position:0% code and you need to verify that your 00:13:56.990 --> 00:13:59.650 align:start position:0% code and you need to verify that your test<00:13:57.230> code<00:13:58.010> is<00:13:58.339> working<00:13:58.670> as<00:13:59.000> you<00:13:59.149> expect<00:13:59.510> them 00:13:59.650 --> 00:13:59.660 align:start position:0% test code is working as you expect them 00:13:59.660 --> 00:14:03.250 align:start position:0% test code is working as you expect them to<00:13:59.690> do<00:13:59.899> and<00:14:00.170> you<00:14:01.510> I'm<00:14:02.510> not<00:14:02.690> suggesting<00:14:02.870> you 00:14:03.250 --> 00:14:03.260 align:start position:0% to do and you I'm not suggesting you 00:14:03.260 --> 00:14:05.290 align:start position:0% to do and you I'm not suggesting you writing<00:14:03.589> tests<00:14:03.860> for<00:14:04.040> your<00:14:04.100> tests<00:14:04.310> right<00:14:04.519> so 00:14:05.290 --> 00:14:05.300 align:start position:0% writing tests for your tests right so 00:14:05.300 --> 00:14:07.150 align:start position:0% writing tests for your tests right so the<00:14:05.480> only<00:14:05.510> way<00:14:06.019> you<00:14:06.079> verify<00:14:06.620> that<00:14:06.649> you<00:14:06.920> test 00:14:07.150 --> 00:14:07.160 align:start position:0% the only way you verify that you test 00:14:07.160 --> 00:14:09.250 align:start position:0% the only way you verify that you test check<00:14:07.579> something<00:14:08.060> and<00:14:08.240> it's<00:14:08.360> not<00:14:08.540> like<00:14:08.779> one 00:14:09.250 --> 00:14:09.260 align:start position:0% check something and it's not like one 00:14:09.260 --> 00:14:12.250 align:start position:0% check something and it's not like one equals<00:14:09.680> one<00:14:09.890> in<00:14:10.339> the<00:14:10.550> end<00:14:10.700> is<00:14:10.880> that<00:14:11.510> you<00:14:12.050> write 00:14:12.250 --> 00:14:12.260 align:start position:0% equals one in the end is that you write 00:14:12.260 --> 00:14:14.920 align:start position:0% equals one in the end is that you write tests<00:14:12.560> first<00:14:12.829> and<00:14:13.250> they<00:14:13.459> fail<00:14:13.730> and<00:14:14.089> then<00:14:14.779> they 00:14:14.920 --> 00:14:14.930 align:start position:0% tests first and they fail and then they 00:14:14.930 --> 00:14:16.930 align:start position:0% tests first and they fail and then they fail<00:14:15.170> your<00:14:15.380> ad<00:14:15.500> code<00:14:15.860> and<00:14:16.100> then<00:14:16.220> they<00:14:16.399> pass<00:14:16.640> and 00:14:16.930 --> 00:14:16.940 align:start position:0% fail your ad code and then they pass and 00:14:16.940 --> 00:14:18.340 align:start position:0% fail your ad code and then they pass and that<00:14:17.240> means<00:14:17.450> that<00:14:17.630> your<00:14:17.810> tests<00:14:18.110> are<00:14:18.170> actually 00:14:18.340 --> 00:14:18.350 align:start position:0% that means that your tests are actually 00:14:18.350 --> 00:14:20.500 align:start position:0% that means that your tests are actually checking<00:14:19.220> the<00:14:19.370> behavior<00:14:19.850> which<00:14:20.089> you<00:14:20.240> just 00:14:20.500 --> 00:14:20.510 align:start position:0% checking the behavior which you just 00:14:20.510 --> 00:14:24.639 align:start position:0% checking the behavior which you just implemented<00:14:21.380> in<00:14:21.470> your<00:14:21.560> program<00:14:23.170> also<00:14:24.170> I 00:14:24.639 --> 00:14:24.649 align:start position:0% implemented in your program also I 00:14:24.649 --> 00:14:26.680 align:start position:0% implemented in your program also I promise<00:14:25.100> to<00:14:25.190> be<00:14:25.279> problematic<00:14:25.610> no<00:14:26.420> one<00:14:26.570> is 00:14:26.680 --> 00:14:26.690 align:start position:0% promise to be problematic no one is 00:14:26.690 --> 00:14:28.540 align:start position:0% promise to be problematic no one is going<00:14:26.810> to<00:14:26.930> do<00:14:27.110> that<00:14:27.290> all<00:14:27.410> the<00:14:27.440> time<00:14:27.560> this<00:14:28.399> is 00:14:28.540 --> 00:14:28.550 align:start position:0% going to do that all the time this is 00:14:28.550 --> 00:14:30.220 align:start position:0% going to do that all the time this is like<00:14:28.730> true<00:14:29.089> of<00:14:29.269> rust<00:14:29.480> where<00:14:29.660> engineering 00:14:30.220 --> 00:14:30.230 align:start position:0% like true of rust where engineering 00:14:30.230 --> 00:14:32.710 align:start position:0% like true of rust where engineering no<00:14:30.350> one<00:14:30.500> is<00:14:30.620> writing<00:14:30.949> tests<00:14:31.160> first<00:14:31.370> so<00:14:32.300> what 00:14:32.710 --> 00:14:32.720 align:start position:0% no one is writing tests first so what 00:14:32.720 --> 00:14:34.660 align:start position:0% no one is writing tests first so what I'm<00:14:32.899> suggesting<00:14:33.079> for<00:14:33.589> the<00:14:33.709> existing<00:14:34.190> systems 00:14:34.660 --> 00:14:34.670 align:start position:0% I'm suggesting for the existing systems 00:14:34.670 --> 00:14:37.030 align:start position:0% I'm suggesting for the existing systems systems<00:14:35.269> weren't<00:14:35.600> written<00:14:36.320> right<00:14:36.529> now<00:14:36.589> by<00:14:36.980> you 00:14:37.030 --> 00:14:37.040 align:start position:0% systems weren't written right now by you 00:14:37.040 --> 00:14:39.910 align:start position:0% systems weren't written right now by you and<00:14:37.519> you<00:14:38.240> have<00:14:38.420> to<00:14:38.449> write<00:14:38.810> tests<00:14:39.050> for<00:14:39.140> it<00:14:39.320> just 00:14:39.910 --> 00:14:39.920 align:start position:0% and you have to write tests for it just 00:14:39.920 --> 00:14:42.340 align:start position:0% and you have to write tests for it just try<00:14:40.190> to<00:14:40.250> break<00:14:40.850> your<00:14:41.089> test<00:14:41.390> by<00:14:41.720> modifying<00:14:42.110> your 00:14:42.340 --> 00:14:42.350 align:start position:0% try to break your test by modifying your 00:14:42.350 --> 00:14:44.710 align:start position:0% try to break your test by modifying your code<00:14:42.529> just<00:14:42.800> introduce<00:14:43.670> miles<00:14:44.000> sounds<00:14:44.480> small 00:14:44.710 --> 00:14:44.720 align:start position:0% code just introduce miles sounds small 00:14:44.720 --> 00:14:47.560 align:start position:0% code just introduce miles sounds small error<00:14:44.990> and<00:14:45.320> make<00:14:45.740> sure<00:14:45.949> you<00:14:46.160> test<00:14:46.399> go<00:14:46.670> read<00:14:46.910> if 00:14:47.560 --> 00:14:47.570 align:start position:0% error and make sure you test go read if 00:14:47.570 --> 00:14:49.870 align:start position:0% error and make sure you test go read if it<00:14:47.750> happens<00:14:48.079> yeah<00:14:48.230> this<00:14:48.500> test<00:14:48.769> is<00:14:48.949> useful<00:14:49.130> this 00:14:49.870 --> 00:14:49.880 align:start position:0% it happens yeah this test is useful this 00:14:49.880 --> 00:14:51.699 align:start position:0% it happens yeah this test is useful this test<00:14:50.180> is<00:14:50.329> testing<00:14:50.630> what<00:14:51.079> it's<00:14:51.230> supposed<00:14:51.589> to 00:14:51.699 --> 00:14:51.709 align:start position:0% test is testing what it's supposed to 00:14:51.709 --> 00:14:53.650 align:start position:0% test is testing what it's supposed to and<00:14:51.920> there<00:14:52.250> is<00:14:52.339> no<00:14:52.459> subtool<00:14:52.910> syntactic 00:14:53.650 --> 00:14:53.660 align:start position:0% and there is no subtool syntactic 00:14:53.660 --> 00:14:56.230 align:start position:0% and there is no subtool syntactic mistakes<00:14:53.990> in<00:14:54.140> there<00:14:54.399> another<00:14:55.399> like<00:14:55.730> being 00:14:56.230 --> 00:14:56.240 align:start position:0% mistakes in there another like being 00:14:56.240 --> 00:14:59.290 align:start position:0% mistakes in there another like being more<00:14:56.990> to<00:14:57.320> the<00:14:57.470> solidity<00:14:57.920> testing<00:14:58.399> i<00:14:58.610> recommend 00:14:59.290 --> 00:14:59.300 align:start position:0% more to the solidity testing i recommend 00:14:59.300 --> 00:15:01.689 align:start position:0% more to the solidity testing i recommend testing<00:14:59.570> solidity<00:15:00.529> in<00:15:00.709> javascript<00:15:01.279> because 00:15:01.689 --> 00:15:01.699 align:start position:0% testing solidity in javascript because 00:15:01.699 --> 00:15:04.990 align:start position:0% testing solidity in javascript because then<00:15:02.120> small<00:15:02.860> syntactic<00:15:04.000> misunderstandings 00:15:04.990 --> 00:15:05.000 align:start position:0% then small syntactic misunderstandings 00:15:05.000 --> 00:15:06.939 align:start position:0% then small syntactic misunderstandings between<00:15:05.120> you<00:15:05.480> in<00:15:05.600> solidity<00:15:05.959> won't<00:15:06.410> get<00:15:06.620> in<00:15:06.829> a 00:15:06.939 --> 00:15:06.949 align:start position:0% between you in solidity won't get in a 00:15:06.949 --> 00:15:09.069 align:start position:0% between you in solidity won't get in a place<00:15:07.190> so<00:15:07.730> you<00:15:08.000> basically<00:15:08.209> won't<00:15:08.690> repeat<00:15:08.930> the 00:15:09.069 --> 00:15:09.079 align:start position:0% place so you basically won't repeat the 00:15:09.079 --> 00:15:11.259 align:start position:0% place so you basically won't repeat the same<00:15:09.290> error<00:15:09.560> on<00:15:09.890> your<00:15:09.949> testing<00:15:10.820> side<00:15:11.000> of<00:15:11.180> the 00:15:11.259 --> 00:15:11.269 align:start position:0% same error on your testing side of the 00:15:11.269 --> 00:15:16.269 align:start position:0% same error on your testing side of the code<00:15:11.480> oh<00:15:12.670> yeah<00:15:13.699> and<00:15:14.410> actually<00:15:15.410> the<00:15:16.010> major 00:15:16.269 --> 00:15:16.279 align:start position:0% code oh yeah and actually the major 00:15:16.279 --> 00:15:18.220 align:start position:0% code oh yeah and actually the major truth<00:15:16.730> is<00:15:16.940> that<00:15:17.089> you<00:15:17.300> are<00:15:17.329> not<00:15:17.540> designing<00:15:17.899> just 00:15:18.220 --> 00:15:18.230 align:start position:0% truth is that you are not designing just 00:15:18.230 --> 00:15:20.530 align:start position:0% truth is that you are not designing just the<00:15:18.410> system<00:15:18.920> which<00:15:19.190> is<00:15:19.399> deployed<00:15:19.730> on<00:15:19.910> chain<00:15:20.209> or 00:15:20.530 --> 00:15:20.540 align:start position:0% the system which is deployed on chain or 00:15:20.540 --> 00:15:22.000 align:start position:0% the system which is deployed on chain or like<00:15:20.779> the<00:15:20.930> web<00:15:21.110> app<00:15:21.290> you<00:15:21.470> are<00:15:21.500> deploying<00:15:21.769> to 00:15:22.000 --> 00:15:22.010 align:start position:0% like the web app you are deploying to 00:15:22.010 --> 00:15:24.250 align:start position:0% like the web app you are deploying to accompany<00:15:22.190> it<00:15:22.430> but<00:15:23.000> the<00:15:23.209> system<00:15:23.449> includes<00:15:23.959> you 00:15:24.250 --> 00:15:24.260 align:start position:0% accompany it but the system includes you 00:15:24.260 --> 00:15:27.400 align:start position:0% accompany it but the system includes you and<00:15:24.529> it<00:15:24.770> includes<00:15:25.310> the<00:15:25.959> way<00:15:26.959> you<00:15:27.020> deliver 00:15:27.400 --> 00:15:27.410 align:start position:0% and it includes the way you deliver 00:15:27.410 --> 00:15:29.350 align:start position:0% and it includes the way you deliver things<00:15:27.949> and<00:15:28.190> so<00:15:28.310> on<00:15:28.430> and<00:15:28.640> this<00:15:28.730> is<00:15:28.790> the<00:15:29.029> info 00:15:29.350 --> 00:15:29.360 align:start position:0% things and so on and this is the info 00:15:29.360 --> 00:15:30.430 align:start position:0% things and so on and this is the info front<00:15:29.600> blockchain<00:15:29.930> gravy 00:15:30.430 --> 00:15:30.440 align:start position:0% front blockchain gravy 00:15:30.440 --> 00:15:31.780 align:start position:0% front blockchain gravy really<00:15:30.830> wonderful<00:15:31.220> project<00:15:31.610> which 00:15:31.780 --> 00:15:31.790 align:start position:0% really wonderful project which 00:15:31.790 --> 00:15:34.390 align:start position:0% really wonderful project which accumulates<00:15:32.450> the<00:15:32.930> post-mortems<00:15:33.860> of<00:15:34.070> failed 00:15:34.390 --> 00:15:34.400 align:start position:0% accumulates the post-mortems of failed 00:15:34.400 --> 00:15:37.150 align:start position:0% accumulates the post-mortems of failed and<00:15:34.700> hacked<00:15:35.350> blockchain<00:15:36.350> related<00:15:36.770> projects 00:15:37.150 --> 00:15:37.160 align:start position:0% and hacked blockchain related projects 00:15:37.160 --> 00:15:39.790 align:start position:0% and hacked blockchain related projects and<00:15:37.340> as<00:15:37.820> you<00:15:37.970> see<00:15:38.240> how<00:15:38.900> other<00:15:38.930> projects 00:15:39.790 --> 00:15:39.800 align:start position:0% and as you see how other projects 00:15:39.800 --> 00:15:41.680 align:start position:0% and as you see how other projects haven't<00:15:40.310> been<00:15:40.490> hacked<00:15:40.760> through<00:15:41.000> the<00:15:41.210> unchain 00:15:41.680 --> 00:15:41.690 align:start position:0% haven't been hacked through the unchain 00:15:41.690 --> 00:15:44.290 align:start position:0% haven't been hacked through the unchain things<00:15:41.990> at<00:15:42.200> all<00:15:42.350> it<00:15:42.590> is<00:15:43.010> all<00:15:43.250> poor<00:15:43.670> operational 00:15:44.290 --> 00:15:44.300 align:start position:0% things at all it is all poor operational 00:15:44.300 --> 00:15:45.910 align:start position:0% things at all it is all poor operational security<00:15:44.540> it's<00:15:44.870> either<00:15:45.020> your<00:15:45.260> servers<00:15:45.650> hacked 00:15:45.910 --> 00:15:45.920 align:start position:0% security it's either your servers hacked 00:15:45.920 --> 00:15:48.700 align:start position:0% security it's either your servers hacked or<00:15:46.220> your<00:15:46.610> cloud<00:15:47.540> credentials<00:15:47.900> hijacked<00:15:48.500> or 00:15:48.700 --> 00:15:48.710 align:start position:0% or your cloud credentials hijacked or 00:15:48.710 --> 00:15:50.650 align:start position:0% or your cloud credentials hijacked or your<00:15:49.130> keys<00:15:49.520> are<00:15:49.700> compromised<00:15:50.180> or<00:15:50.360> something 00:15:50.650 --> 00:15:50.660 align:start position:0% your keys are compromised or something 00:15:50.660 --> 00:15:55.210 align:start position:0% your keys are compromised or something at<00:15:50.780> that<00:15:50.900> and<00:15:52.960> good<00:15:53.960> operational<00:15:54.560> security<00:15:54.800> is 00:15:55.210 --> 00:15:55.220 align:start position:0% at that and good operational security is 00:15:55.220 --> 00:15:57.010 align:start position:0% at that and good operational security is a<00:15:55.250> part<00:15:55.640> of<00:15:55.850> a<00:15:55.940> security<00:15:56.480> of<00:15:56.540> a<00:15:56.600> system<00:15:56.900> you 00:15:57.010 --> 00:15:57.020 align:start position:0% a part of a security of a system you 00:15:57.020 --> 00:16:01.780 align:start position:0% a part of a security of a system you delivering<00:15:57.800> you<00:15:59.770> know<00:16:00.770> this<00:16:01.010> this<00:16:01.520> is<00:16:01.640> the 00:16:01.780 --> 00:16:01.790 align:start position:0% delivering you know this this is the 00:16:01.790 --> 00:16:03.520 align:start position:0% delivering you know this this is the thing<00:16:01.940> like<00:16:02.150> you<00:16:02.390> all<00:16:02.570> know<00:16:02.870> what<00:16:03.110> needs<00:16:03.260> to<00:16:03.380> be 00:16:03.520 --> 00:16:03.530 align:start position:0% thing like you all know what needs to be 00:16:03.530 --> 00:16:05.320 align:start position:0% thing like you all know what needs to be done<00:16:03.680> you're<00:16:04.160> just<00:16:04.190> not<00:16:04.730> doing<00:16:04.760> that<00:16:05.150> because 00:16:05.320 --> 00:16:05.330 align:start position:0% done you're just not doing that because 00:16:05.330 --> 00:16:08.890 align:start position:0% done you're just not doing that because it<00:16:05.540> requires<00:16:05.900> you<00:16:06.140> to<00:16:06.170> change<00:16:06.290> your<00:16:06.590> habits<00:16:07.900> to 00:16:08.890 --> 00:16:08.900 align:start position:0% it requires you to change your habits to 00:16:08.900 --> 00:16:10.990 align:start position:0% it requires you to change your habits to the<00:16:09.260> second<00:16:09.530> factor<00:16:09.800> just<00:16:10.220> get<00:16:10.580> a<00:16:10.610> hardware 00:16:10.990 --> 00:16:11.000 align:start position:0% the second factor just get a hardware 00:16:11.000 --> 00:16:12.880 align:start position:0% the second factor just get a hardware token<00:16:11.030> if<00:16:11.450> it<00:16:11.900> is<00:16:12.140> too<00:16:12.290> expensive<00:16:12.380> for<00:16:12.740> you 00:16:12.880 --> 00:16:12.890 align:start position:0% token if it is too expensive for you 00:16:12.890 --> 00:16:14.620 align:start position:0% token if it is too expensive for you just<00:16:13.190> get<00:16:13.400> the<00:16:13.610> Kryptonite<00:16:14.120> on<00:16:14.180> your 00:16:14.620 --> 00:16:14.630 align:start position:0% just get the Kryptonite on your 00:16:14.630 --> 00:16:17.530 align:start position:0% just get the Kryptonite on your smartphone<00:16:15.410> it<00:16:15.590> is<00:16:15.620> almost<00:16:16.130> as<00:16:16.340> good<00:16:16.640> for<00:16:17.090> zero 00:16:17.530 --> 00:16:17.540 align:start position:0% smartphone it is almost as good for zero 00:16:17.540 --> 00:16:21.250 align:start position:0% smartphone it is almost as good for zero price<00:16:18.670> hardware<00:16:19.670> wallets<00:16:20.030> air-gapped<00:16:20.480> sonic 00:16:21.250 --> 00:16:21.260 align:start position:0% price hardware wallets air-gapped sonic 00:16:21.260 --> 00:16:23.950 align:start position:0% price hardware wallets air-gapped sonic devices<00:16:22.180> yes<00:16:23.180> please 00:16:23.950 --> 00:16:23.960 align:start position:0% devices yes please 00:16:23.960 --> 00:16:27.550 align:start position:0% devices yes please please<00:16:24.260> do<00:16:24.410> that<00:16:25.520> website<00:16:26.510> based<00:16:26.720> wallets<00:16:27.110> bad 00:16:27.550 --> 00:16:27.560 align:start position:0% please do that website based wallets bad 00:16:27.560 --> 00:16:28.030 align:start position:0% please do that website based wallets bad idea 00:16:28.030 --> 00:16:28.040 align:start position:0% idea 00:16:28.040 --> 00:16:30.400 align:start position:0% idea never<00:16:28.340> just<00:16:28.760> if<00:16:29.150> it<00:16:29.600> is<00:16:29.750> a<00:16:29.780> production-related 00:16:30.400 --> 00:16:30.410 align:start position:0% never just if it is a production-related 00:16:30.410 --> 00:16:33.970 align:start position:0% never just if it is a production-related key<00:16:30.830> never<00:16:31.280> to<00:16:31.640> type<00:16:32.630> it<00:16:32.810> in<00:16:32.960> any<00:16:33.230> website<00:16:33.710> this 00:16:33.970 --> 00:16:33.980 align:start position:0% key never to type it in any website this 00:16:33.980 --> 00:16:36.250 align:start position:0% key never to type it in any website this is<00:16:34.040> like<00:16:34.550> instant<00:16:34.940> compromise<00:16:35.420> just<00:16:35.750> assume 00:16:36.250 --> 00:16:36.260 align:start position:0% is like instant compromise just assume 00:16:36.260 --> 00:16:38.260 align:start position:0% is like instant compromise just assume that<00:16:36.440> we've<00:16:36.890> seen<00:16:37.100> even<00:16:37.490> the<00:16:37.640> best<00:16:37.910> online 00:16:38.260 --> 00:16:38.270 align:start position:0% that we've seen even the best online 00:16:38.270 --> 00:16:40.510 align:start position:0% that we've seen even the best online wallets<00:16:38.990> being<00:16:39.200> compromised<00:16:39.740> by<00:16:39.950> really 00:16:40.510 --> 00:16:40.520 align:start position:0% wallets being compromised by really 00:16:40.520 --> 00:16:42.460 align:start position:0% wallets being compromised by really really<00:16:40.790> expensive<00:16:40.940> attacks<00:16:41.480> you<00:16:42.200> are<00:16:42.290> not 00:16:42.460 --> 00:16:42.470 align:start position:0% really expensive attacks you are not 00:16:42.470 --> 00:16:44.080 align:start position:0% really expensive attacks you are not protected<00:16:42.920> from<00:16:42.950> that<00:16:43.190> just<00:16:43.670> use<00:16:43.790> something 00:16:44.080 --> 00:16:44.090 align:start position:0% protected from that just use something 00:16:44.090 --> 00:16:48.160 align:start position:0% protected from that just use something else<00:16:45.100> real<00:16:46.100> keys<00:16:46.400> to<00:16:46.540> conduct<00:16:47.540> damage<00:16:47.840> like<00:16:48.020> to 00:16:48.160 --> 00:16:48.170 align:start position:0% else real keys to conduct damage like to 00:16:48.170 --> 00:16:50.200 align:start position:0% else real keys to conduct damage like to your<00:16:48.290> investors<00:16:48.770> or<00:16:48.980> to<00:16:49.070> someone<00:16:49.250> mmm 00:16:50.200 --> 00:16:50.210 align:start position:0% your investors or to someone mmm 00:16:50.210 --> 00:16:52.210 align:start position:0% your investors or to someone mmm use<00:16:50.600> the<00:16:50.720> test<00:16:50.960> net<00:16:51.140> all<00:16:51.290> the<00:16:51.500> time<00:16:51.920> like<00:16:52.040> your 00:16:52.210 --> 00:16:52.220 align:start position:0% use the test net all the time like your 00:16:52.220 --> 00:16:54.010 align:start position:0% use the test net all the time like your production<00:16:52.580> keys<00:16:52.790> stay<00:16:53.210> safe<00:16:53.510> if<00:16:53.750> they<00:16:53.900> are 00:16:54.010 --> 00:16:54.020 align:start position:0% production keys stay safe if they are 00:16:54.020 --> 00:16:55.630 align:start position:0% production keys stay safe if they are not<00:16:54.230> on<00:16:54.380> the<00:16:54.500> screen<00:16:54.770> when<00:16:54.980> someone<00:16:55.310> else<00:16:55.490> is 00:16:55.630 --> 00:16:55.640 align:start position:0% not on the screen when someone else is 00:16:55.640 --> 00:16:57.760 align:start position:0% not on the screen when someone else is looking<00:16:55.790> that's<00:16:56.150> the<00:16:56.450> rule<00:16:56.690> just<00:16:57.380> you 00:16:57.760 --> 00:16:57.770 align:start position:0% looking that's the rule just you 00:16:57.770 --> 00:17:00.000 align:start position:0% looking that's the rule just you wouldn't<00:16:58.160> believe<00:16:58.460> how<00:16:58.730> frequently<00:16:59.360> I<00:16:59.450> see 00:17:00.000 --> 00:17:00.010 align:start position:0% wouldn't believe how frequently I see 00:17:00.010 --> 00:17:03.120 align:start position:0% wouldn't believe how frequently I see compromises<00:17:01.010> from<00:17:01.250> these<00:17:01.520> like<00:17:02.090> probably 00:17:03.120 --> 00:17:03.130 align:start position:0% compromises from these like probably 00:17:03.130 --> 00:17:05.290 align:start position:0% compromises from these like probably everything<00:17:04.130> ends<00:17:04.520> up<00:17:04.640> fine<00:17:04.970> and<00:17:05.240> you 00:17:05.290 --> 00:17:05.300 align:start position:0% everything ends up fine and you 00:17:05.300 --> 00:17:07.120 align:start position:0% everything ends up fine and you investors<00:17:05.720> a<00:17:05.810> trust<00:17:06.050> for<00:17:06.199> few<00:17:06.319> guys<00:17:06.500> but<00:17:06.530> why 00:17:07.120 --> 00:17:07.130 align:start position:0% investors a trust for few guys but why 00:17:07.130 --> 00:17:08.800 align:start position:0% investors a trust for few guys but why push<00:17:07.490> your<00:17:07.670> luck<00:17:07.790> and<00:17:08.270> just<00:17:08.420> don't<00:17:08.660> ever 00:17:08.800 --> 00:17:08.810 align:start position:0% push your luck and just don't ever 00:17:08.810 --> 00:17:10.689 align:start position:0% push your luck and just don't ever forget<00:17:09.230> that<00:17:09.290> many<00:17:09.650> mass<00:17:09.829> uses<00:17:10.189> the<00:17:10.310> same<00:17:10.459> key 00:17:10.689 --> 00:17:10.699 align:start position:0% forget that many mass uses the same key 00:17:10.699 --> 00:17:15.670 align:start position:0% forget that many mass uses the same key and<00:17:10.850> every<00:17:11.089> network<00:17:11.390> yes<00:17:14.500> general<00:17:15.500> hygiene 00:17:15.670 --> 00:17:15.680 align:start position:0% and every network yes general hygiene 00:17:15.680 --> 00:17:18.220 align:start position:0% and every network yes general hygiene like<00:17:16.100> do<00:17:16.730> it<00:17:16.880> like<00:17:17.089> you<00:17:17.209> know<00:17:17.360> you<00:17:17.630> not<00:17:17.780> need<00:17:17.990> to 00:17:18.220 --> 00:17:18.230 align:start position:0% like do it like you know you not need to 00:17:18.230 --> 00:17:19.750 align:start position:0% like do it like you know you not need to use<00:17:18.380> password<00:17:18.740> manager<00:17:19.100> you<00:17:19.220> don't<00:17:19.430> need<00:17:19.640> to 00:17:19.750 --> 00:17:19.760 align:start position:0% use password manager you don't need to 00:17:19.760 --> 00:17:21.550 align:start position:0% use password manager you don't need to reuse<00:17:19.850> passwords<00:17:20.150> still<00:17:20.810> like<00:17:20.990> everyone<00:17:21.380> has 00:17:21.550 --> 00:17:21.560 align:start position:0% reuse passwords still like everyone has 00:17:21.560 --> 00:17:24.150 align:start position:0% reuse passwords still like everyone has them<00:17:21.770> let's<00:17:22.130> just<00:17:22.520> make<00:17:22.939> push<00:17:23.300> and<00:17:23.540> change<00:17:23.839> it 00:17:24.150 --> 00:17:24.160 align:start position:0% them let's just make push and change it 00:17:24.160 --> 00:17:26.679 align:start position:0% them let's just make push and change it full<00:17:25.160> disk<00:17:25.339> encryption<00:17:25.430> just<00:17:26.180> is<00:17:26.300> a<00:17:26.329> must<00:17:26.600> you 00:17:26.679 --> 00:17:26.689 align:start position:0% full disk encryption just is a must you 00:17:26.689 --> 00:17:28.179 align:start position:0% full disk encryption just is a must you don't<00:17:26.900> want<00:17:27.140> to<00:17:27.410> have<00:17:27.829> your<00:17:27.980> project 00:17:28.179 --> 00:17:28.189 align:start position:0% don't want to have your project 00:17:28.189 --> 00:17:29.950 align:start position:0% don't want to have your project compromised<00:17:28.940> just<00:17:29.210> because<00:17:29.420> you<00:17:29.540> forgot<00:17:29.810> your 00:17:29.950 --> 00:17:29.960 align:start position:0% compromised just because you forgot your 00:17:29.960 --> 00:17:32.020 align:start position:0% compromised just because you forgot your laptop<00:17:30.290> on<00:17:30.380> the<00:17:30.470> train<00:17:30.850> firewalls<00:17:31.850> like 00:17:32.020 --> 00:17:32.030 align:start position:0% laptop on the train firewalls like 00:17:32.030 --> 00:17:35.290 align:start position:0% laptop on the train firewalls like everyone<00:17:32.510> knows<00:17:32.660> the<00:17:32.870> list<00:17:33.430> just<00:17:34.430> figure<00:17:35.060> out 00:17:35.290 --> 00:17:35.300 align:start position:0% everyone knows the list just figure out 00:17:35.300 --> 00:17:36.880 align:start position:0% everyone knows the list just figure out the<00:17:35.600> way<00:17:35.750> you<00:17:35.810> can<00:17:36.200> incorporate<00:17:36.470> those 00:17:36.880 --> 00:17:36.890 align:start position:0% the way you can incorporate those 00:17:36.890 --> 00:17:38.200 align:start position:0% the way you can incorporate those security<00:17:37.340> habits<00:17:37.640> in<00:17:37.730> your<00:17:37.760> day-to-day<00:17:38.000> life 00:17:38.200 --> 00:17:38.210 align:start position:0% security habits in your day-to-day life 00:17:38.210 --> 00:17:40.930 align:start position:0% security habits in your day-to-day life I<00:17:38.740> promise<00:17:39.740> you<00:17:39.890> I<00:17:39.920> will<00:17:40.130> be<00:17:40.370> motivational 00:17:40.930 --> 00:17:40.940 align:start position:0% I promise you I will be motivational 00:17:40.940 --> 00:17:43.120 align:start position:0% I promise you I will be motivational speaker<00:17:41.660> yeah<00:17:42.140> you<00:17:42.410> know<00:17:42.560> what<00:17:42.770> needs<00:17:42.920> to<00:17:43.010> be 00:17:43.120 --> 00:17:43.130 align:start position:0% speaker yeah you know what needs to be 00:17:43.130 --> 00:17:43.990 align:start position:0% speaker yeah you know what needs to be done<00:17:43.250> I<00:17:43.490> know 00:17:43.990 --> 00:17:44.000 align:start position:0% done I know 00:17:44.000 --> 00:17:47.890 align:start position:0% done I know can<00:17:44.150> do<00:17:44.270> it<00:17:44.390> please<00:17:44.660> do<00:17:44.900> it<00:17:46.850> another<00:17:47.330> thing<00:17:47.540> sit 00:17:47.890 --> 00:17:47.900 align:start position:0% can do it please do it another thing sit 00:17:47.900 --> 00:17:49.540 align:start position:0% can do it please do it another thing sit down<00:17:48.020> with<00:17:48.230> your<00:17:48.410> DevOps<00:17:48.980> or<00:17:49.250> operations 00:17:49.540 --> 00:17:49.550 align:start position:0% down with your DevOps or operations 00:17:49.550 --> 00:17:51.640 align:start position:0% down with your DevOps or operations engineers<00:17:50.360> and<00:17:50.720> come<00:17:51.050> up<00:17:51.170> with<00:17:51.350> a<00:17:51.410> list<00:17:51.560> of 00:17:51.640 --> 00:17:51.650 align:start position:0% engineers and come up with a list of 00:17:51.650 --> 00:17:53.320 align:start position:0% engineers and come up with a list of security<00:17:52.070> improvements<00:17:52.340> there<00:17:52.700> they 00:17:53.320 --> 00:17:53.330 align:start position:0% security improvements there they 00:17:53.330 --> 00:17:55.210 align:start position:0% security improvements there they probably<00:17:53.600> also<00:17:53.900> know<00:17:54.230> what<00:17:54.680> needs<00:17:54.860> to<00:17:54.980> be<00:17:55.100> done 00:17:55.210 --> 00:17:55.220 align:start position:0% probably also know what needs to be done 00:17:55.220 --> 00:17:58.030 align:start position:0% probably also know what needs to be done but<00:17:55.640> they<00:17:55.790> also<00:17:56.230> overload<00:17:57.230> it<00:17:57.440> with<00:17:57.470> day<00:17:57.980> to 00:17:58.030 --> 00:17:58.040 align:start position:0% but they also overload it with day to 00:17:58.040 --> 00:17:59.950 align:start position:0% but they also overload it with day to day<00:17:58.280> tasks<00:17:58.640> so<00:17:58.850> they<00:17:58.880> never<00:17:59.330> improved<00:17:59.810> your 00:17:59.950 --> 00:17:59.960 align:start position:0% day tasks so they never improved your 00:17:59.960 --> 00:18:02.230 align:start position:0% day tasks so they never improved your security<00:18:00.290> but<00:18:00.920> we<00:18:01.040> need<00:18:01.310> know<00:18:01.640> what<00:18:01.910> needs<00:18:02.150> to 00:18:02.230 --> 00:18:02.240 align:start position:0% security but we need know what needs to 00:18:02.240 --> 00:18:04.840 align:start position:0% security but we need know what needs to be<00:18:02.360> done<00:18:02.540> so<00:18:02.720> please<00:18:03.200> go<00:18:03.620> in<00:18:03.770> and<00:18:04.010> figure<00:18:04.730> out 00:18:04.840 --> 00:18:04.850 align:start position:0% be done so please go in and figure out 00:18:04.850 --> 00:18:06.520 align:start position:0% be done so please go in and figure out do<00:18:05.090> you<00:18:05.150> need<00:18:05.270> passwords<00:18:05.660> for<00:18:05.780> SSH<00:18:06.170> properly 00:18:06.520 --> 00:18:06.530 align:start position:0% do you need passwords for SSH properly 00:18:06.530 --> 00:18:10.090 align:start position:0% do you need passwords for SSH properly you<00:18:06.590> don't<00:18:06.770> change<00:18:07.550> that<00:18:08.050> are<00:18:09.050> you<00:18:09.230> build 00:18:10.090 --> 00:18:10.100 align:start position:0% you don't change that are you build 00:18:10.100 --> 00:18:12.910 align:start position:0% you don't change that are you build machines<00:18:10.430> are<00:18:10.580> secure<00:18:10.910> are<00:18:11.900> your<00:18:12.140> secrets<00:18:12.770> for 00:18:12.910 --> 00:18:12.920 align:start position:0% machines are secure are your secrets for 00:18:12.920 --> 00:18:15.190 align:start position:0% machines are secure are your secrets for builds<00:18:13.550> are<00:18:13.700> protected<00:18:14.390> and<00:18:14.540> they<00:18:14.720> won't<00:18:14.990> leak 00:18:15.190 --> 00:18:15.200 align:start position:0% builds are protected and they won't leak 00:18:15.200 --> 00:18:18.880 align:start position:0% builds are protected and they won't leak to<00:18:15.410> any<00:18:15.620> third<00:18:16.010> party<00:18:16.400> pull<00:18:16.580> request<00:18:17.410> offer<00:18:18.410> to 00:18:18.880 --> 00:18:18.890 align:start position:0% to any third party pull request offer to 00:18:18.890 --> 00:18:21.400 align:start position:0% to any third party pull request offer to your<00:18:19.130> repository<00:18:19.550> that's<00:18:20.360> a<00:18:20.540> surprisingly 00:18:21.400 --> 00:18:21.410 align:start position:0% your repository that's a surprisingly 00:18:21.410 --> 00:18:24.610 align:start position:0% your repository that's a surprisingly frequent<00:18:21.950> thing<00:18:22.130> I<00:18:22.340> see<00:18:22.520> well<00:18:23.300> yeah<00:18:23.840> if<00:18:24.050> easier 00:18:24.610 --> 00:18:24.620 align:start position:0% frequent thing I see well yeah if easier 00:18:24.620 --> 00:18:26.530 align:start position:0% frequent thing I see well yeah if easier MongoDB<00:18:25.220> port<00:18:25.460> is<00:18:25.610> closed<00:18:25.850> from<00:18:26.030> the<00:18:26.210> external 00:18:26.530 --> 00:18:26.540 align:start position:0% MongoDB port is closed from the external 00:18:26.540 --> 00:18:28.540 align:start position:0% MongoDB port is closed from the external world<00:18:26.720> that's<00:18:27.170> like<00:18:27.320> the<00:18:27.800> most<00:18:28.040> frequent 00:18:28.540 --> 00:18:28.550 align:start position:0% world that's like the most frequent 00:18:28.550 --> 00:18:33.870 align:start position:0% world that's like the most frequent source<00:18:28.790> of<00:18:28.940> hacks<00:18:29.180> in<00:18:29.450> the<00:18:29.600> last<00:18:29.930> year<00:18:32.230> yeah 00:18:33.870 --> 00:18:33.880 align:start position:0% source of hacks in the last year yeah 00:18:33.880 --> 00:18:40.900 align:start position:0% source of hacks in the last year yeah this<00:18:34.880> thing<00:18:36.820> problems<00:18:37.820> happen<00:18:39.220> you<00:18:40.220> just<00:18:40.250> need 00:18:40.900 --> 00:18:40.910 align:start position:0% this thing problems happen you just need 00:18:40.910 --> 00:18:42.910 align:start position:0% this thing problems happen you just need to<00:18:41.030> be<00:18:41.150> able<00:18:41.270> to<00:18:41.450> recover<00:18:42.200> from<00:18:42.350> it<00:18:42.590> and<00:18:42.710> have<00:18:42.890> a 00:18:42.910 --> 00:18:42.920 align:start position:0% to be able to recover from it and have a 00:18:42.920 --> 00:18:48.190 align:start position:0% to be able to recover from it and have a back-up<00:18:43.250> plan<00:18:45.460> the<00:18:46.460> thing<00:18:46.730> is<00:18:46.940> that<00:18:47.150> when 00:18:48.190 --> 00:18:48.200 align:start position:0% back-up plan the thing is that when 00:18:48.200 --> 00:18:49.570 align:start position:0% back-up plan the thing is that when hits<00:18:48.410> the<00:18:48.470> fan<00:18:48.590> you<00:18:48.860> will<00:18:49.010> be<00:18:49.100> under<00:18:49.340> stress 00:18:49.570 --> 00:18:49.580 align:start position:0% hits the fan you will be under stress 00:18:49.580 --> 00:18:51.880 align:start position:0% hits the fan you will be under stress and<00:18:49.850> you<00:18:50.060> want<00:18:50.480> to<00:18:50.570> be<00:18:50.660> able<00:18:50.870> to<00:18:51.080> react<00:18:51.590> in<00:18:51.830> time 00:18:51.880 --> 00:18:51.890 align:start position:0% and you want to be able to react in time 00:18:51.890 --> 00:18:54.850 align:start position:0% and you want to be able to react in time the<00:18:52.400> smartest<00:18:52.820> way<00:18:53.000> so<00:18:53.810> the<00:18:53.990> only<00:18:54.170> thing<00:18:54.560> I<00:18:54.680> can 00:18:54.850 --> 00:18:54.860 align:start position:0% the smartest way so the only thing I can 00:18:54.860 --> 00:18:56.800 align:start position:0% the smartest way so the only thing I can recommend<00:18:54.980> is<00:18:55.520> come<00:18:55.940> up<00:18:56.120> with<00:18:56.330> a<00:18:56.360> recovery 00:18:56.800 --> 00:18:56.810 align:start position:0% recommend is come up with a recovery 00:18:56.810 --> 00:18:59.410 align:start position:0% recommend is come up with a recovery plan<00:18:56.990> before<00:18:57.530> things<00:18:57.890> happen<00:18:57.950> have<00:18:58.850> a<00:18:58.880> really 00:18:59.410 --> 00:18:59.420 align:start position:0% plan before things happen have a really 00:18:59.420 --> 00:19:01.060 align:start position:0% plan before things happen have a really it<00:18:59.570> will<00:18:59.780> be<00:18:59.900> stupid<00:19:00.320> it<00:19:00.440> will<00:19:00.590> be<00:19:00.680> obvious 00:19:01.060 --> 00:19:01.070 align:start position:0% it will be stupid it will be obvious 00:19:01.070 --> 00:19:03.790 align:start position:0% it will be stupid it will be obvious checklist<00:19:01.520> you<00:19:01.700> will<00:19:01.850> feel<00:19:02.330> like<00:19:02.630> am<00:19:03.380> I<00:19:03.590> in<00:19:03.710> the 00:19:03.790 --> 00:19:03.800 align:start position:0% checklist you will feel like am I in the 00:19:03.800 --> 00:19:05.320 align:start position:0% checklist you will feel like am I in the five<00:19:04.010> grade<00:19:04.340> again<00:19:04.640> I'm<00:19:04.820> writing<00:19:05.300> down 00:19:05.320 --> 00:19:05.330 align:start position:0% five grade again I'm writing down 00:19:05.330 --> 00:19:07.870 align:start position:0% five grade again I'm writing down obvious<00:19:05.900> things<00:19:06.490> trust<00:19:07.490> me 00:19:07.870 --> 00:19:07.880 align:start position:0% obvious things trust me 00:19:07.880 --> 00:19:10.570 align:start position:0% obvious things trust me you<00:19:08.210> will<00:19:08.480> really<00:19:08.990> thank<00:19:09.380> you<00:19:09.470> later<00:19:09.830> when<00:19:10.400> it 00:19:10.570 --> 00:19:10.580 align:start position:0% you will really thank you later when it 00:19:10.580 --> 00:19:13.240 align:start position:0% you will really thank you later when it times<00:19:10.940> come<00:19:11.270> to<00:19:11.540> unpack<00:19:12.410> that<00:19:12.590> checklist<00:19:12.920> and 00:19:13.240 --> 00:19:13.250 align:start position:0% times come to unpack that checklist and 00:19:13.250 --> 00:19:15.400 align:start position:0% times come to unpack that checklist and go<00:19:13.460> step<00:19:13.790> by<00:19:13.820> step<00:19:13.970> and<00:19:14.390> ensure<00:19:14.750> who<00:19:15.320> is 00:19:15.400 --> 00:19:15.410 align:start position:0% go step by step and ensure who is 00:19:15.410 --> 00:19:17.500 align:start position:0% go step by step and ensure who is responsible<00:19:15.950> for<00:19:16.010> what<00:19:16.310> what<00:19:16.850> is<00:19:17.000> the<00:19:17.180> effect 00:19:17.500 --> 00:19:17.510 align:start position:0% responsible for what what is the effect 00:19:17.510 --> 00:19:20.410 align:start position:0% responsible for what what is the effect that<00:19:17.770> the<00:19:18.770> parts<00:19:19.520> of<00:19:19.640> your<00:19:19.790> system 00:19:20.410 --> 00:19:20.420 align:start position:0% that the parts of your system 00:19:20.420 --> 00:19:22.330 align:start position:0% that the parts of your system do<00:19:20.810> you<00:19:20.930> need<00:19:21.080> to<00:19:21.200> notify<00:19:21.440> your<00:19:21.680> partners<00:19:22.130> what 00:19:22.330 --> 00:19:22.340 align:start position:0% do you need to notify your partners what 00:19:22.340 --> 00:19:23.740 align:start position:0% do you need to notify your partners what are<00:19:22.490> the<00:19:22.580> channel<00:19:22.940> for<00:19:23.090> those<00:19:23.180> notifications 00:19:23.740 --> 00:19:23.750 align:start position:0% are the channel for those notifications 00:19:23.750 --> 00:19:25.690 align:start position:0% are the channel for those notifications and<00:19:23.870> so<00:19:23.990> on<00:19:24.110> obvious<00:19:24.500> things<00:19:24.710> have<00:19:25.160> it<00:19:25.340> have<00:19:25.670> it 00:19:25.690 --> 00:19:25.700 align:start position:0% and so on obvious things have it have it 00:19:25.700 --> 00:19:26.110 align:start position:0% and so on obvious things have it have it ready 00:19:26.110 --> 00:19:26.120 align:start position:0% ready 00:19:26.120 --> 00:19:30.220 align:start position:0% ready it<00:19:26.360> will<00:19:26.570> save<00:19:26.720> you<00:19:26.810> day<00:19:28.030> yeah<00:19:29.060> yes<00:19:29.720> so<00:19:29.930> I<00:19:30.020> think 00:19:30.220 --> 00:19:30.230 align:start position:0% it will save you day yeah yes so I think 00:19:30.230 --> 00:19:32.170 align:start position:0% it will save you day yeah yes so I think just<00:19:30.620> like<00:19:30.770> all<00:19:31.010> in<00:19:31.160> summary<00:19:31.520> you<00:19:31.820> guys<00:19:32.000> are 00:19:32.170 --> 00:19:32.180 align:start position:0% just like all in summary you guys are 00:19:32.180 --> 00:19:34.060 align:start position:0% just like all in summary you guys are all<00:19:32.270> really<00:19:32.420> smart<00:19:32.750> people<00:19:33.020> just<00:19:33.590> write<00:19:33.860> down 00:19:34.060 --> 00:19:34.070 align:start position:0% all really smart people just write down 00:19:34.070 --> 00:19:35.830 align:start position:0% all really smart people just write down more<00:19:34.310> things<00:19:34.610> on<00:19:34.790> paper<00:19:35.000> share<00:19:35.660> them<00:19:35.810> with 00:19:35.830 --> 00:19:35.840 align:start position:0% more things on paper share them with 00:19:35.840 --> 00:19:36.460 align:start position:0% more things on paper share them with each<00:19:36.050> other 00:19:36.460 --> 00:19:36.470 align:start position:0% each other 00:19:36.470 --> 00:19:38.440 align:start position:0% each other that'll<00:19:37.100> make<00:19:37.250> your<00:19:37.400> things<00:19:37.670> all<00:19:38.000> the<00:19:38.270> more 00:19:38.440 --> 00:19:38.450 align:start position:0% that'll make your things all the more 00:19:38.450 --> 00:19:40.060 align:start position:0% that'll make your things all the more secure<00:19:38.840> that<00:19:39.080> all<00:19:39.500> of<00:19:39.710> these<00:19:39.860> recommendations 00:19:40.060 --> 00:19:40.070 align:start position:0% secure that all of these recommendations 00:19:40.070 --> 00:19:42.240 align:start position:0% secure that all of these recommendations involve<00:19:40.910> writing<00:19:41.270> things<00:19:41.480> down 00:19:42.240 --> 00:19:42.250 align:start position:0% involve writing things down 00:19:42.250 --> 00:19:44.560 align:start position:0% involve writing things down thanks<00:19:43.250> to<00:19:43.310> those<00:19:43.460> folks<00:19:43.700> we<00:19:44.060> got<00:19:44.210> 10<00:19:44.420> minutes 00:19:44.560 --> 00:19:44.570 align:start position:0% thanks to those folks we got 10 minutes 00:19:44.570 --> 00:19:50.419 align:start position:0% thanks to those folks we got 10 minutes for<00:19:44.810> questions 00:19:50.419 --> 00:19:50.429 align:start position:0% 00:19:50.429 --> 00:19:59.360 align:start position:0% just<00:19:51.429> raise<00:19:51.730> your<00:19:51.940> hand<00:19:53.370> we<00:19:54.370> got<00:19:54.549> this<00:19:54.669> down 00:19:59.360 --> 00:19:59.370 align:start position:0% 00:19:59.370 --> 00:20:02.879 align:start position:0% hey<00:20:00.370> so<00:20:00.429> essentially<00:20:01.269> first<00:20:01.960> slide<00:20:02.169> is<00:20:02.409> the 00:20:02.879 --> 00:20:02.889 align:start position:0% hey so essentially first slide is the 00:20:02.889 --> 00:20:04.860 align:start position:0% hey so essentially first slide is the return<00:20:03.250> of<00:20:03.279> waterfall<00:20:04.000> a<00:20:04.269> little<00:20:04.539> bit<00:20:04.720> at 00:20:04.860 --> 00:20:04.870 align:start position:0% return of waterfall a little bit at 00:20:04.870 --> 00:20:07.529 align:start position:0% return of waterfall a little bit at least<00:20:04.990> it<00:20:05.169> feels<00:20:05.769> like<00:20:06.130> that<00:20:06.370> and<00:20:06.669> I<00:20:07.240> get<00:20:07.419> it 00:20:07.529 --> 00:20:07.539 align:start position:0% least it feels like that and I get it 00:20:07.539 --> 00:20:09.269 align:start position:0% least it feels like that and I get it for<00:20:07.690> airspace<00:20:08.259> if<00:20:08.470> you're<00:20:08.559> building<00:20:08.679> rockets 00:20:09.269 --> 00:20:09.279 align:start position:0% for airspace if you're building rockets 00:20:09.279 --> 00:20:11.249 align:start position:0% for airspace if you're building rockets and<00:20:09.519> planes<00:20:09.730> where<00:20:10.210> people<00:20:10.480> can<00:20:10.659> die<00:20:10.929> or 00:20:11.249 --> 00:20:11.259 align:start position:0% and planes where people can die or 00:20:11.259 --> 00:20:13.440 align:start position:0% and planes where people can die or people<00:20:11.860> can<00:20:12.009> lose<00:20:12.159> all<00:20:12.340> of<00:20:12.370> their<00:20:12.519> money<00:20:12.730> for 00:20:13.440 --> 00:20:13.450 align:start position:0% people can lose all of their money for 00:20:13.450 --> 00:20:15.629 align:start position:0% people can lose all of their money for sure<00:20:13.659> you<00:20:13.809> shouldn't<00:20:14.169> throw<00:20:15.429> on<00:20:15.549> the 00:20:15.629 --> 00:20:15.639 align:start position:0% sure you shouldn't throw on the 00:20:15.639 --> 00:20:17.399 align:start position:0% sure you shouldn't throw on the wall<00:20:15.789> and<00:20:15.940> see<00:20:16.179> what<00:20:16.210> sticks<00:20:16.450> or<00:20:16.899> what's<00:20:17.049> what 00:20:17.399 --> 00:20:17.409 align:start position:0% wall and see what sticks or what's what 00:20:17.409 --> 00:20:19.619 align:start position:0% wall and see what sticks or what's what gets<00:20:17.620> hacked<00:20:17.980> but<00:20:18.639> in<00:20:18.759> reality<00:20:18.940> it's<00:20:19.389> it's 00:20:19.619 --> 00:20:19.629 align:start position:0% gets hacked but in reality it's it's 00:20:19.629 --> 00:20:21.119 align:start position:0% gets hacked but in reality it's it's also<00:20:19.870> a<00:20:20.049> little<00:20:20.200> bit<00:20:20.289> more<00:20:20.500> nuanced<00:20:20.889> right 00:20:21.119 --> 00:20:21.129 align:start position:0% also a little bit more nuanced right 00:20:21.129 --> 00:20:23.220 align:start position:0% also a little bit more nuanced right it's<00:20:21.309> not<00:20:21.460> a<00:20:21.669> plane<00:20:22.090> or<00:20:22.450> something<00:20:22.960> super 00:20:23.220 --> 00:20:23.230 align:start position:0% it's not a plane or something super 00:20:23.230 --> 00:20:25.289 align:start position:0% it's not a plane or something super agile<00:20:23.409> where<00:20:23.799> you<00:20:23.889> can<00:20:24.039> can<00:20:24.700> afford<00:20:24.970> to<00:20:25.149> make 00:20:25.289 --> 00:20:25.299 align:start position:0% agile where you can can afford to make 00:20:25.299 --> 00:20:28.490 align:start position:0% agile where you can can afford to make mistakes<00:20:25.870> so<00:20:26.649> I'd<00:20:26.799> like<00:20:26.980> to<00:20:27.039> know<00:20:27.399> how<00:20:27.700> do<00:20:27.759> you 00:20:28.490 --> 00:20:28.500 align:start position:0% mistakes so I'd like to know how do you 00:20:28.500 --> 00:20:32.249 align:start position:0% mistakes so I'd like to know how do you how<00:20:29.500> do<00:20:29.559> you<00:20:29.740> know<00:20:30.309> which<00:20:30.759> mindset<00:20:31.600> to<00:20:31.779> apply 00:20:32.249 --> 00:20:32.259 align:start position:0% how do you know which mindset to apply 00:20:32.259 --> 00:20:35.279 align:start position:0% how do you know which mindset to apply because<00:20:33.100> in<00:20:33.279> that<00:20:33.370> first<00:20:33.669> example<00:20:34.299> if<00:20:34.570> the 00:20:35.279 --> 00:20:35.289 align:start position:0% because in that first example if the 00:20:35.289 --> 00:20:37.529 align:start position:0% because in that first example if the first<00:20:35.559> time<00:20:35.799> users<00:20:36.070> actually<00:20:36.549> see<00:20:36.730> this<00:20:36.879> is<00:20:37.149> at 00:20:37.529 --> 00:20:37.539 align:start position:0% first time users actually see this is at 00:20:37.539 --> 00:20:40.080 align:start position:0% first time users actually see this is at the<00:20:37.690> very<00:20:38.039> top<00:20:39.039> right<00:20:39.100> of<00:20:39.460> the<00:20:39.610> V<00:20:39.820> you 00:20:40.080 --> 00:20:40.090 align:start position:0% the very top right of the V you 00:20:40.090 --> 00:20:42.590 align:start position:0% the very top right of the V you potentially<00:20:40.929> have<00:20:41.019> lost<00:20:41.259> a<00:20:41.409> lot<00:20:41.620> of<00:20:41.679> time 00:20:42.590 --> 00:20:42.600 align:start position:0% potentially have lost a lot of time 00:20:42.600 --> 00:20:45.539 align:start position:0% potentially have lost a lot of time where<00:20:43.600> users<00:20:44.080> could<00:20:44.409> have<00:20:44.559> told<00:20:44.830> you<00:20:45.070> what's 00:20:45.539 --> 00:20:45.549 align:start position:0% where users could have told you what's 00:20:45.549 --> 00:20:48.060 align:start position:0% where users could have told you what's not<00:20:45.789> working<00:20:46.120> that<00:20:46.600> is<00:20:47.379> a<00:20:47.440> great<00:20:47.620> point<00:20:47.830> I 00:20:48.060 --> 00:20:48.070 align:start position:0% not working that is a great point I 00:20:48.070 --> 00:20:49.680 align:start position:0% not working that is a great point I think<00:20:48.129> like<00:20:48.879> just<00:20:48.909> getting<00:20:49.269> more<00:20:49.509> user 00:20:49.680 --> 00:20:49.690 align:start position:0% think like just getting more user 00:20:49.690 --> 00:20:51.659 align:start position:0% think like just getting more user feedback<00:20:50.019> in<00:20:50.440> terms<00:20:50.950> of<00:20:51.100> the<00:20:51.190> cycles<00:20:51.580> so 00:20:51.659 --> 00:20:51.669 align:start position:0% feedback in terms of the cycles so 00:20:51.669 --> 00:20:53.759 align:start position:0% feedback in terms of the cycles so that's<00:20:51.820> about<00:20:51.940> doing<00:20:52.240> smaller<00:20:52.570> demos<00:20:53.049> trying 00:20:53.759 --> 00:20:53.769 align:start position:0% that's about doing smaller demos trying 00:20:53.769 --> 00:20:55.440 align:start position:0% that's about doing smaller demos trying to<00:20:53.889> figure<00:20:54.129> out<00:20:54.159> things<00:20:54.279> ahead<00:20:54.700> of<00:20:54.850> time<00:20:54.970> like 00:20:55.440 --> 00:20:55.450 align:start position:0% to figure out things ahead of time like 00:20:55.450 --> 00:20:57.480 align:start position:0% to figure out things ahead of time like getting<00:20:55.809> practical<00:20:56.559> feedback<00:20:57.070> about<00:20:57.250> the 00:20:57.480 --> 00:20:57.490 align:start position:0% getting practical feedback about the 00:20:57.490 --> 00:20:59.850 align:start position:0% getting practical feedback about the market<00:20:57.879> right<00:20:58.200> that<00:20:59.200> you're<00:20:59.320> intending<00:20:59.679> and 00:20:59.850 --> 00:20:59.860 align:start position:0% market right that you're intending and 00:20:59.860 --> 00:21:03.389 align:start position:0% market right that you're intending and operate<00:21:00.190> in<00:21:00.340> I<00:21:00.519> think<00:21:01.500> so<00:21:02.500> in<00:21:02.769> response<00:21:03.129> to<00:21:03.279> the 00:21:03.389 --> 00:21:03.399 align:start position:0% operate in I think so in response to the 00:21:03.399 --> 00:21:05.039 align:start position:0% operate in I think so in response to the V<00:21:03.519> thing<00:21:03.820> like<00:21:04.090> like<00:21:04.389> nobody<00:21:04.779> said<00:21:04.960> you 00:21:05.039 --> 00:21:05.049 align:start position:0% V thing like like nobody said you 00:21:05.049 --> 00:21:06.509 align:start position:0% V thing like like nobody said you couldn't<00:21:05.289> use<00:21:05.409> V<00:21:05.590> and<00:21:05.740> agile<00:21:06.009> at<00:21:06.190> waterfall 00:21:06.509 --> 00:21:06.519 align:start position:0% couldn't use V and agile at waterfall 00:21:06.519 --> 00:21:08.759 align:start position:0% couldn't use V and agile at waterfall and<00:21:06.639> agile<00:21:06.759> together<00:21:07.299> like<00:21:07.750> everyone's<00:21:08.649> like 00:21:08.759 --> 00:21:08.769 align:start position:0% and agile together like everyone's like 00:21:08.769 --> 00:21:10.860 align:start position:0% and agile together like everyone's like oh<00:21:08.950> man<00:21:09.159> that's<00:21:09.399> that's<00:21:10.330> the<00:21:10.419> thing<00:21:10.570> you<00:21:10.690> can't 00:21:10.860 --> 00:21:10.870 align:start position:0% oh man that's that's the thing you can't 00:21:10.870 --> 00:21:12.840 align:start position:0% oh man that's that's the thing you can't do<00:21:11.019> but<00:21:11.200> like<00:21:11.409> you<00:21:11.740> can<00:21:11.950> like<00:21:12.190> I<00:21:12.309> chose<00:21:12.549> like 00:21:12.840 --> 00:21:12.850 align:start position:0% do but like you can like I chose like 00:21:12.850 --> 00:21:14.940 align:start position:0% do but like you can like I chose like kind<00:21:13.029> of<00:21:13.090> a<00:21:13.149> short<00:21:13.450> cycle<00:21:14.110> that<00:21:14.470> you're<00:21:14.620> you're 00:21:14.940 --> 00:21:14.950 align:start position:0% kind of a short cycle that you're you're 00:21:14.950 --> 00:21:16.320 align:start position:0% kind of a short cycle that you're you're always<00:21:15.159> constantly<00:21:15.399> building<00:21:15.940> towards<00:21:16.240> a 00:21:16.320 --> 00:21:16.330 align:start position:0% always constantly building towards a 00:21:16.330 --> 00:21:19.830 align:start position:0% always constantly building towards a goal<00:21:16.720> and<00:21:16.990> you<00:21:17.769> know<00:21:18.009> waterfall<00:21:18.909> or<00:21:19.149> V<00:21:19.419> is<00:21:19.450> is 00:21:19.830 --> 00:21:19.840 align:start position:0% goal and you know waterfall or V is is 00:21:19.840 --> 00:21:21.930 align:start position:0% goal and you know waterfall or V is is like<00:21:20.139> the<00:21:20.350> long-term<00:21:20.620> push<00:21:21.159> like<00:21:21.519> the<00:21:21.639> idea 00:21:21.930 --> 00:21:21.940 align:start position:0% like the long-term push like the idea 00:21:21.940 --> 00:21:24.149 align:start position:0% like the long-term push like the idea from<00:21:22.179> start<00:21:22.509> to<00:21:22.659> finish<00:21:22.919> you<00:21:23.919> know<00:21:23.950> we're 00:21:24.149 --> 00:21:24.159 align:start position:0% from start to finish you know we're 00:21:24.159 --> 00:21:25.740 align:start position:0% from start to finish you know we're building<00:21:24.340> protocols<00:21:24.940> that<00:21:25.149> like<00:21:25.330> once<00:21:25.600> you 00:21:25.740 --> 00:21:25.750 align:start position:0% building protocols that like once you 00:21:25.750 --> 00:21:27.930 align:start position:0% building protocols that like once you build<00:21:25.929> you<00:21:26.649> probably<00:21:27.129> won't<00:21:27.370> want<00:21:27.519> to<00:21:27.700> spend 00:21:27.930 --> 00:21:27.940 align:start position:0% build you probably won't want to spend 00:21:27.940 --> 00:21:29.399 align:start position:0% build you probably won't want to spend you<00:21:28.149> know<00:21:28.210> the<00:21:28.480> ninety<00:21:28.779> percent<00:21:28.929> of<00:21:29.110> the<00:21:29.230> time 00:21:29.399 --> 00:21:29.409 align:start position:0% you know the ninety percent of the time 00:21:29.409 --> 00:21:31.169 align:start position:0% you know the ninety percent of the time you<00:21:29.529> spent<00:21:29.740> testing<00:21:30.190> and<00:21:30.399> do<00:21:30.730> that<00:21:30.850> over<00:21:31.149> again 00:21:31.169 --> 00:21:31.179 align:start position:0% you spent testing and do that over again 00:21:31.179 --> 00:21:34.019 align:start position:0% you spent testing and do that over again for<00:21:32.019> one<00:21:32.169> small<00:21:32.379> change<00:21:32.799> so<00:21:33.519> it<00:21:33.730> like<00:21:33.879> it 00:21:34.019 --> 00:21:34.029 align:start position:0% for one small change so it like it 00:21:34.029 --> 00:21:35.610 align:start position:0% for one small change so it like it really<00:21:34.269> pays<00:21:34.570> to<00:21:34.600> get<00:21:34.899> things<00:21:35.080> right<00:21:35.259> ahead<00:21:35.500> of 00:21:35.610 --> 00:21:35.620 align:start position:0% really pays to get things right ahead of 00:21:35.620 --> 00:21:37.379 align:start position:0% really pays to get things right ahead of time<00:21:35.799> so<00:21:36.009> just<00:21:36.549> building<00:21:36.820> that<00:21:37.000> into<00:21:37.299> your 00:21:37.379 --> 00:21:37.389 align:start position:0% time so just building that into your 00:21:37.389 --> 00:21:39.600 align:start position:0% time so just building that into your process<00:21:37.929> I<00:21:38.169> I<00:21:38.200> think<00:21:38.470> is<00:21:38.799> really<00:21:38.950> helpful<00:21:39.039> and 00:21:39.600 --> 00:21:39.610 align:start position:0% process I I think is really helpful and 00:21:39.610 --> 00:21:41.669 align:start position:0% process I I think is really helpful and you<00:21:39.820> can<00:21:39.970> still<00:21:40.120> use<00:21:40.360> agile<00:21:40.600> for<00:21:40.990> everyday<00:21:41.200> you 00:21:41.669 --> 00:21:41.679 align:start position:0% you can still use agile for everyday you 00:21:41.679 --> 00:21:43.529 align:start position:0% you can still use agile for everyday you know<00:21:41.799> everyday<00:21:42.159> use<00:21:42.370> that<00:21:42.639> that<00:21:43.029> keeps<00:21:43.269> people 00:21:43.529 --> 00:21:43.539 align:start position:0% know everyday use that that keeps people 00:21:43.539 --> 00:21:44.970 align:start position:0% know everyday use that that keeps people moving<00:21:43.750> in<00:21:43.899> a<00:21:43.960> specific<00:21:44.139> direction<00:21:44.710> this<00:21:44.799> is 00:21:44.970 --> 00:21:44.980 align:start position:0% moving in a specific direction this is 00:21:44.980 --> 00:21:47.159 align:start position:0% moving in a specific direction this is more<00:21:45.159> project<00:21:45.669> management<00:21:46.120> stuff<00:21:46.389> to<00:21:47.019> make 00:21:47.159 --> 00:21:47.169 align:start position:0% more project management stuff to make 00:21:47.169 --> 00:21:48.389 align:start position:0% more project management stuff to make sure<00:21:47.320> that<00:21:47.470> like<00:21:47.620> when<00:21:47.830> you're<00:21:47.950> at<00:21:48.070> the<00:21:48.159> end<00:21:48.279> of 00:21:48.389 --> 00:21:48.399 align:start position:0% sure that like when you're at the end of 00:21:48.399 --> 00:21:50.310 align:start position:0% sure that like when you're at the end of the<00:21:48.460> process<00:21:48.669> you<00:21:49.149> know<00:21:49.629> you<00:21:49.659> cross<00:21:50.049> your<00:21:50.289> eyes 00:21:50.310 --> 00:21:50.320 align:start position:0% the process you know you cross your eyes 00:21:50.320 --> 00:21:51.810 align:start position:0% the process you know you cross your eyes not<00:21:50.649> your<00:21:50.799> T's<00:21:50.980> and<00:21:51.009> all<00:21:51.250> the<00:21:51.370> technical 00:21:51.810 --> 00:21:51.820 align:start position:0% not your T's and all the technical 00:21:51.820 --> 00:21:53.519 align:start position:0% not your T's and all the technical things<00:21:52.059> but<00:21:52.330> you're<00:21:52.809> you're<00:21:53.049> totally<00:21:53.320> right 00:21:53.519 --> 00:21:53.529 align:start position:0% things but you're you're totally right 00:21:53.529 --> 00:21:55.129 align:start position:0% things but you're you're totally right you<00:21:53.710> have<00:21:53.919> to<00:21:54.100> have<00:21:54.250> the<00:21:54.429> feature<00:21:54.669> set 00:21:55.129 --> 00:21:55.139 align:start position:0% you have to have the feature set 00:21:55.139 --> 00:21:57.419 align:start position:0% you have to have the feature set identified<00:21:56.139> and<00:21:56.350> validated<00:21:56.379> by<00:21:56.889> the<00:21:57.010> market 00:21:57.419 --> 00:21:57.429 align:start position:0% identified and validated by the market 00:21:57.429 --> 00:21:57.870 align:start position:0% identified and validated by the market you're<00:21:57.490> ten 00:21:57.870 --> 00:21:57.880 align:start position:0% you're ten 00:21:57.880 --> 00:22:00.600 align:start position:0% you're ten operated<00:21:58.420> can<00:21:59.350> also<00:21:59.770> I<00:21:59.920> meet<00:22:00.220> a<00:22:00.250> little<00:22:00.520> bit 00:22:00.600 --> 00:22:00.610 align:start position:0% operated can also I meet a little bit 00:22:00.610 --> 00:22:02.940 align:start position:0% operated can also I meet a little bit because<00:22:01.090> I<00:22:01.420> believe<00:22:01.930> what<00:22:02.320> waterfall 00:22:02.940 --> 00:22:02.950 align:start position:0% because I believe what waterfall 00:22:02.950 --> 00:22:05.970 align:start position:0% because I believe what waterfall typically<00:22:03.640> emits<00:22:03.970> like<00:22:04.540> they<00:22:04.870> don't<00:22:05.320> do<00:22:05.560> that 00:22:05.970 --> 00:22:05.980 align:start position:0% typically emits like they don't do that 00:22:05.980 --> 00:22:08.190 align:start position:0% typically emits like they don't do that is<00:22:06.130> they<00:22:06.610> never<00:22:06.940> get<00:22:07.240> the<00:22:07.300> feedback<00:22:07.810> loop<00:22:07.990> on 00:22:08.190 --> 00:22:08.200 align:start position:0% is they never get the feedback loop on 00:22:08.200 --> 00:22:10.320 align:start position:0% is they never get the feedback loop on pre-production<00:22:08.980> stage<00:22:09.190> of<00:22:09.370> things<00:22:09.580> but<00:22:10.120> it 00:22:10.320 --> 00:22:10.330 align:start position:0% pre-production stage of things but it 00:22:10.330 --> 00:22:12.570 align:start position:0% pre-production stage of things but it can<00:22:10.660> be<00:22:11.200> done<00:22:11.380> and<00:22:11.620> it<00:22:11.770> works<00:22:11.980> perfectly<00:22:12.400> like 00:22:12.570 --> 00:22:12.580 align:start position:0% can be done and it works perfectly like 00:22:12.580 --> 00:22:14.280 align:start position:0% can be done and it works perfectly like you<00:22:12.670> can<00:22:12.820> show<00:22:13.060> like<00:22:13.330> I<00:22:13.360> don't<00:22:13.720> know<00:22:13.840> sketches 00:22:14.280 --> 00:22:14.290 align:start position:0% you can show like I don't know sketches 00:22:14.290 --> 00:22:15.780 align:start position:0% you can show like I don't know sketches of<00:22:14.410> your<00:22:14.530> interface<00:22:14.890> to<00:22:15.040> the<00:22:15.130> end<00:22:15.280> users<00:22:15.610> and 00:22:15.780 --> 00:22:15.790 align:start position:0% of your interface to the end users and 00:22:15.790 --> 00:22:17.220 align:start position:0% of your interface to the end users and get<00:22:15.970> feedbacks<00:22:16.330> or<00:22:16.450> something<00:22:16.750> like<00:22:16.810> that<00:22:16.900> and 00:22:17.220 --> 00:22:17.230 align:start position:0% get feedbacks or something like that and 00:22:17.230 --> 00:22:19.710 align:start position:0% get feedbacks or something like that and this<00:22:17.650> is<00:22:17.710> what<00:22:17.980> all<00:22:18.190> agile<00:22:18.910> is<00:22:19.060> about<00:22:19.270> we<00:22:19.480> find 00:22:19.710 --> 00:22:19.720 align:start position:0% this is what all agile is about we find 00:22:19.720 --> 00:22:23.550 align:start position:0% this is what all agile is about we find your<00:22:20.760> hypothesis<00:22:21.760> earlier<00:22:22.240> so<00:22:22.930> if<00:22:23.170> you<00:22:23.290> can 00:22:23.550 --> 00:22:23.560 align:start position:0% your hypothesis earlier so if you can 00:22:23.560 --> 00:22:25.260 align:start position:0% your hypothesis earlier so if you can incorporate<00:22:23.920> those<00:22:24.460> feedback<00:22:24.910> loops<00:22:25.120> in 00:22:25.260 --> 00:22:25.270 align:start position:0% incorporate those feedback loops in 00:22:25.270 --> 00:22:29.150 align:start position:0% incorporate those feedback loops in whatever<00:22:25.990> is<00:22:26.230> large<00:22:26.530> planning<00:22:27.460> really 00:22:29.150 --> 00:22:29.160 align:start position:0% whatever is large planning really 00:22:29.160 --> 00:22:31.710 align:start position:0% whatever is large planning really complicated<00:22:30.160> process<00:22:30.550> the<00:22:31.030> more<00:22:31.210> agile<00:22:31.510> you 00:22:31.710 --> 00:22:31.720 align:start position:0% complicated process the more agile you 00:22:31.720 --> 00:22:33.570 align:start position:0% complicated process the more agile you would<00:22:31.840> yet<00:22:32.110> even<00:22:32.380> if<00:22:32.500> it<00:22:32.620> looks<00:22:33.040> a<00:22:33.250> little<00:22:33.370> bit 00:22:33.570 --> 00:22:33.580 align:start position:0% would yet even if it looks a little bit 00:22:33.580 --> 00:22:35.280 align:start position:0% would yet even if it looks a little bit like<00:22:33.730> waterfall<00:22:34.330> yeah<00:22:34.510> we<00:22:34.690> understand<00:22:35.140> that 00:22:35.280 --> 00:22:35.290 align:start position:0% like waterfall yeah we understand that 00:22:35.290 --> 00:22:37.590 align:start position:0% like waterfall yeah we understand that it<00:22:35.500> has<00:22:35.530> stages<00:22:36.190> and<00:22:36.400> they<00:22:36.700> go<00:22:36.970> one<00:22:37.300> after 00:22:37.590 --> 00:22:37.600 align:start position:0% it has stages and they go one after 00:22:37.600 --> 00:22:39.330 align:start position:0% it has stages and they go one after another<00:22:37.630> when<00:22:38.320> when<00:22:38.560> you're<00:22:38.710> at<00:22:38.830> the<00:22:38.950> lambo 00:22:39.330 --> 00:22:39.340 align:start position:0% another when when you're at the lambo 00:22:39.340 --> 00:22:41.130 align:start position:0% another when when you're at the lambo stage<00:22:39.640> that's<00:22:40.150> that's<00:22:40.420> the<00:22:40.630> end<00:22:40.780> release 00:22:41.130 --> 00:22:41.140 align:start position:0% stage that's that's the end release 00:22:41.140 --> 00:22:42.690 align:start position:0% stage that's that's the end release that's<00:22:41.440> every<00:22:41.710> what<00:22:42.010> everyone's<00:22:42.550> been 00:22:42.690 --> 00:22:42.700 align:start position:0% that's every what everyone's been 00:22:42.700 --> 00:22:44.010 align:start position:0% that's every what everyone's been waiting<00:22:42.850> for<00:22:43.030> that's<00:22:43.360> when<00:22:43.510> real<00:22:43.660> people's 00:22:44.010 --> 00:22:44.020 align:start position:0% waiting for that's when real people's 00:22:44.020 --> 00:22:47.010 align:start position:0% waiting for that's when real people's money<00:22:44.230> enters<00:22:44.440> the<00:22:44.770> equation<00:22:44.860> so<00:22:45.610> you<00:22:46.300> know<00:22:46.750> I 00:22:47.010 --> 00:22:47.020 align:start position:0% money enters the equation so you know I 00:22:47.020 --> 00:22:49.110 align:start position:0% money enters the equation so you know I will<00:22:47.080> absolutely<00:22:47.380> stay<00:22:48.160> on<00:22:48.250> the<00:22:48.370> side<00:22:48.580> of<00:22:48.790> you 00:22:49.110 --> 00:22:49.120 align:start position:0% will absolutely stay on the side of you 00:22:49.120 --> 00:22:51.480 align:start position:0% will absolutely stay on the side of you know<00:22:49.210> handling<00:22:49.570> my<00:22:49.950> clients<00:22:50.950> money<00:22:51.160> and<00:22:51.400> my 00:22:51.480 --> 00:22:51.490 align:start position:0% know handling my clients money and my 00:22:51.490 --> 00:22:52.920 align:start position:0% know handling my clients money and my users<00:22:51.790> money<00:22:52.060> as<00:22:52.210> effectively<00:22:52.660> as<00:22:52.840> possible 00:22:52.920 --> 00:22:52.930 align:start position:0% users money as effectively as possible 00:22:52.930 --> 00:22:55.110 align:start position:0% users money as effectively as possible so<00:22:53.590> this<00:22:54.070> is<00:22:54.220> the<00:22:54.310> best<00:22:54.490> way<00:22:54.580> I<00:22:54.610> know<00:22:54.730> to<00:22:54.820> do 00:22:55.110 --> 00:22:55.120 align:start position:0% so this is the best way I know to do 00:22:55.120 --> 00:22:55.560 align:start position:0% so this is the best way I know to do that 00:22:55.560 --> 00:22:55.570 align:start position:0% that 00:22:55.570 --> 00:22:57.990 align:start position:0% that but<00:22:55.770> again<00:22:56.770> absolutely<00:22:57.430> you<00:22:57.550> have<00:22:57.580> to<00:22:57.880> get 00:22:57.990 --> 00:22:58.000 align:start position:0% but again absolutely you have to get 00:22:58.000 --> 00:22:59.520 align:start position:0% but again absolutely you have to get that<00:22:58.120> feedback<00:22:58.480> along<00:22:58.690> the<00:22:58.750> way<00:22:58.900> or<00:22:59.350> you're 00:22:59.520 --> 00:22:59.530 align:start position:0% that feedback along the way or you're 00:22:59.530 --> 00:23:00.660 align:start position:0% that feedback along the way or you're building<00:22:59.680> the<00:22:59.950> wrong<00:23:00.070> thing<00:23:00.430> you're<00:23:00.640> not 00:23:00.660 --> 00:23:00.670 align:start position:0% building the wrong thing you're not 00:23:00.670 --> 00:23:03.080 align:start position:0% building the wrong thing you're not doing<00:23:01.030> the<00:23:01.150> right<00:23:01.270> thing<00:23:01.450> and<00:23:01.570> to<00:23:01.690> begin<00:23:01.900> with 00:23:03.080 --> 00:23:03.090 align:start position:0% doing the right thing and to begin with 00:23:03.090 --> 00:23:06.060 align:start position:0% doing the right thing and to begin with yes<00:23:04.090> thank<00:23:04.990> you<00:23:05.020> for<00:23:05.230> the<00:23:05.290> presentation<00:23:05.680> guys 00:23:06.060 --> 00:23:06.070 align:start position:0% yes thank you for the presentation guys 00:23:06.070 --> 00:23:09.870 align:start position:0% yes thank you for the presentation guys we<00:23:06.910> talked<00:23:07.420> about<00:23:07.570> TDD<00:23:08.530> and<00:23:08.560> testing<00:23:09.160> and<00:23:09.640> I 00:23:09.870 --> 00:23:09.880 align:start position:0% we talked about TDD and testing and I 00:23:09.880 --> 00:23:11.900 align:start position:0% we talked about TDD and testing and I wanted<00:23:10.120> to<00:23:10.240> know<00:23:10.420> where<00:23:10.720> would<00:23:10.990> you<00:23:11.200> recommend 00:23:11.900 --> 00:23:11.910 align:start position:0% wanted to know where would you recommend 00:23:11.910 --> 00:23:15.540 align:start position:0% wanted to know where would you recommend testing<00:23:12.910> with<00:23:13.840> JavaScript<00:23:14.500> their<00:23:14.920> solidity 00:23:15.540 --> 00:23:15.550 align:start position:0% testing with JavaScript their solidity 00:23:15.550 --> 00:23:20.820 align:start position:0% testing with JavaScript their solidity is<00:23:15.940> it<00:23:16.690> more<00:23:16.900> like<00:23:17.110> you<00:23:19.290> like<00:23:20.290> like<00:23:20.590> he<00:23:20.710> was 00:23:20.820 --> 00:23:20.830 align:start position:0% is it more like you like like he was 00:23:20.830 --> 00:23:22.500 align:start position:0% is it more like you like like he was saying<00:23:21.040> just<00:23:21.250> never<00:23:21.520> use<00:23:21.700> solidity<00:23:22.060> tests 00:23:22.500 --> 00:23:22.510 align:start position:0% saying just never use solidity tests 00:23:22.510 --> 00:23:24.000 align:start position:0% saying just never use solidity tests they're<00:23:22.750> I<00:23:22.990> think<00:23:23.110> they're<00:23:23.500> a<00:23:23.530> terrible<00:23:23.770> idea 00:23:24.000 --> 00:23:24.010 align:start position:0% they're I think they're a terrible idea 00:23:24.010 --> 00:23:25.980 align:start position:0% they're I think they're a terrible idea you're<00:23:24.400> trying<00:23:24.670> to<00:23:24.760> use<00:23:24.940> the<00:23:25.120> thing<00:23:25.390> you're 00:23:25.980 --> 00:23:25.990 align:start position:0% you're trying to use the thing you're 00:23:25.990 --> 00:23:28.860 align:start position:0% you're trying to use the thing you're using<00:23:26.290> to<00:23:26.650> release<00:23:26.920> as<00:23:27.240> you<00:23:28.240> know<00:23:28.360> like<00:23:28.630> real 00:23:28.860 --> 00:23:28.870 align:start position:0% using to release as you know like real 00:23:28.870 --> 00:23:31.350 align:start position:0% using to release as you know like real live<00:23:29.170> code<00:23:29.560> and<00:23:30.550> developing<00:23:30.970> in<00:23:31.090> that<00:23:31.180> same 00:23:31.350 --> 00:23:31.360 align:start position:0% live code and developing in that same 00:23:31.360 --> 00:23:32.850 align:start position:0% live code and developing in that same framework<00:23:31.720> which<00:23:31.870> was<00:23:32.020> never<00:23:32.230> designed<00:23:32.740> to 00:23:32.850 --> 00:23:32.860 align:start position:0% framework which was never designed to 00:23:32.860 --> 00:23:35.340 align:start position:0% framework which was never designed to actually<00:23:33.250> do<00:23:33.460> testing<00:23:33.940> there<00:23:34.780> meant<00:23:34.960> there<00:23:35.200> is 00:23:35.340 --> 00:23:35.350 align:start position:0% actually do testing there meant there is 00:23:35.350 --> 00:23:37.140 align:start position:0% actually do testing there meant there is some<00:23:35.620> caveats<00:23:35.950> to<00:23:36.310> that<00:23:36.490> sometimes<00:23:36.940> there's 00:23:37.140 --> 00:23:37.150 align:start position:0% some caveats to that sometimes there's 00:23:37.150 --> 00:23:38.670 align:start position:0% some caveats to that sometimes there's just<00:23:37.210> something<00:23:37.810> that's<00:23:37.900> not<00:23:38.080> possible<00:23:38.440> like 00:23:38.670 --> 00:23:38.680 align:start position:0% just something that's not possible like 00:23:38.680 --> 00:23:41.070 align:start position:0% just something that's not possible like a<00:23:38.890> library<00:23:39.400> it's<00:23:40.060> really<00:23:40.420> hard<00:23:40.630> to<00:23:40.750> test<00:23:40.960> the 00:23:41.070 --> 00:23:41.080 align:start position:0% a library it's really hard to test the 00:23:41.080 --> 00:23:43.170 align:start position:0% a library it's really hard to test the library<00:23:41.500> without<00:23:41.860> like<00:23:42.040> some<00:23:42.220> sort<00:23:42.460> of<00:23:42.520> you 00:23:43.170 --> 00:23:43.180 align:start position:0% library without like some sort of you 00:23:43.180 --> 00:23:44.910 align:start position:0% library without like some sort of you know<00:23:43.240> infrastructure<00:23:43.960> around<00:23:44.080> that<00:23:44.470> but<00:23:44.680> use 00:23:44.910 --> 00:23:44.920 align:start position:0% know infrastructure around that but use 00:23:44.920 --> 00:23:46.680 align:start position:0% know infrastructure around that but use that<00:23:44.950> and<00:23:45.430> then<00:23:45.520> do<00:23:45.700> it<00:23:45.820> in<00:23:45.910> JavaScript<00:23:46.240> test 00:23:46.680 --> 00:23:46.690 align:start position:0% that and then do it in JavaScript test 00:23:46.690 --> 00:23:48.480 align:start position:0% that and then do it in JavaScript test where<00:23:46.900> it<00:23:47.020> has<00:23:47.140> a<00:23:47.170> more<00:23:47.440> more<00:23:47.920> feature<00:23:48.190> full 00:23:48.480 --> 00:23:48.490 align:start position:0% where it has a more more feature full 00:23:48.490 --> 00:23:50.910 align:start position:0% where it has a more more feature full test<00:23:48.750> testing<00:23:49.750> infrastructure<00:23:50.320> or<00:23:50.470> use 00:23:50.910 --> 00:23:50.920 align:start position:0% test testing infrastructure or use 00:23:50.920 --> 00:23:55.680 align:start position:0% test testing infrastructure or use Python<00:23:51.370> I<00:23:53.310> hope<00:23:54.310> people<00:23:54.490> writing<00:23:55.240> tests<00:23:55.510> in 00:23:55.680 --> 00:23:55.690 align:start position:0% Python I hope people writing tests in 00:23:55.690 --> 00:23:57.750 align:start position:0% Python I hope people writing tests in solidity<00:23:56.080> where<00:23:56.560> you<00:23:56.800> have<00:23:56.920> a<00:23:56.950> team<00:23:57.460> of<00:23:57.610> people 00:23:57.750 --> 00:23:57.760 align:start position:0% solidity where you have a team of people 00:23:57.760 --> 00:23:59.970 align:start position:0% solidity where you have a team of people working<00:23:58.060> on<00:23:58.390> a<00:23:58.420> contract<00:23:58.930> and<00:23:59.230> you 00:23:59.970 --> 00:23:59.980 align:start position:0% working on a contract and you 00:23:59.980 --> 00:24:02.220 align:start position:0% working on a contract and you right<00:24:00.160> like<00:24:00.340> you<00:24:00.730> know<00:24:00.820> people<00:24:01.600> are<00:24:01.750> focusing 00:24:02.220 --> 00:24:02.230 align:start position:0% right like you know people are focusing 00:24:02.230 --> 00:24:04.440 align:start position:0% right like you know people are focusing on<00:24:02.350> a<00:24:02.380> function<00:24:02.919> and<00:24:03.760> you<00:24:03.790> want<00:24:04.000> to<00:24:04.059> pass<00:24:04.240> it<00:24:04.419> so 00:24:04.440 --> 00:24:04.450 align:start position:0% on a function and you want to pass it so 00:24:04.450 --> 00:24:06.390 align:start position:0% on a function and you want to pass it so well<00:24:04.840> you<00:24:05.049> can<00:24:05.590> write<00:24:05.740> this<00:24:05.919> without<00:24:06.220> that 00:24:06.390 --> 00:24:06.400 align:start position:0% well you can write this without that 00:24:06.400 --> 00:24:07.799 align:start position:0% well you can write this without that it's<00:24:06.760> okay<00:24:06.940> thank<00:24:07.179> you<00:24:07.270> there's<00:24:07.630> always 00:24:07.799 --> 00:24:07.809 align:start position:0% it's okay thank you there's always 00:24:07.809 --> 00:24:12.120 align:start position:0% it's okay thank you there's always nuance<00:24:08.230> yeah<00:24:10.590> couple<00:24:11.590> behind 00:24:12.120 --> 00:24:12.130 align:start position:0% nuance yeah couple behind 00:24:12.130 --> 00:24:17.039 align:start position:0% nuance yeah couple behind I<00:24:12.840> was<00:24:13.840> hoping<00:24:14.080> could<00:24:14.679> you<00:24:14.830> clarify<00:24:15.760> or<00:24:16.660> the 00:24:17.039 --> 00:24:17.049 align:start position:0% I was hoping could you clarify or the 00:24:17.049 --> 00:24:19.320 align:start position:0% I was hoping could you clarify or the tools<00:24:17.290> around<00:24:17.440> traceability<00:24:17.919> or<00:24:18.250> their<00:24:18.669> repos 00:24:19.320 --> 00:24:19.330 align:start position:0% tools around traceability or their repos 00:24:19.330 --> 00:24:21.690 align:start position:0% tools around traceability or their repos that<00:24:19.660> are<00:24:19.720> open-source<00:24:19.929> you<00:24:20.169> think<00:24:20.700> apples 00:24:21.690 --> 00:24:21.700 align:start position:0% that are open-source you think apples 00:24:21.700 --> 00:24:23.850 align:start position:0% that are open-source you think apples I'm<00:24:22.000> working<00:24:22.690> on<00:24:22.780> some<00:24:23.080> particular<00:24:23.260> tools<00:24:23.710> I 00:24:23.850 --> 00:24:23.860 align:start position:0% I'm working on some particular tools I 00:24:23.860 --> 00:24:25.860 align:start position:0% I'm working on some particular tools I have<00:24:24.490> like<00:24:24.640> a<00:24:24.669> BIM<00:24:24.910> plug-in<00:24:25.330> that<00:24:25.510> like<00:24:25.690> will 00:24:25.860 --> 00:24:25.870 align:start position:0% have like a BIM plug-in that like will 00:24:25.870 --> 00:24:28.320 align:start position:0% have like a BIM plug-in that like will help<00:24:26.110> you<00:24:26.230> like<00:24:26.850> what<00:24:27.850> I<00:24:27.880> was<00:24:28.090> talking<00:24:28.299> about 00:24:28.320 --> 00:24:28.330 align:start position:0% help you like what I was talking about 00:24:28.330 --> 00:24:29.820 align:start position:0% help you like what I was talking about with<00:24:28.510> the<00:24:28.570> hashing<00:24:28.960> thing<00:24:29.169> so<00:24:29.470> that's<00:24:29.679> really 00:24:29.820 --> 00:24:29.830 align:start position:0% with the hashing thing so that's really 00:24:29.830 --> 00:24:32.490 align:start position:0% with the hashing thing so that's really useful<00:24:30.179> once<00:24:31.179> you<00:24:31.240> very<00:24:31.510> greed<00:24:32.080> upon<00:24:32.320> your 00:24:32.490 --> 00:24:32.500 align:start position:0% useful once you very greed upon your 00:24:32.500 --> 00:24:33.960 align:start position:0% useful once you very greed upon your list<00:24:32.710> of<00:24:32.799> requirements<00:24:33.190> you<00:24:33.760> know<00:24:33.850> they 00:24:33.960 --> 00:24:33.970 align:start position:0% list of requirements you know they 00:24:33.970 --> 00:24:35.070 align:start position:0% list of requirements you know they should<00:24:34.030> never<00:24:34.270> change<00:24:34.510> the<00:24:34.780> hash<00:24:34.900> should 00:24:35.070 --> 00:24:35.080 align:start position:0% should never change the hash should 00:24:35.080 --> 00:24:36.870 align:start position:0% should never change the hash should never<00:24:35.230> change<00:24:35.470> and<00:24:35.890> if<00:24:36.220> you<00:24:36.309> use<00:24:36.429> that<00:24:36.640> hash 00:24:36.870 --> 00:24:36.880 align:start position:0% never change and if you use that hash 00:24:36.880 --> 00:24:38.730 align:start position:0% never change and if you use that hash and<00:24:37.210> like<00:24:37.360> you<00:24:37.510> have<00:24:37.660> a<00:24:37.690> really<00:24:38.020> big<00:24:38.230> codebase 00:24:38.730 --> 00:24:38.740 align:start position:0% and like you have a really big codebase 00:24:38.740 --> 00:24:40.440 align:start position:0% and like you have a really big codebase and<00:24:39.040> you<00:24:39.520> start<00:24:39.760> putting<00:24:39.910> like<00:24:40.150> you<00:24:40.330> know<00:24:40.419> a 00:24:40.440 --> 00:24:40.450 align:start position:0% and you start putting like you know a 00:24:40.450 --> 00:24:43.590 align:start position:0% and you start putting like you know a trek<00:24:40.900> hash<00:24:41.490> this<00:24:42.490> does<00:24:42.700> blah<00:24:42.910> blah<00:24:43.059> blah<00:24:43.240> a 00:24:43.590 --> 00:24:43.600 align:start position:0% trek hash this does blah blah blah a 00:24:43.600 --> 00:24:45.810 align:start position:0% trek hash this does blah blah blah a part<00:24:44.020> of<00:24:44.080> that<00:24:44.200> requirement<00:24:44.740> and<00:24:44.919> and<00:24:45.610> then 00:24:45.810 --> 00:24:45.820 align:start position:0% part of that requirement and and then 00:24:45.820 --> 00:24:47.340 align:start position:0% part of that requirement and and then like<00:24:46.150> further<00:24:46.390> down<00:24:46.660> the<00:24:46.750> line<00:24:46.900> you've<00:24:47.140> sort 00:24:47.340 --> 00:24:47.350 align:start position:0% like further down the line you've sort 00:24:47.350 --> 00:24:48.630 align:start position:0% like further down the line you've sort of<00:24:47.380> forgotten<00:24:47.830> everything<00:24:48.010> you've<00:24:48.280> ever<00:24:48.340> done 00:24:48.630 --> 00:24:48.640 align:start position:0% of forgotten everything you've ever done 00:24:48.640 --> 00:24:50.760 align:start position:0% of forgotten everything you've ever done behind<00:24:49.570> the<00:24:49.780> scenes<00:24:49.840> and<00:24:50.260> someone's<00:24:50.559> like<00:24:50.679> oh 00:24:50.760 --> 00:24:50.770 align:start position:0% behind the scenes and someone's like oh 00:24:50.770 --> 00:24:52.440 align:start position:0% behind the scenes and someone's like oh well<00:24:51.040> this<00:24:51.309> requirement<00:24:51.790> is<00:24:51.970> wrong<00:24:52.179> we 00:24:52.440 --> 00:24:52.450 align:start position:0% well this requirement is wrong we 00:24:52.450 --> 00:24:54.090 align:start position:0% well this requirement is wrong we validated<00:24:52.929> with<00:24:53.049> the<00:24:53.110> market<00:24:53.440> those<00:24:53.830> are<00:24:53.950> bad 00:24:54.090 --> 00:24:54.100 align:start position:0% validated with the market those are bad 00:24:54.100 --> 00:24:55.409 align:start position:0% validated with the market those are bad assumption<00:24:54.640> we<00:24:54.730> need<00:24:54.880> to<00:24:55.000> change<00:24:55.179> these 00:24:55.409 --> 00:24:55.419 align:start position:0% assumption we need to change these 00:24:55.419 --> 00:24:57.750 align:start position:0% assumption we need to change these features<00:24:55.919> now<00:24:56.919> you're<00:24:57.100> like<00:24:57.220> okay<00:24:57.460> what<00:24:57.610> do<00:24:57.669> I 00:24:57.750 --> 00:24:57.760 align:start position:0% features now you're like okay what do I 00:24:57.760 --> 00:25:00.360 align:start position:0% features now you're like okay what do I have<00:24:57.850> to<00:24:58.000> go<00:24:58.090> update<00:24:58.419> super<00:24:59.200> easy<00:24:59.380> I<00:24:59.710> now<00:25:00.100> go 00:25:00.360 --> 00:25:00.370 align:start position:0% have to go update super easy I now go 00:25:00.370 --> 00:25:02.340 align:start position:0% have to go update super easy I now go change<00:25:00.790> of<00:25:00.910> the<00:25:00.970> hash<00:25:01.120> and<00:25:01.360> see<00:25:01.570> where<00:25:01.750> all<00:25:02.140> the 00:25:02.340 --> 00:25:02.350 align:start position:0% change of the hash and see where all the 00:25:02.350 --> 00:25:03.750 align:start position:0% change of the hash and see where all the places<00:25:02.590> where<00:25:02.860> the<00:25:02.919> old<00:25:03.070> hash<00:25:03.280> were<00:25:03.460> in<00:25:03.549> place 00:25:03.750 --> 00:25:03.760 align:start position:0% places where the old hash were in place 00:25:03.760 --> 00:25:05.400 align:start position:0% places where the old hash were in place that<00:25:03.790> now<00:25:04.210> are<00:25:04.480> mismatched<00:25:04.929> with<00:25:05.169> the<00:25:05.290> new 00:25:05.400 --> 00:25:05.410 align:start position:0% that now are mismatched with the new 00:25:05.410 --> 00:25:08.250 align:start position:0% that now are mismatched with the new hash<00:25:06.150> pretty<00:25:07.150> cool<00:25:07.360> so<00:25:07.540> I'm<00:25:07.780> working<00:25:08.020> on<00:25:08.140> a 00:25:08.250 --> 00:25:08.260 align:start position:0% hash pretty cool so I'm working on a 00:25:08.260 --> 00:25:09.690 align:start position:0% hash pretty cool so I'm working on a tool<00:25:08.410> like<00:25:08.590> that<00:25:08.830> but<00:25:08.980> there's<00:25:09.130> no<00:25:09.220> real<00:25:09.429> tool 00:25:09.690 --> 00:25:09.700 align:start position:0% tool like that but there's no real tool 00:25:09.700 --> 00:25:11.520 align:start position:0% tool like that but there's no real tool tool<00:25:10.660> set<00:25:10.809> in<00:25:10.870> the<00:25:10.929> market<00:25:11.200> so<00:25:11.380> if<00:25:11.440> you're 00:25:11.520 --> 00:25:11.530 align:start position:0% tool set in the market so if you're 00:25:11.530 --> 00:25:19.020 align:start position:0% tool set in the market so if you're interested<00:25:11.890> to<00:25:11.919> come<00:25:12.040> talk<00:25:12.220> to<00:25:12.250> me<00:25:17.940> hey<00:25:18.940> guys 00:25:19.020 --> 00:25:19.030 align:start position:0% interested to come talk to me hey guys 00:25:19.030 --> 00:25:22.260 align:start position:0% interested to come talk to me hey guys thanks<00:25:19.650> I'm<00:25:20.650> a<00:25:20.710> bit<00:25:21.160> curious<00:25:21.309> you've<00:25:21.820> provided 00:25:22.260 --> 00:25:22.270 align:start position:0% thanks I'm a bit curious you've provided 00:25:22.270 --> 00:25:24.659 align:start position:0% thanks I'm a bit curious you've provided some<00:25:22.480> very<00:25:22.660> awesome<00:25:22.720> technical<00:25:23.440> points<00:25:23.950> one 00:25:24.659 --> 00:25:24.669 align:start position:0% some very awesome technical points one 00:25:24.669 --> 00:25:26.340 align:start position:0% some very awesome technical points one thing<00:25:24.820> that<00:25:24.970> I'm<00:25:25.150> very<00:25:25.179> curious<00:25:25.660> about<00:25:25.750> is<00:25:25.990> how 00:25:26.340 --> 00:25:26.350 align:start position:0% thing that I'm very curious about is how 00:25:26.350 --> 00:25:28.169 align:start position:0% thing that I'm very curious about is how do<00:25:26.410> you<00:25:26.530> actually<00:25:26.710> develop<00:25:27.190> a<00:25:27.640> kind<00:25:28.030> of 00:25:28.169 --> 00:25:28.179 align:start position:0% do you actually develop a kind of 00:25:28.179 --> 00:25:30.630 align:start position:0% do you actually develop a kind of company<00:25:28.690> culture<00:25:28.780> of<00:25:29.380> appreciating<00:25:30.160> the 00:25:30.630 --> 00:25:30.640 align:start position:0% company culture of appreciating the 00:25:30.640 --> 00:25:32.970 align:start position:0% company culture of appreciating the importance<00:25:31.090> of<00:25:31.330> these<00:25:31.450> sorts<00:25:31.750> of<00:25:31.809> things<00:25:31.980> both 00:25:32.970 --> 00:25:32.980 align:start position:0% importance of these sorts of things both 00:25:32.980 --> 00:25:34.770 align:start position:0% importance of these sorts of things both from<00:25:33.220> like<00:25:33.400> the<00:25:33.610> technical<00:25:34.210> standpoint<00:25:34.480> and 00:25:34.770 --> 00:25:34.780 align:start position:0% from like the technical standpoint and 00:25:34.780 --> 00:25:36.330 align:start position:0% from like the technical standpoint and perhaps<00:25:35.020> the<00:25:35.169> non-technical<00:25:35.590> people<00:25:36.100> in<00:25:36.220> your 00:25:36.330 --> 00:25:36.340 align:start position:0% perhaps the non-technical people in your 00:25:36.340 --> 00:25:42.090 align:start position:0% perhaps the non-technical people in your team<00:25:37.980> like<00:25:39.660> basic<00:25:40.660> thing<00:25:40.900> I<00:25:41.140> like<00:25:41.950> to 00:25:42.090 --> 00:25:42.100 align:start position:0% team like basic thing I like to 00:25:42.100 --> 00:25:45.120 align:start position:0% team like basic thing I like to encourage<00:25:42.340> and<00:25:42.640> like<00:25:43.030> I<00:25:43.210> see<00:25:43.630> really<00:25:44.169> helpful 00:25:45.120 --> 00:25:45.130 align:start position:0% encourage and like I see really helpful 00:25:45.130 --> 00:25:47.970 align:start position:0% encourage and like I see really helpful in<00:25:45.309> encouraging<00:25:45.490> that<00:25:46.059> is<00:25:46.299> use<00:25:46.960> robots<00:25:47.530> as<00:25:47.710> as 00:25:47.970 --> 00:25:47.980 align:start position:0% in encouraging that is use robots as as 00:25:47.980 --> 00:25:51.210 align:start position:0% in encouraging that is use robots as as long<00:25:48.220> as<00:25:48.460> you<00:25:48.580> can<00:25:48.820> like<00:25:49.540> no<00:25:50.200> one<00:25:50.440> like<00:25:50.679> when 00:25:51.210 --> 00:25:51.220 align:start position:0% long as you can like no one like when 00:25:51.220 --> 00:25:53.130 align:start position:0% long as you can like no one like when you<00:25:51.490> go<00:25:51.820> in<00:25:52.090> into<00:25:52.390> the<00:25:52.480> pull<00:25:52.630> request<00:25:52.929> and<00:25:53.020> you 00:25:53.130 --> 00:25:53.140 align:start position:0% you go in into the pull request and you 00:25:53.140 --> 00:25:55.500 align:start position:0% you go in into the pull request and you said<00:25:53.320> no<00:25:53.470> this<00:25:53.830> is<00:25:54.100> just<00:25:54.460> not<00:25:54.910> testing<00:25:55.330> this 00:25:55.500 --> 00:25:55.510 align:start position:0% said no this is just not testing this 00:25:55.510 --> 00:25:56.970 align:start position:0% said no this is just not testing this requirement<00:25:55.840> or<00:25:56.169> something<00:25:56.440> like<00:25:56.500> that 00:25:56.970 --> 00:25:56.980 align:start position:0% requirement or something like that 00:25:56.980 --> 00:25:59.190 align:start position:0% requirement or something like that you're<00:25:57.280> not<00:25:57.460> like<00:25:58.030> you<00:25:58.240> enforcing<00:25:58.690> it<00:25:58.809> by<00:25:58.929> hand 00:25:59.190 --> 00:25:59.200 align:start position:0% you're not like you enforcing it by hand 00:25:59.200 --> 00:26:01.350 align:start position:0% you're not like you enforcing it by hand and<00:25:59.380> people<00:25:59.440> start<00:25:59.950> arguing<00:26:00.309> with<00:26:00.400> you<00:26:00.669> but<00:26:00.880> no 00:26:01.350 --> 00:26:01.360 align:start position:0% and people start arguing with you but no 00:26:01.360 --> 00:26:03.030 align:start position:0% and people start arguing with you but no one<00:26:01.510> will<00:26:01.630> ever<00:26:01.690> argue<00:26:02.320> with<00:26:02.470> robot<00:26:02.799> because 00:26:03.030 --> 00:26:03.040 align:start position:0% one will ever argue with robot because 00:26:03.040 --> 00:26:05.070 align:start position:0% one will ever argue with robot because that's<00:26:03.220> sort<00:26:03.429> of<00:26:03.490> stupid<00:26:03.940> and<00:26:04.090> this<00:26:04.750> is<00:26:04.900> how 00:26:05.070 --> 00:26:05.080 align:start position:0% that's sort of stupid and this is how 00:26:05.080 --> 00:26:07.169 align:start position:0% that's sort of stupid and this is how you<00:26:05.140> basically<00:26:05.500> put<00:26:06.100> the<00:26:06.280> baseline<00:26:06.760> on<00:26:06.970> any 00:26:07.169 --> 00:26:07.179 align:start position:0% you basically put the baseline on any 00:26:07.179 --> 00:26:09.149 align:start position:0% you basically put the baseline on any culture<00:26:07.630> of<00:26:07.780> a<00:26:07.840> culture<00:26:08.140> of<00:26:08.169> tests<00:26:08.679> on<00:26:08.830> the 00:26:09.149 --> 00:26:09.159 align:start position:0% culture of a culture of tests on the 00:26:09.159 --> 00:26:11.430 align:start position:0% culture of a culture of tests on the culture<00:26:09.429> of<00:26:09.460> code<00:26:09.820> style<00:26:10.150> and<00:26:10.450> so<00:26:10.630> on<00:26:10.780> just<00:26:10.809> use 00:26:11.430 --> 00:26:11.440 align:start position:0% culture of code style and so on just use 00:26:11.440 --> 00:26:12.880 align:start position:0% culture of code style and so on just use the<00:26:11.650> robots<00:26:12.010> to<00:26:12.220> the<00:26:12.429> like 00:26:12.880 --> 00:26:12.890 align:start position:0% the robots to the like 00:26:12.890 --> 00:26:17.230 align:start position:0% the robots to the like maximum<00:26:13.280> extent<00:26:13.900> after<00:26:14.900> that<00:26:15.790> probably<00:26:16.790> just 00:26:17.230 --> 00:26:17.240 align:start position:0% maximum extent after that probably just 00:26:17.240 --> 00:26:19.210 align:start position:0% maximum extent after that probably just talking<00:26:17.660> with<00:26:17.930> people<00:26:17.990> like<00:26:18.440> explaining<00:26:18.860> why 00:26:19.210 --> 00:26:19.220 align:start position:0% talking with people like explaining why 00:26:19.220 --> 00:26:21.340 align:start position:0% talking with people like explaining why you're<00:26:19.400> doing<00:26:19.640> that<00:26:19.670> in<00:26:20.120> before<00:26:20.390> will<00:26:21.110> help 00:26:21.340 --> 00:26:21.350 align:start position:0% you're doing that in before will help 00:26:21.350 --> 00:26:23.230 align:start position:0% you're doing that in before will help like<00:26:21.620> they<00:26:21.770> will<00:26:21.920> not<00:26:22.160> they<00:26:22.400> will<00:26:22.670> agree<00:26:23.060> and 00:26:23.230 --> 00:26:23.240 align:start position:0% like they will not they will agree and 00:26:23.240 --> 00:26:25.020 align:start position:0% like they will not they will agree and then<00:26:23.390> we<00:26:23.630> will<00:26:23.840> feel<00:26:24.020> bad<00:26:24.260> if<00:26:24.440> we<00:26:24.530> will<00:26:24.680> try<00:26:24.950> to 00:26:25.020 --> 00:26:25.030 align:start position:0% then we will feel bad if we will try to 00:26:25.030 --> 00:26:28.090 align:start position:0% then we will feel bad if we will try to like<00:26:26.030> push<00:26:26.240> you<00:26:26.480> away<00:26:26.750> from<00:26:26.990> your<00:26:27.290> various<00:26:27.590> and 00:26:28.090 --> 00:26:28.100 align:start position:0% like push you away from your various and 00:26:28.100 --> 00:26:29.920 align:start position:0% like push you away from your various and I<00:26:28.250> think<00:26:28.550> at<00:26:28.640> the<00:26:28.760> end<00:26:28.790> of<00:26:28.940> the<00:26:29.090> day<00:26:29.270> it's<00:26:29.630> it's 00:26:29.920 --> 00:26:29.930 align:start position:0% I think at the end of the day it's it's 00:26:29.930 --> 00:26:31.600 align:start position:0% I think at the end of the day it's it's either<00:26:30.140> gonna<00:26:30.350> come<00:26:30.650> from<00:26:30.860> a<00:26:30.950> cultural<00:26:31.370> shift 00:26:31.600 --> 00:26:31.610 align:start position:0% either gonna come from a cultural shift 00:26:31.610 --> 00:26:35.080 align:start position:0% either gonna come from a cultural shift before<00:26:32.120> a<00:26:32.150> problem<00:26:32.750> happens<00:26:33.080> or<00:26:33.440> after<00:26:33.590> so<00:26:34.100> I 00:26:35.080 --> 00:26:35.090 align:start position:0% before a problem happens or after so I 00:26:35.090 --> 00:26:36.580 align:start position:0% before a problem happens or after so I think<00:26:35.330> a<00:26:35.570> lot<00:26:35.690> of<00:26:35.840> people<00:26:36.050> in<00:26:36.110> the<00:26:36.200> space<00:26:36.380> look 00:26:36.580 --> 00:26:36.590 align:start position:0% think a lot of people in the space look 00:26:36.590 --> 00:26:37.720 align:start position:0% think a lot of people in the space look at<00:26:36.680> the<00:26:36.740> problems<00:26:37.040> that<00:26:37.160> happen<00:26:37.430> and<00:26:37.580> think 00:26:37.720 --> 00:26:37.730 align:start position:0% at the problems that happen and think 00:26:37.730 --> 00:26:39.190 align:start position:0% at the problems that happen and think like<00:26:37.910> oh<00:26:38.060> those<00:26:38.210> people<00:26:38.390> were<00:26:38.630> stupid<00:26:38.900> they 00:26:39.190 --> 00:26:39.200 align:start position:0% like oh those people were stupid they 00:26:39.200 --> 00:26:40.330 align:start position:0% like oh those people were stupid they didn't<00:26:39.470> think<00:26:39.620> ahead<00:26:39.770> of<00:26:39.920> time 00:26:40.330 --> 00:26:40.340 align:start position:0% didn't think ahead of time 00:26:40.340 --> 00:26:41.920 align:start position:0% didn't think ahead of time no<00:26:40.670> they<00:26:40.880> just<00:26:41.090> weren't<00:26:41.240> aware<00:26:41.510> of<00:26:41.570> it<00:26:41.750> they 00:26:41.920 --> 00:26:41.930 align:start position:0% no they just weren't aware of it they 00:26:41.930 --> 00:26:43.420 align:start position:0% no they just weren't aware of it they weren't<00:26:42.080> thinking<00:26:42.500> along<00:26:42.710> those<00:26:42.890> lines<00:26:43.190> and 00:26:43.420 --> 00:26:43.430 align:start position:0% weren't thinking along those lines and 00:26:43.430 --> 00:26:45.580 align:start position:0% weren't thinking along those lines and they've<00:26:43.580> bathed<00:26:44.420> drastically<00:26:45.080> changed<00:26:45.500> how 00:26:45.580 --> 00:26:45.590 align:start position:0% they've bathed drastically changed how 00:26:45.590 --> 00:26:46.990 align:start position:0% they've bathed drastically changed how they've<00:26:45.800> approached<00:26:46.190> the<00:26:46.370> problem<00:26:46.760> and<00:26:46.910> we 00:26:46.990 --> 00:26:47.000 align:start position:0% they've approached the problem and we 00:26:47.000 --> 00:26:48.910 align:start position:0% they've approached the problem and we should<00:26:47.030> learn<00:26:47.390> from<00:26:47.450> them<00:26:47.870> because<00:26:48.470> you're 00:26:48.910 --> 00:26:48.920 align:start position:0% should learn from them because you're 00:26:48.920 --> 00:26:50.260 align:start position:0% should learn from them because you're gonna<00:26:49.010> repeat<00:26:49.310> the<00:26:49.460> same<00:26:49.640> mistakes<00:26:50.030> if<00:26:50.180> you 00:26:50.260 --> 00:26:50.270 align:start position:0% gonna repeat the same mistakes if you 00:26:50.270 --> 00:26:59.510 align:start position:0% gonna repeat the same mistakes if you don't<00:26:50.420> take<00:26:50.540> that<00:26:50.720> seriously 00:26:59.510 --> 00:26:59.520 align:start position:0% 00:26:59.520 --> 00:27:01.580 align:start position:0% you