| Topic | Presenter | Summary | Duration |
| -------------------------------------- | ---------- | ---------------------------------------------------------------------------------------------------------------------- | -------- |
| Expectations of a Developer at Clarity | Brandon M. | This is a presentation done by Brandon M. during a Friday Training that covers Expectations of a Developer at Clarity. | 1:22:05 |00:00:07.410 --> 00:00:10.560 Expectations of a developer clarity.00:00:10.560 --> 00:00:13.270 Alright, so this first slide here,00:00:13.270 --> 00:00:18.674 UM, let's kick it off with Alex.00:00:18.680 --> 00:00:19.790 Can you see my screen buddy?00:00:19.790 --> 00:00:23.022 Can you read these for me? Yeah, sure.00:00:23.022 --> 00:00:24.886 Uh, prioritize understanding the00:00:24.886 --> 00:00:27.711 languages you'll be using more frequently00:00:27.711 --> 00:00:29.495 and understand your deficiencies00:00:29.495 --> 00:00:32.079 and where you need to improve.00:00:32.080 --> 00:00:33.216 If working on staff,00:00:33.216 --> 00:00:34.636 understand what the features are,00:00:34.640 --> 00:00:36.096 what the site does out of box,00:00:36.100 --> 00:00:38.011 and how the app settings can alter00:00:38.011 --> 00:00:39.329 the functionality of the site.00:00:39.330 --> 00:00:42.354 For a list of apps settings, go to Seth.00:00:42.354 --> 00:00:45.230 Dash config slash pet thing.00:00:45.230 --> 00:00:47.510 Collaborate with other developers,00:00:47.510 --> 00:00:47.806 particularly,00:00:47.806 --> 00:00:49.878 but in the back end to learn00:00:49.878 --> 00:00:51.627 snippets of what you don't know,00:00:51.630 --> 00:00:52.834 which will increase efficiency.00:00:52.834 --> 00:00:54.038 Teamwork makes the dream.00:00:56.480 --> 00:00:59.240 Awesome thank you man. Uh yeah,00:00:59.240 --> 00:01:01.430 I'm sorry. Oh no, go ahead, Brendan.00:01:04.000 --> 00:01:06.638 I was just gonna say #2 is.00:01:06.638 --> 00:01:08.822 So much bigger than you would00:01:08.822 --> 00:01:11.492 expect for starting that at the00:01:11.492 --> 00:01:13.817 company to come out intimidating,00:01:13.820 --> 00:01:16.190 to see that immediately, but.00:01:16.190 --> 00:01:17.978 Uh, I agree with the concept.00:01:21.050 --> 00:01:23.270 Yeah, thank you. Uhm yeah.00:01:23.270 --> 00:01:24.936 So these are just sort of some00:01:24.936 --> 00:01:26.289 baseline things as a developer.00:01:26.290 --> 00:01:30.427 Uhm, I think. Understanding what your00:01:30.427 --> 00:01:33.001 deficiencies are is is crucial to00:01:33.001 --> 00:01:34.774 obviously you laying out and thinking00:01:34.774 --> 00:01:37.400 of a of a of an improvement path.00:01:37.400 --> 00:01:40.480 The career PATH app settings I think,00:01:40.480 --> 00:01:43.152 as Brendan kind of alluded to there have00:01:43.152 --> 00:01:45.287 gotten everybody at one point or another.00:01:45.290 --> 00:01:46.706 And then the big one here for me,00:01:46.710 --> 00:01:49.095 where I think we as a team need to00:01:49.095 --> 00:01:51.472 get much better is collaborating00:01:51.472 --> 00:01:52.999 with other developers.00:01:53.000 --> 00:01:54.968 I would say if you're on,00:01:54.970 --> 00:01:57.028 you know during Sprint planning you00:01:57.028 --> 00:01:59.922 look at a task and you look at that00:01:59.922 --> 00:02:01.542 user story and another developer00:02:01.542 --> 00:02:04.098 has a task on that same user story.00:02:04.100 --> 00:02:05.948 Like before you even leave Sprint00:02:05.948 --> 00:02:07.779 planning or right after you leave,00:02:07.780 --> 00:02:08.780 you should ping that developer00:02:08.780 --> 00:02:10.422 and be like hey I see we both00:02:10.422 --> 00:02:11.616 have tasks for this user story.00:02:11.620 --> 00:02:13.318 We should work on that together.00:02:13.320 --> 00:02:15.049 Like what day do you think would00:02:15.049 --> 00:02:16.944 work for that or or when do you00:02:16.944 --> 00:02:18.689 plan on working that in the Sprint?00:02:18.690 --> 00:02:20.229 I think we need to get a lot better00:02:20.229 --> 00:02:21.895 at that in general on the dev team.00:02:29.620 --> 00:02:30.800 So that those snippets.00:02:33.380 --> 00:02:37.804 Alright, uh, let's see, let's do a.00:02:37.810 --> 00:02:38.642 I guess Brandon flirty.00:02:38.642 --> 00:02:40.152 Can you read this one? It's a lot.00:02:40.152 --> 00:02:41.520 We could split it into a couple people,00:02:41.520 --> 00:02:43.140 but start with the first one.00:02:45.500 --> 00:02:48.279 Did you know we are only employed00:02:48.279 --> 00:02:50.346 because we have clients who00:02:50.346 --> 00:02:52.716 pay us to work on projects?00:02:52.720 --> 00:02:55.480 I love Brendan's general sarcasm,00:02:55.480 --> 00:02:57.664 so that's why I wanted him to00:02:57.664 --> 00:02:59.690 read that one fit perfectly.00:02:59.690 --> 00:03:01.506 It's a little sarcastic for that first one,00:03:01.510 --> 00:03:03.558 but I wanted to kind of point that00:03:03.558 --> 00:03:05.552 out because obviously like our00:03:05.552 --> 00:03:08.022 products are super important and00:03:08.022 --> 00:03:10.382 critical and we all want to make the00:03:10.382 --> 00:03:12.379 product better so that you know the00:03:12.379 --> 00:03:14.440 projects go better in the long term.00:03:14.440 --> 00:03:16.810 However, you know when it comes00:03:16.810 --> 00:03:18.390 down to brass tacks,00:03:18.390 --> 00:03:20.667 we need to just go into the next one,00:03:20.670 --> 00:03:23.250 prioritize client, work over internal,00:03:23.250 --> 00:03:25.080 especially when you're not sure00:03:25.080 --> 00:03:26.910 which one is more important.00:03:26.910 --> 00:03:28.968 We have a lot of people.00:03:28.970 --> 00:03:31.778 Who will you know choose to work on00:03:31.778 --> 00:03:34.433 an internal task rather than a client00:03:34.433 --> 00:03:36.830 task when all things are equal?00:03:36.830 --> 00:03:37.971 And if you're going to finish them00:03:37.971 --> 00:03:39.258 on the Sprint, that's totally fine.00:03:39.258 --> 00:03:41.120 But we've had a lot of people00:03:41.174 --> 00:03:42.847 do that and then kick the client00:03:42.847 --> 00:03:44.259 tasks to the next Sprint,00:03:44.260 --> 00:03:46.620 and we've just sort of seen a repeat of that.00:03:46.620 --> 00:03:48.010 And that's something that we00:03:48.010 --> 00:03:49.790 need to get away from doing,00:03:49.790 --> 00:03:52.082 because ultimately making our00:03:52.082 --> 00:03:55.975 clients happy is the only reason why00:03:55.975 --> 00:03:58.720 were employed here as developers.00:03:58.720 --> 00:04:00.208 Uhm alright, sorry Brendan.00:04:00.208 --> 00:04:02.869 Can you read the next two and00:04:02.869 --> 00:04:04.975 then we'll go to somebody else?00:04:04.980 --> 00:04:06.312 I can do that,00:04:06.312 --> 00:04:07.644 prioritize client work over00:04:07.644 --> 00:04:09.680 internal when you're not sure which00:04:09.680 --> 00:04:10.988 one is more important.00:04:13.420 --> 00:04:17.354 Get the IW mockups and markups if00:04:17.354 --> 00:04:20.104 applicable for the project and save them00:04:20.104 --> 00:04:22.349 to miscellaneous folder on your local.00:04:28.660 --> 00:04:29.731 Awesome, thanks, uh.00:04:29.731 --> 00:04:31.516 Prior to starting your day,00:04:31.520 --> 00:04:33.568 decide what project you're going to work on.00:04:33.570 --> 00:04:36.081 Try to stick to one project and the same00:04:36.081 --> 00:04:38.458 feature if possible to increase efficiency.00:04:38.460 --> 00:04:41.016 So this is just sort of an efficiency tip.00:04:41.020 --> 00:04:43.336 If you're a more experienced developer,00:04:43.340 --> 00:04:44.220 this this probably won't00:04:44.220 --> 00:04:45.540 be as big of an issue,00:04:45.540 --> 00:04:48.520 but particularly for newer developers.00:04:48.520 --> 00:04:51.085 I know this is something that I had a00:04:51.085 --> 00:04:53.556 major problem on when I first started.00:04:53.560 --> 00:04:55.135 As you look at a task and you're like,00:04:55.140 --> 00:04:57.188 Oh yeah, I can't do that, and but you00:04:57.188 --> 00:04:59.410 put like 40 minutes into figuring it out.00:04:59.410 --> 00:05:01.978 And typically before you start something,00:05:01.980 --> 00:05:04.017 in most cases you're going to pull00:05:04.017 --> 00:05:07.386 from QA and so you can get into this00:05:07.386 --> 00:05:09.942 pattern of just extreme inefficiency00:05:09.942 --> 00:05:12.091 where you're pulling from QA.00:05:12.091 --> 00:05:14.630 You know doing everything you need to do,00:05:14.630 --> 00:05:15.878 building all that stuff.00:05:17.940 --> 00:05:20.340 And then trying to work on that task,00:05:20.340 --> 00:05:22.440 figuring out that you can't do it00:05:22.440 --> 00:05:24.771 up going to another one and another00:05:24.771 --> 00:05:27.275 one and some it is happened here00:05:27.275 --> 00:05:29.240 before where sometimes the developer00:05:29.240 --> 00:05:32.436 will go an entire day with just that00:05:32.436 --> 00:05:34.860 that vicious cycle and not actually00:05:34.942 --> 00:05:37.487 complete any any development work.00:05:37.490 --> 00:05:39.814 So just so pro tip for efficiency,00:05:39.820 --> 00:05:41.740 try to stick to one project and if00:05:41.740 --> 00:05:43.397 you have multiple tasks for the00:05:43.397 --> 00:05:45.580 same user story or the same feature,00:05:45.580 --> 00:05:47.650 just just work on those.00:05:47.650 --> 00:05:49.288 And what you can do is really00:05:49.288 --> 00:05:50.260 plan your week out.00:05:50.260 --> 00:05:52.788 That way if you're looking at your Sprint,00:05:52.790 --> 00:05:56.552 UM, at the beginning of the week and just,00:05:56.560 --> 00:05:58.121 you know Monday I'm going to work00:05:58.121 --> 00:05:59.366 on this Tuesday, this Wednesday.00:05:59.366 --> 00:06:00.806 This could get blown up.00:06:00.810 --> 00:06:01.564 You know,00:06:01.564 --> 00:06:05.188 if you're on SSB and or or any other00:06:05.188 --> 00:06:08.260 that we have that that priority.00:06:08.260 --> 00:06:09.622 Deal with the client where they00:06:09.622 --> 00:06:10.530 can just come in,00:06:10.530 --> 00:06:12.290 but having that plan will allow you to00:06:12.290 --> 00:06:14.259 be so much more efficient when you're00:06:14.259 --> 00:06:16.090 when you're working on your tasks.00:06:18.200 --> 00:06:19.384 Brendan, go for it.00:06:19.384 --> 00:06:21.720 Uh, I definitely agree on that one.00:06:21.720 --> 00:06:27.248 It is so easy and so you know.00:06:27.250 --> 00:06:30.260 Not necessarily anyone's fault, uh,00:06:30.260 --> 00:06:32.807 when you try to start a project and you,00:06:32.810 --> 00:06:35.170 you see, there's no, uh.00:06:35.170 --> 00:06:36.895 You're not meeting requirement or00:06:36.895 --> 00:06:38.955 you don't have the information you00:06:38.955 --> 00:06:43.050 need or something like that and, uh.00:06:43.050 --> 00:06:44.550 I don't know if there's a.00:06:44.550 --> 00:06:47.050 If anybody knows a good way to to solve that,00:06:47.050 --> 00:06:48.898 but that would definitely help if we00:06:48.898 --> 00:06:50.939 had some way to minimize that more.00:06:53.800 --> 00:06:55.858 Yeah, that that's a great point00:06:55.858 --> 00:06:58.608 and we are we are working on a,00:06:58.610 --> 00:07:01.154 you know, improving that and and00:07:01.154 --> 00:07:02.882 getting that information from.00:07:02.882 --> 00:07:05.594 You know having the task be00:07:05.594 --> 00:07:07.910 while the actually tests out.00:07:07.910 --> 00:07:09.737 We have a couple ideas that we're00:07:09.737 --> 00:07:11.740 working on to make that happen,00:07:11.740 --> 00:07:14.588 which you know if nothing else will well,00:07:14.588 --> 00:07:15.878 it should accomplish two things.00:07:15.880 --> 00:07:17.545 Either the developers will have00:07:17.545 --> 00:07:19.599 more instructions as to what to do,00:07:19.600 --> 00:07:21.880 or the person who helped ask it out.00:07:21.880 --> 00:07:23.410 Will say to the PM like Oh no this00:07:23.410 --> 00:07:25.019 we don't have enough information.00:07:25.020 --> 00:07:27.106 For this, so hopefully that solves it.00:07:31.740 --> 00:07:33.340 Alright, uh, just over,00:07:33.340 --> 00:07:36.369 could you read the bottom 4 for me?00:07:36.370 --> 00:07:38.322 Sure, if you have a bucket ticket or00:07:38.322 --> 00:07:40.627 a task that doesn't make sense to you,00:07:40.630 --> 00:07:42.562 reach out to a more experienced developer00:07:42.562 --> 00:07:44.957 and ask for assistance in tasking it out.00:07:47.590 --> 00:07:48.496 Very important.00:07:48.496 --> 00:07:51.214 Even if you're not incredibly new,00:07:51.220 --> 00:07:54.660 I still have to do this from time to time.00:07:54.660 --> 00:07:56.946 Yeah, I mean and that's that's a great point.00:07:56.950 --> 00:07:58.814 I'm so thank you so much for saying00:07:58.814 --> 00:08:00.640 that Josh, I want to make sure00:08:00.640 --> 00:08:02.385 that everybody on this call feels00:08:02.385 --> 00:08:04.618 empowered to like hit the stop button.00:08:04.620 --> 00:08:05.380 That's what we used to.00:08:05.380 --> 00:08:07.909 What I used to say in my previous life,00:08:07.910 --> 00:08:10.226 you know. But if you're if you're looking00:08:10.226 --> 00:08:12.298 at something and it doesn't make sense,00:08:12.300 --> 00:08:14.365 the worst thing you can do is00:08:14.365 --> 00:08:16.170 start to work on it, right?00:08:16.170 --> 00:08:17.930 Because at that point,00:08:17.930 --> 00:08:20.348 you know you're either going in00:08:20.348 --> 00:08:22.561 the wrong direction or parallel00:08:22.561 --> 00:08:24.660 direction and just, you know.00:08:24.660 --> 00:08:25.720 Costing the company money,00:08:25.720 --> 00:08:27.340 so I want to make sure that everybody on00:08:27.340 --> 00:08:29.044 this call feels empowered to say, hey,00:08:29.044 --> 00:08:31.956 Brandon, this does not make sense to me.00:08:31.960 --> 00:08:33.454 Like literally all you guys have00:08:33.454 --> 00:08:35.381 to do is send me a message and00:08:35.381 --> 00:08:36.784 say this doesn't make sense.00:08:36.784 --> 00:08:39.565 Can you look at this and get me somebody00:08:39.565 --> 00:08:41.763 to help help me get more information00:08:41.828 --> 00:08:45.360 and I will take care of it 100%.00:08:45.360 --> 00:08:46.740 Whether that's Riccio, sorry,00:08:46.740 --> 00:08:47.430 go ahead.00:08:50.920 --> 00:08:52.656 Sorry I keep forgetting that can raise my00:08:52.656 --> 00:08:54.517 hand to wait until you're done talking.00:08:54.520 --> 00:08:57.050 No, you're fine, go ahead.00:08:57.050 --> 00:09:02.167 Ah, I actually do this pretty often where00:09:02.167 --> 00:09:04.610 I don't have enough information and I00:09:04.675 --> 00:09:07.163 just need you know that little bit extra00:09:07.170 --> 00:09:10.812 and it can take the PM quite a bit of00:09:10.812 --> 00:09:13.229 time to to feed you everything you need.00:09:13.230 --> 00:09:17.814 So a good tip that I've learned is.00:09:17.820 --> 00:09:20.100 You know you get a look as soon as you00:09:20.160 --> 00:09:22.302 get us something where you can't continue00:09:22.302 --> 00:09:24.840 or do you don't have all the information00:09:24.840 --> 00:09:28.024 you need or might not get asked out enough.00:09:28.024 --> 00:09:31.224 Look at what other ticket you have come00:09:31.224 --> 00:09:34.500 and see if you can work on that instead,00:09:34.500 --> 00:09:37.055 because if you try to continue without00:09:37.055 --> 00:09:39.640 having you know what you need for it,00:09:39.640 --> 00:09:41.848 that can waste quite a bit of time.00:09:45.000 --> 00:09:47.100 Absolutely, uhm and yeah.00:09:47.100 --> 00:09:49.765 I mean literally, I want to make sure00:09:49.765 --> 00:09:51.410 this is super clear for everybody.00:09:51.410 --> 00:09:54.394 Like if you don't understand what to do,00:09:54.400 --> 00:09:56.101 do not work on the do not00:09:56.101 --> 00:09:57.619 work on the task right.00:09:57.620 --> 00:09:59.454 Reach out to me or you know00:09:59.454 --> 00:10:00.848 it doesn't have to be me,00:10:00.850 --> 00:10:02.890 but you can always reach out to me00:10:02.890 --> 00:10:05.158 and I will make sure that somebody,00:10:05.160 --> 00:10:07.085 whether it's you know getting00:10:07.085 --> 00:10:10.070 with the PM myself, you know,00:10:10.070 --> 00:10:12.950 James somebody that can00:10:12.950 --> 00:10:16.213 provide that clarity TM. For.00:10:16.213 --> 00:10:19.277 Uh, to help you get unblocked on that?00:10:19.280 --> 00:10:21.818 Uhm, Josh, sorry go ahead man,00:10:21.820 --> 00:10:23.275 continue cool, uh,00:10:23.275 --> 00:10:25.700 when is the task complete?00:10:25.700 --> 00:10:27.092 When the work you've done has00:10:27.092 --> 00:10:28.313 either been submitted in a00:10:28.313 --> 00:10:29.277 pull request and approved,00:10:29.280 --> 00:10:31.338 or if the work you've done cannot00:10:31.338 --> 00:10:33.180 be submitted in a PR turning00:10:33.180 --> 00:10:34.680 on nap setting for example.00:10:34.680 --> 00:10:36.455 That work should be duplicated00:10:36.455 --> 00:10:38.230 on all environments such as00:10:38.300 --> 00:10:40.076 QA or stage for that project.00:10:40.080 --> 00:10:41.598 For pipelines you would want to00:10:41.598 --> 00:10:43.411 add the app settings to the backup00:10:43.411 --> 00:10:44.651 configs folder for the project00:10:44.651 --> 00:10:46.229 on the QA or staging server.00:10:49.330 --> 00:10:50.080 Thank you.00:10:52.200 --> 00:10:54.928 Yeah, go ahead K.00:10:54.930 --> 00:10:56.466 Check to see if other developers00:10:56.466 --> 00:10:58.209 have tasks for the same feature00:10:58.209 --> 00:10:59.545 you've completed tasks for.00:10:59.550 --> 00:11:01.026 If so, communicate with them as00:11:01.026 --> 00:11:03.008 soon as your PR has been approved,00:11:03.010 --> 00:11:04.440 although ideally you worked on00:11:04.440 --> 00:11:06.217 the future together and have been00:11:06.217 --> 00:11:07.672 in communication during most of00:11:07.672 --> 00:11:09.280 the development of that feature.00:11:12.910 --> 00:11:14.690 Wind, should deployments be done?00:11:14.690 --> 00:11:16.202 Ideally just once at the end00:11:16.202 --> 00:11:17.815 of the Sprint? Who does them?00:11:17.815 --> 00:11:19.525 The developer that has been assigned00:11:19.525 --> 00:11:21.757 a deployment ticket for that project.00:11:25.430 --> 00:11:27.653 Yeah, so I know this is one that we00:11:27.653 --> 00:11:30.096 sort of do things differently and00:11:30.096 --> 00:11:31.800 the deployment obviously doesn't.00:11:31.800 --> 00:11:33.870 You know doesn't qualify if00:11:33.870 --> 00:11:35.940 we have a pipeline setup,00:11:35.940 --> 00:11:41.129 but I've we've seen PM's some PM's do00:11:41.129 --> 00:11:43.118 tickets for deployments, some don't.00:11:43.118 --> 00:11:46.366 So if you're on a project that00:11:46.366 --> 00:11:48.692 does not have a pipeline setup.00:11:48.692 --> 00:11:51.780 Uhm, but I want to start doing is00:11:51.862 --> 00:11:54.235 making sure that the PM is giving00:11:54.235 --> 00:11:57.118 a task to do the deployments, uhm?00:11:57.118 --> 00:11:58.846 That way, if they need something00:11:58.846 --> 00:12:01.010 done in the middle of the Sprint,00:12:01.010 --> 00:12:02.690 they can just go to that developer.00:12:02.690 --> 00:12:04.100 They already have a task and00:12:04.100 --> 00:12:05.390 they can take care of it.00:12:05.390 --> 00:12:08.060 Brandon, go ahead.00:12:08.060 --> 00:12:11.888 Are in regards to that second00:12:11.890 --> 00:12:13.650 one on the bottom up.00:12:13.650 --> 00:12:16.236 Another part of that that I00:12:16.236 --> 00:12:18.756 don't myself know all the rules00:12:18.756 --> 00:12:22.116 for is there's the the parent00:12:22.116 --> 00:12:24.436 story and you know when do you.00:12:24.440 --> 00:12:26.928 When do you change the status is on00:12:26.928 --> 00:12:29.438 that as you're working on the ticket00:12:29.438 --> 00:12:32.210 and putting into a PR and what is00:12:32.210 --> 00:12:34.555 how much of that is the developer00:12:34.555 --> 00:12:36.176 responsible for and does anyone00:12:36.176 --> 00:12:38.030 else responsible for some of that?00:12:40.710 --> 00:12:43.182 That is a fantastic question. Thank you.00:12:43.182 --> 00:12:45.578 I did not address that in here recently.00:12:45.578 --> 00:12:47.906 Asked for clarity on that myself00:12:47.906 --> 00:12:50.716 and basically it should be the00:12:50.716 --> 00:12:51.768 developers responsibility.00:12:51.770 --> 00:12:56.990 So the way that it should work is if.00:12:56.990 --> 00:12:59.225 Alex and Brendan are working00:12:59.225 --> 00:13:01.460 on the same user story.00:13:01.460 --> 00:13:05.858 UM, when Alex finishes his tasks,00:13:05.860 --> 00:13:09.236 he should go to the parent and see,00:13:09.240 --> 00:13:11.440 you know, around when you submit the PR,00:13:11.440 --> 00:13:13.850 go to the parent and see if if the other00:13:13.915 --> 00:13:16.267 tasks for the parent or open or closed.00:13:16.270 --> 00:13:18.215 If they're closed and then00:13:18.215 --> 00:13:20.160 you've closed the last task,00:13:20.160 --> 00:13:23.720 you should be moving that to code complete.00:13:23.720 --> 00:13:25.598 UM, and then once it's deployed,00:13:25.600 --> 00:13:28.865 it should be moved to deploy to QA.00:13:28.865 --> 00:13:31.656 Now that in itself is kind00:13:31.656 --> 00:13:33.077 of going to be a black hole,00:13:33.080 --> 00:13:34.665 because if you're not deploying00:13:34.665 --> 00:13:36.250 it to QA right away.00:13:38.420 --> 00:13:40.832 Which in most cases you're not going to be00:13:40.832 --> 00:13:43.208 then like if you market is code complete.00:13:43.210 --> 00:13:46.052 What do you have to remind yourself00:13:46.052 --> 00:13:49.497 that you need to go back and Mark that00:13:49.497 --> 00:13:51.870 as deployed to QA, which is why James?00:13:51.870 --> 00:13:54.039 I'm not sure if you guys are all aware00:13:54.039 --> 00:13:55.730 of this, but basically what James00:13:55.730 --> 00:13:58.281 that one of the things he does is if00:13:58.281 --> 00:14:00.479 a ticket has or if a user story has00:14:00.479 --> 00:14:02.565 been in code complete for 30 days,00:14:02.570 --> 00:14:04.655 he automatically says it's been00:14:04.655 --> 00:14:05.906 deployed to QA.00:14:07.930 --> 00:14:10.160 Because there's currently nobody going00:14:10.160 --> 00:14:12.860 in and and manually putting, you know,00:14:12.860 --> 00:14:15.130 deploy to QA on that on that user story.00:14:15.130 --> 00:14:16.870 So that is a great question,00:14:16.870 --> 00:14:18.906 Brendan, and definitely something00:14:18.906 --> 00:14:22.400 we need to get get hashed out.00:14:22.400 --> 00:14:23.516 Because yeah, currently it's00:14:23.516 --> 00:14:25.190 just sort of a black hole.00:14:31.960 --> 00:14:35.970 Communication alright, uhm Jonathan Lee.00:14:35.970 --> 00:14:37.160 Can you take this one for me?00:14:39.190 --> 00:14:40.290 All communication between developer00:14:40.290 --> 00:14:42.384 and PM about a project should be in00:14:42.384 --> 00:14:43.590 the team shell for that project,00:14:43.590 --> 00:14:44.990 but a PR has been completed send00:14:44.990 --> 00:14:46.230 message in the teams channel.00:14:46.230 --> 00:14:47.520 Pain in the group that was00:14:47.520 --> 00:14:48.830 linked to PR for blocked.00:14:48.830 --> 00:14:50.279 Ask 'cause we're waiting on the client00:14:50.279 --> 00:14:51.896 to PM the task should be blocked00:14:51.896 --> 00:14:53.414 and banned and create add script00:14:53.414 --> 00:14:55.388 blocker on the PM and Scrum master00:14:55.388 --> 00:14:57.186 painting team shell for that project.00:14:57.190 --> 00:14:58.331 If you work on something that you00:14:58.331 --> 00:14:59.447 don't have to take it for pain,00:14:59.450 --> 00:15:01.207 PM and Scrum Master and Team Shell00:15:01.207 --> 00:15:02.920 for that project described and what00:15:02.920 --> 00:15:04.430 you did and requested tickets.00:15:04.430 --> 00:15:05.560 When we're kind of project,00:15:05.560 --> 00:15:06.810 understand the scope and communicate00:15:06.810 --> 00:15:07.560 any scope creep.00:15:07.560 --> 00:15:09.395 Something or doing something in00:15:09.395 --> 00:15:11.230 the client disagreed hasn't agreed00:15:11.289 --> 00:15:12.179 to pay us to do.00:15:12.180 --> 00:15:13.988 As well as when a task will be00:15:13.988 --> 00:15:15.270 exceeding the estimated time,00:15:15.270 --> 00:15:16.634 like human communication style00:15:16.634 --> 00:15:17.998 spread cause most damage.00:15:18.000 --> 00:15:19.352 I'm working relationships and00:15:19.352 --> 00:15:21.042 projects like one that communicates.00:15:27.930 --> 00:15:29.616 Thank you, it probably won't come00:15:29.616 --> 00:15:31.906 as too big of a surprise that this00:15:31.906 --> 00:15:33.956 is probably the area as a company00:15:33.956 --> 00:15:35.954 that we struggle with the most.00:15:35.960 --> 00:15:38.318 UM, at least in my opinion.00:15:38.320 --> 00:15:41.540 Uh, I think almost everything.00:15:41.540 --> 00:15:43.826 Almost everything that happens here can00:15:43.826 --> 00:15:46.608 probably be traced back to a lack of00:15:46.608 --> 00:15:48.390 communication in one way or another.00:15:48.390 --> 00:15:50.765 UM, and I know personally00:15:50.765 --> 00:15:52.972 I still struggle with UM.00:15:52.972 --> 00:15:57.020 When a task is going to exceed the estimate,00:15:57.020 --> 00:15:58.571 so I'm curious,00:15:58.571 --> 00:16:01.156 is there anybody here who?00:16:01.160 --> 00:16:03.395 Consistently communicates when a task00:16:03.395 --> 00:16:06.716 when you're going to exceed on a task00:16:06.716 --> 00:16:08.732 but before you actually exceed it,00:16:08.740 --> 00:16:09.574 and if so,00:16:09.574 --> 00:16:11.520 I'd love to know kind of what00:16:11.589 --> 00:16:13.614 your process is for doing that.00:16:13.614 --> 00:16:16.078 Because I think what happens a lot00:16:16.078 --> 00:16:18.668 of times is people are heads down00:16:18.668 --> 00:16:20.653 and don't necessarily realize that00:16:20.653 --> 00:16:22.937 they've put you know four hours into a00:16:22.937 --> 00:16:25.647 3 hour task and still aren't done with it.00:16:25.650 --> 00:16:27.962 Either that or you hit 2 1/2 hours00:16:27.962 --> 00:16:30.685 on a 3 hour task and you're like.00:16:30.690 --> 00:16:33.099 I got this.00:16:33.100 --> 00:16:33.470 Yeah.00:16:36.330 --> 00:16:38.444 Two hours later, I don't get this.00:16:38.450 --> 00:16:39.800 That's usually that's usually it00:16:39.800 --> 00:16:41.848 goes like I feel like I'm so close,00:16:41.850 --> 00:16:43.050 like just a little bit more.00:16:43.050 --> 00:16:45.192 And I don't know if that00:16:45.192 --> 00:16:46.620 didn't work either OK.00:16:46.620 --> 00:16:48.312 Yeah, yeah, so does anybody have00:16:48.312 --> 00:16:50.408 any tips for this or any thoughts?00:16:54.230 --> 00:17:00.450 Just one. I tend to work along with a timer.00:17:00.450 --> 00:17:03.096 I built a Pomodoro app because I'm bad at00:17:03.096 --> 00:17:05.305 staying on task left to my own devices.00:17:05.310 --> 00:17:07.564 So I use that and it basically00:17:07.564 --> 00:17:09.828 just gives an audible cue every00:17:09.828 --> 00:17:12.270 time a working period has ended.00:17:12.270 --> 00:17:14.654 So I tend to leave00:17:14.654 --> 00:17:16.757 for what I'm actually doing during00:17:16.757 --> 00:17:19.390 that half hour to 45 minute block,00:17:19.390 --> 00:17:21.178 whatever it's set for that day,00:17:21.180 --> 00:17:23.760 it makes it a lot easier to tell if you're00:17:23.830 --> 00:17:27.620 going to go way over or make it in time.00:17:27.620 --> 00:17:28.814 Uh, that's awesome.00:17:28.814 --> 00:17:30.804 Is that something you can00:17:30.804 --> 00:17:32.887 share with uh with the team?00:17:32.890 --> 00:17:35.634 Yeah, uhm, I can either give you guys00:17:35.634 --> 00:17:38.593 the link to it on my GitHub or just00:17:38.593 --> 00:17:40.511 pass around the portable executable00:17:40.511 --> 00:17:43.647 because I've got one of those too.00:17:43.650 --> 00:17:45.340 Yeah, whichever way you'd prefer,00:17:45.340 --> 00:17:46.873 I think, but that I think that'd00:17:46.873 --> 00:17:48.598 be great for anybody who wants to,00:17:48.600 --> 00:17:51.930 you know, try to implement that.00:17:51.930 --> 00:17:54.390 Cool, Brendan.00:17:54.390 --> 00:17:56.964 I don't know if anyone else runs into this,00:17:56.970 --> 00:17:58.926 but one of the reasons that00:17:58.926 --> 00:18:01.182 causes me to go over, uh,00:18:01.182 --> 00:18:04.134 so far is I expecting something00:18:04.134 --> 00:18:07.358 to work a certain way or.00:18:07.360 --> 00:18:10.060 Uh, that I get back all the fields and00:18:10.060 --> 00:18:12.898 I need something needs to be fixed00:18:12.898 --> 00:18:15.400 and stuff itself to get my work done,00:18:15.400 --> 00:18:17.880 which causes you know it takes more time.00:18:17.880 --> 00:18:20.743 Should I notify the the PM immediately00:18:20.743 --> 00:18:23.730 when I see something like that?00:18:23.730 --> 00:18:29.116 Or a? Which I do in that case.00:18:29.120 --> 00:18:31.768 Uh, I guess yeah, I mean that's that's,00:18:31.770 --> 00:18:33.282 that's a tricky one.00:18:33.282 --> 00:18:33.660 Uhm,00:18:33.660 --> 00:18:36.204 I guess it depends on like if you're00:18:36.204 --> 00:18:38.717 able to give a rough estimate for00:18:38.717 --> 00:18:40.960 how much you're gonna go over.00:18:40.960 --> 00:18:41.638 If you are,00:18:41.638 --> 00:18:44.109 I would say yeah reach out to the PM and say,00:18:44.110 --> 00:18:46.336 hey, I had this for our task.00:18:46.340 --> 00:18:48.032 I got halfway through it expecting00:18:48.032 --> 00:18:49.940 that this would work a certain way.00:18:49.940 --> 00:18:50.490 It didn't.00:18:50.490 --> 00:18:52.690 I'm probably going to go 2 hours over.00:18:52.690 --> 00:18:53.906 Just wanted to give you a heads up.00:19:00.200 --> 00:19:02.872 OK, so, uh, you should see if you00:19:02.872 --> 00:19:05.456 can find out how much time you00:19:05.456 --> 00:19:09.290 think that would take to fix. Yep.00:19:09.290 --> 00:19:11.426 Yep, and it's always good too.00:19:11.430 --> 00:19:13.104 And this is just a tip for you know,00:19:13.110 --> 00:19:14.470 not even for development,00:19:14.470 --> 00:19:16.170 but just for anything that00:19:16.170 --> 00:19:17.670 you do professionally.00:19:17.670 --> 00:19:20.054 You always like if you're if you go.00:19:20.060 --> 00:19:22.088 If you. If you're bringing like00:19:22.088 --> 00:19:24.070 a potential problem to somebody,00:19:24.070 --> 00:19:26.008 you always want to bring either00:19:26.008 --> 00:19:28.080 a solution or what you can do.00:19:28.080 --> 00:19:30.131 And particularly with the PM's I can00:19:30.131 --> 00:19:31.829 only imagine that they're worse.00:19:31.830 --> 00:19:33.776 Their least favorite thing to hear from00:19:33.776 --> 00:19:36.338 the from a developer is we can't do that.00:19:36.340 --> 00:19:38.680 Right, because from a PM's perspective00:19:38.680 --> 00:19:41.298 they're like just do the thing like.00:19:41.300 --> 00:19:42.776 You know I have a meeting with the client.00:19:42.780 --> 00:19:45.354 We have a demo like just do this thing and00:19:45.354 --> 00:19:49.080 So what we should be doing is saying hey,00:19:49.080 --> 00:19:51.710 we can't do that but we can do XYZ and00:19:51.784 --> 00:19:54.208 that's just sort of a form of that.00:19:54.210 --> 00:19:56.650 Like hey, I'm going to go over on this task,00:19:56.650 --> 00:19:58.740 but I think I'll have it done an extra 2
00:19:58.795 --> 00:20:00.937 hours even if you end up going over that.00:20:00.940 --> 00:20:02.916 I mean those things are going to happen,00:20:02.920 --> 00:20:07.200 but at least giving them sort of a heads up.00:20:07.200 --> 00:20:11.568 Be beneficial and will help them to plan.00:20:11.570 --> 00:20:14.756 And ideally, from a PM standpoint.00:20:14.760 --> 00:20:16.218 I don't know what they're doing00:20:16.218 --> 00:20:16.947 with that information,00:20:16.950 --> 00:20:19.990 but if I were a PM I would be documenting00:20:20.069 --> 00:20:23.037 like oh this user story on that feature.00:20:23.040 --> 00:20:25.077 We're going to have an extra two00:20:25.077 --> 00:20:26.970 to four hours because of this00:20:26.970 --> 00:20:29.938 for future change requests.00:20:29.940 --> 00:20:31.753 So that that would be the reason00:20:31.753 --> 00:20:32.830 to be communicating that.00:20:39.720 --> 00:20:41.088 Alright, time management one00:20:41.088 --> 00:20:42.716 of my favorites. Brandon Lyon.00:20:42.716 --> 00:20:44.504 You take this away for me.00:20:46.830 --> 00:20:50.392 Sure. Uhm log time daily.00:20:50.392 --> 00:20:52.720 Find a plan that works for you.00:20:52.720 --> 00:20:54.673 Some people write their time down as they go.00:20:54.680 --> 00:20:57.740 Some remember some type it into VS code file.00:20:57.740 --> 00:20:59.240 All that matters is that before00:20:59.240 --> 00:21:00.720 you sign off for the day,00:21:00.720 --> 00:21:01.992 your time for that day has00:21:01.992 --> 00:21:03.310 been logged to easy projects.00:21:06.000 --> 00:21:08.652 Uh, moving on if nobody has00:21:08.652 --> 00:21:11.508 any discussion on that one.00:21:11.508 --> 00:21:13.916 Uh update tickets daily.00:21:13.920 --> 00:21:15.887 Whatever your plan for time logs is,00:21:15.890 --> 00:21:17.434 add this to it, whether at the same00:21:17.434 --> 00:21:18.738 time or immediately after logging00:21:18.738 --> 00:21:20.193 time and updating tickets should00:21:20.193 --> 00:21:21.858 be two sides of the same coin.00:21:26.340 --> 00:21:27.764 We can talk about those for a minute.00:21:27.770 --> 00:21:29.436 Uhm, so I know that some people00:21:29.436 --> 00:21:31.180 do it like the next morning,00:21:31.180 --> 00:21:33.080 and that's totally fine. UM,00:21:33.080 --> 00:21:35.704 as long as you're obviously getting it in,00:21:35.710 --> 00:21:38.118 either you know that same day or early00:21:38.118 --> 00:21:40.537 the next day, that's that's fine.00:21:40.537 --> 00:21:44.030 I, I think most people have had,00:21:44.030 --> 00:21:47.050 you know, jobs outside of outside of00:21:47.050 --> 00:21:49.475 clarity or outside of development.00:21:49.480 --> 00:21:51.736 And I just I would ask you when00:21:51.736 --> 00:21:53.500 you're thinking about logging time.00:21:53.500 --> 00:21:55.124 If you're somebody that struggles with it,00:21:55.130 --> 00:21:57.086 I would ask you to consider.00:21:57.090 --> 00:21:58.714 Like what you did in your past00:21:58.714 --> 00:22:00.438 life or in your past career,00:22:00.440 --> 00:22:02.456 and if it would have ever have00:22:02.456 --> 00:22:04.182 been acceptable to not log your00:22:04.182 --> 00:22:06.037 time for like two or three days.00:22:08.270 --> 00:22:10.886 I can't think of another profession00:22:10.886 --> 00:22:13.197 where that's even remotely OK to00:22:13.197 --> 00:22:15.165 do so I would just ask you to00:22:15.239 --> 00:22:17.279 consider that moving forward.00:22:17.280 --> 00:22:19.260 If you are somebody who struggles00:22:19.260 --> 00:22:21.442 with logging time and then as far00:22:21.442 --> 00:22:23.230 as the update tickets daily go,00:22:23.230 --> 00:22:26.296 does everybody know what Daniel means00:22:26.296 --> 00:22:29.990 by like burn up and burned down?00:22:29.990 --> 00:22:31.208 As they written, let me rephrase that.00:22:31.210 --> 00:22:33.484 Is there anybody who doesn't know00:22:33.484 --> 00:22:35.639 what Daniel means by burn up?00:22:35.640 --> 00:22:36.888 Since we've been hearing about the00:22:36.888 --> 00:22:38.480 burn down for our whole careers here00:22:42.950 --> 00:22:44.805 OK, so everybody knows what it means.00:22:44.810 --> 00:22:48.698 So Alex. Can you explain what burnup is?00:22:58.480 --> 00:23:01.987 Uh, I honestly I get them confused00:23:01.987 --> 00:23:06.840 between the two. One of them is a.00:23:06.840 --> 00:23:09.626 How many hours you've spent have you?00:23:09.630 --> 00:23:12.100 How many hours you've completed?00:23:12.100 --> 00:23:15.636 Uhm? And the other one is how many00:23:15.636 --> 00:23:18.760 hours total you've taken on tasks.00:23:21.210 --> 00:23:23.746 Cool yeah the the hours completed is the00:23:23.746 --> 00:23:26.578 burn up so when you're logging time to00:23:26.578 --> 00:23:29.165 your tickets your burn up is basically00:23:29.165 --> 00:23:31.483 Daniel seeing just just looking at00:23:31.483 --> 00:23:33.720 your completed work on tickets, right?00:23:36.060 --> 00:23:39.708 The that is huge for figuring out that00:23:39.708 --> 00:23:42.489 you've actually been doing work right00:23:42.490 --> 00:23:44.240 because you're burned down can look bad,00:23:44.240 --> 00:23:45.560 but your burn up can look00:23:45.560 --> 00:23:46.750 good if you've you know,00:23:46.750 --> 00:23:48.310 like Alex and Josh for example,00:23:48.310 --> 00:23:51.646 you guys had some SSB drama either earlier.00:23:51.650 --> 00:23:53.694 This printer at the end of last00:23:53.694 --> 00:23:55.422 Sprint where everybody knew what you00:23:55.422 --> 00:23:57.277 were doing and it was totally cool.00:23:57.280 --> 00:23:59.232 But you guys had like 18 hours log00:23:59.232 --> 00:24:01.004 to like 4 hour tickets, right?00:24:01.004 --> 00:24:03.412 So your burn downs look bad and00:24:03.412 --> 00:24:05.557 your burn up look great well.00:24:05.557 --> 00:24:09.133 Part of that burn up is also should00:24:09.133 --> 00:24:12.326 be met like your burn up not.00:24:12.330 --> 00:24:14.858 You're burned out but your burn up should00:24:14.858 --> 00:24:18.118 be a perfect match to easy projects, right?00:24:18.118 --> 00:24:21.585 So like if you have 14 hours on00:24:21.585 --> 00:24:23.910 an SSB ticket for performance,00:24:23.910 --> 00:24:25.042 you know improving the00:24:25.042 --> 00:24:26.174 performance of the site,00:24:26.180 --> 00:24:29.180 you should have 14 hours logged in easy00:24:29.180 --> 00:24:31.215 projects describing what you did to00:24:31.215 --> 00:24:33.220 improve the performance of the site.00:24:38.550 --> 00:24:41.838 Cool alright Brendan if you could do the00:24:41.838 --> 00:24:44.837 at least the last two please. Alright,00:24:44.837 --> 00:24:47.686 uh, respond to pings within one hour,00:24:47.690 --> 00:24:49.170 just as you'd like people to respond to00:24:49.170 --> 00:24:50.903 you when you ping them, return the favor.00:24:50.903 --> 00:24:53.020 Exceptions can be made if your heads down,00:24:53.020 --> 00:24:55.252 but the goal should be checking00:24:55.252 --> 00:24:57.409 your teams messages once per hour.00:24:57.410 --> 00:24:59.220 And then understand how and00:24:59.220 --> 00:25:01.030 when to ask for help.00:25:01.030 --> 00:25:02.154 If you're making progress.00:25:02.154 --> 00:25:04.107 But get halfway through the allocated time00:25:04.107 --> 00:25:06.042 for task and feel that progress is too slow.00:25:06.050 --> 00:25:07.382 Reach out for help.00:25:07.382 --> 00:25:09.047 If you're not making progress,00:25:09.050 --> 00:25:11.066 reach out for help after 20 minutes.00:25:11.070 --> 00:25:13.102 If no developer is available to help you00:25:13.102 --> 00:25:15.206 schedule a time for office hours that day,00:25:15.210 --> 00:25:16.838 if possible with James.00:25:16.838 --> 00:25:19.686 And the only caveat allowed on that00:25:19.686 --> 00:25:22.635 last one personal flavor is if James00:25:22.635 --> 00:25:24.930 doesn't have office hours availability,00:25:24.930 --> 00:25:26.860 other people might as well.00:25:26.860 --> 00:25:30.784 So you can absolutely just put a like general00:25:30.784 --> 00:25:33.710 ping in the office hours just requesting00:25:33.795 --> 00:25:36.286 office hours with whoever's got the time.00:25:36.286 --> 00:25:38.533 If it's a problem that maybe doesn't00:25:38.533 --> 00:25:40.498 need James specific guidance may.00:25:40.500 --> 00:25:42.642 If it's a front end thing that you could00:25:42.642 --> 00:25:44.728 get some of Jesse's office hours for,00:25:44.730 --> 00:25:46.134 or potentially a back end thing00:25:46.134 --> 00:25:48.019 that I might be able to help with.00:25:48.020 --> 00:25:49.970 Or or even anybody else.00:25:49.970 --> 00:25:50.526 Uhm?00:25:50.526 --> 00:25:51.638 But yeah.00:25:53.820 --> 00:25:57.550 Awesome, thank you. Other Brendan.00:25:57.550 --> 00:26:00.469 Uh, one thing I wanted to ask00:26:00.469 --> 00:26:04.400 about responding to pings, uhm?00:26:04.400 --> 00:26:06.490 Obviously you don't wanna expect00:26:06.490 --> 00:26:09.426 someone to respond to a ping that00:26:09.426 --> 00:26:12.005 you sent at midnight, so is there.00:26:12.005 --> 00:26:14.075 Is there a court hours where00:26:14.075 --> 00:26:16.437 where that's should be like? Oh,00:26:16.437 --> 00:26:19.053 you should have responded to that and not.00:26:19.060 --> 00:26:22.189 A sooner kind of a time frame.00:26:22.190 --> 00:26:25.228 Is that core hours of 3:50 or what00:26:25.228 --> 00:26:27.224 would that be? Yes, absolutely.00:26:27.224 --> 00:26:29.303 Yep, I should have put that on00:26:29.303 --> 00:26:31.006 there so I can add that after,00:26:31.010 --> 00:26:32.426 but that is a fantastic point.00:26:32.430 --> 00:26:34.130 Yeah, that would only be00:26:34.130 --> 00:26:35.490 relevant during core hours,00:26:35.490 --> 00:26:37.812 which is 10:00 AM to 4:00 PM central time.00:26:42.520 --> 00:26:43.309 Thank you, Brendan.00:26:46.130 --> 00:26:47.505 Alright, I should have gone00:26:47.505 --> 00:26:48.605 down a list consistently.00:26:48.610 --> 00:26:53.200 Oh Greg, can you read the bottom 4 for me?00:26:53.200 --> 00:26:56.954 Sure thing. Your goal should be to complete00:26:56.954 --> 00:26:58.980 the task the day you start to work on it.00:26:58.980 --> 00:27:01.236 Only exception to this is if you need00:27:01.236 --> 00:27:02.919 assistance from James in the office.00:27:02.920 --> 00:27:05.122 Hours cannot be scheduled that day00:27:05.122 --> 00:27:07.659 or if there wasn't enough time left00:27:07.659 --> 00:27:09.983 in the day when you started it.00:27:09.990 --> 00:27:12.545 You just want to keep moving on.00:27:12.550 --> 00:27:15.422 Yes, please OK uh, make a schedule that00:27:15.422 --> 00:27:18.080 falls within core hours and stick to it.00:27:18.080 --> 00:27:19.709 If you are going to be out during the00:27:19.709 --> 00:27:21.236 time you would normally be working.00:27:21.240 --> 00:27:23.265 Whether it's a full day or for a doctor's00:27:23.265 --> 00:27:24.930 appointment, paying Brandon, Caroline,00:27:24.930 --> 00:27:27.686 and Daniel directly to let them know.00:27:27.686 --> 00:27:29.331 Also submit a PTO request00:27:29.331 --> 00:27:31.198 for that day on rippling.00:27:31.200 --> 00:27:32.043 Requesting time off,00:27:32.043 --> 00:27:34.356 this should be done prior to a Sprint00:27:34.356 --> 00:27:36.042 and ideally with two weeks notice00:27:36.042 --> 00:27:38.110 so that we can plan accordingly.00:27:40.310 --> 00:27:42.182 OK, so a lot to unpack on this one,00:27:42.190 --> 00:27:43.510 uh, starting with the first one,00:27:43.510 --> 00:27:47.670 so uhm, most tasks. I know this isn't.00:27:47.670 --> 00:27:49.008 This doesn't qualify for all tasks,00:27:49.010 --> 00:27:51.110 but most tasks should be basically00:27:51.110 --> 00:27:53.863 less than a days worth of work, right?00:27:53.863 --> 00:27:56.036 Less than seven, you know, seven hours.00:27:56.036 --> 00:27:57.248 Some will be longer,00:27:57.250 --> 00:27:59.110 and that's obviously different,00:27:59.110 --> 00:28:01.900 but most will be less so.00:28:01.900 --> 00:28:03.688 I want everybody to get in00:28:03.688 --> 00:28:04.880 the thought process of,00:28:04.880 --> 00:28:06.050 you know, basically,00:28:06.050 --> 00:28:08.000 when you're deciding what you're00:28:08.000 --> 00:28:09.757 gonna work on for the day,00:28:09.760 --> 00:28:10.960 figuring out something that00:28:10.960 --> 00:28:12.760 you can complete in that day.00:28:12.760 --> 00:28:13.876 I don't know about you guys,00:28:13.880 --> 00:28:16.790 but for me it does help.00:28:16.790 --> 00:28:17.990 Sometimes if you're stuck00:28:17.990 --> 00:28:19.499 on something to walk away,00:28:19.500 --> 00:28:21.318 but I've also had this situation00:28:21.318 --> 00:28:23.729 where I stop in the middle of a00:28:23.729 --> 00:28:25.750 task because I'm done for the day,00:28:25.750 --> 00:28:26.740 which is going to happen.00:28:26.740 --> 00:28:27.332 It's fine,00:28:27.332 --> 00:28:29.700 but then the next day I mean it00:28:29.774 --> 00:28:31.886 takes me awhile to figure out.00:28:31.890 --> 00:28:33.340 Exactly what I was doing.00:28:33.340 --> 00:28:33.660 Uhm,00:28:33.660 --> 00:28:35.580 and so there there can be00:28:35.580 --> 00:28:37.470 some lost time there again.00:28:37.470 --> 00:28:39.080 It's going to happen sometimes,00:28:39.080 --> 00:28:42.824 but if we make it a goal to try to start00:28:42.824 --> 00:28:46.100 and complete work in the same day.00:28:46.100 --> 00:28:49.649 That'll that'll lead to much more efficiency.00:28:49.650 --> 00:28:50.832 Generally speaking up,00:28:50.832 --> 00:28:52.802 making a schedule that falls00:28:52.802 --> 00:28:54.030 within core hours.00:28:54.030 --> 00:28:55.674 You know we're we have every00:28:55.674 --> 00:28:57.230 time zone almost in the US,00:28:57.230 --> 00:28:59.094 at least in the continental U S represented.00:29:01.140 --> 00:29:02.918 But so, so nobody is ever going00:29:02.918 --> 00:29:04.809 to be working all the same hours.00:29:04.810 --> 00:29:08.023 That's fine, but everybody should be getting00:29:08.023 --> 00:29:11.908 to a point where you're working like OK,00:29:11.910 --> 00:29:15.910 I'm I work 11 to 7 or 11 to 8,00:29:15.910 --> 00:29:18.295 you know and take an hour lunch every day.00:29:18.300 --> 00:29:20.512 I've already asked some of the developers00:29:20.512 --> 00:29:23.052 just when it was on my mind, but eventually00:29:23.052 --> 00:29:25.334 I'm going to ask for what you're.00:29:25.340 --> 00:29:27.880 You're basically, your schedule is00:29:27.880 --> 00:29:30.770 because we want more developer.00:29:30.770 --> 00:29:32.800 Collaboration.00:29:32.800 --> 00:29:35.496 And I want to make that time available.00:29:35.500 --> 00:29:39.188 So if, UM, you know Josh is in00:29:39.188 --> 00:29:42.214 the Eastern Time zone, and UM,00:29:42.214 --> 00:29:45.343 Alex is in the central time zone,00:29:45.350 --> 00:29:48.318 but because of our core hours even that,00:29:48.320 --> 00:29:50.308 even though that's only one hour difference,00:29:50.310 --> 00:29:53.534 Josh might start at 8:00 AM Eastern Time.00:29:53.540 --> 00:29:55.215 And Alex doesn't start until00:29:55.215 --> 00:29:56.555 9:00 AM central time.00:29:56.560 --> 00:29:58.882 And there's a that's a 2 hour gap there.00:29:58.890 --> 00:30:00.966 So Josh, if he's going to00:30:00.966 --> 00:30:02.929 collaborate with Alex before he even.00:30:02.930 --> 00:30:04.729 You know, maybe send him a message00:30:04.729 --> 00:30:05.810 or anything like that,00:30:05.810 --> 00:30:07.560 or schedules a working session.00:30:07.560 --> 00:30:10.314 He can go and say oh what, what?00:30:10.314 --> 00:30:12.992 What's Alex is like regular schedule.00:30:12.992 --> 00:30:14.547 He can go and look.00:30:14.550 --> 00:30:15.984 Once we have this document put00:30:15.984 --> 00:30:17.792 together and then he can say oh, OK,00:30:17.792 --> 00:30:18.074 cool.00:30:18.074 --> 00:30:18.920 So he's he's.00:30:18.920 --> 00:30:20.362 He starts at this time so I'll00:30:20.362 --> 00:30:21.602 just plan on starting our00:30:21.602 --> 00:30:23.037 working session at this time.00:30:25.410 --> 00:30:29.410 It also helps you to get into a routine and00:30:29.410 --> 00:30:30.866 I know that's something that helped me.00:30:30.870 --> 00:30:32.529 'cause you know, working here is hard,00:30:32.530 --> 00:30:35.638 especially for newer people.00:30:35.640 --> 00:30:38.862 And I think having getting a routine in a00:30:38.862 --> 00:30:41.866 schedule can can help with that tremendously.00:30:41.870 --> 00:30:42.918 Uhm, and then outages.00:30:42.918 --> 00:30:45.568 This is a thing as a company that we00:30:45.568 --> 00:30:47.920 are just terrible about and it's pretty00:30:47.984 --> 00:30:50.404 much everybody across the board, UM.00:30:50.404 --> 00:30:54.116 So the reason to ping me is obvious.00:30:54.120 --> 00:30:55.780 Caroline is somewhat obvious.00:30:55.780 --> 00:30:58.691 Daniel adding Daniel in there is because00:30:58.691 --> 00:31:01.475 he will have an immediate like he'll see00:31:01.475 --> 00:31:04.202 the ping and he'll be like oh OK, so.00:31:04.202 --> 00:31:07.460 You know Brendan line is sick today he's out.00:31:07.460 --> 00:31:08.676 This is gonna impact,00:31:08.676 --> 00:31:11.408 you know some of the work in his Sprint00:31:11.410 --> 00:31:14.686 so Daniel can be looking at that and and00:31:14.686 --> 00:31:17.360 potentially just move stuff out on the spot.00:31:17.360 --> 00:31:21.530 Uhm? And then requesting time off.00:31:21.530 --> 00:31:23.906 The the goal I mean I put two weeks00:31:23.906 --> 00:31:26.259 in there that's that's somewhat.00:31:26.260 --> 00:31:30.416 Standard nationwide, regardless of the, UM.00:31:30.416 --> 00:31:32.400 Regardless of the business,00:31:32.400 --> 00:31:34.308 two weeks is normally what that00:31:34.308 --> 00:31:36.259 what that time frame should be.00:31:36.260 --> 00:31:38.689 But for us you really just need00:31:38.689 --> 00:31:41.378 to do it prior to a Sprint.00:31:41.380 --> 00:31:42.540 Preferably, the week before,00:31:42.540 --> 00:31:44.950 at least so that it's before you've been,00:31:44.950 --> 00:31:48.580 you know, allocated a bunch of tasks, but.00:31:48.580 --> 00:31:49.868 Uh, so I'll stop there for a second.00:31:49.870 --> 00:31:51.566 Anybody have any questions on any of that?00:31:53.720 --> 00:31:55.248 Or comments or concerns?00:31:59.780 --> 00:32:00.100 Cool.00:32:04.250 --> 00:32:07.316 Meetings all. Right?00:32:07.316 --> 00:32:11.404 Uhm, meetings are fun.00:32:11.410 --> 00:32:17.152 So, uh, lockjaw could take this one for me.00:32:17.160 --> 00:32:19.608 Sure. Assuming you don't want00:32:19.608 --> 00:32:20.940 me to get the chart though,00:32:20.940 --> 00:32:23.376 no, no chart is not necessary.00:32:23.380 --> 00:32:26.038 Hey, meetings that can be rescheduled,00:32:26.040 --> 00:32:26.997 needed product meetings.00:32:26.997 --> 00:32:29.584 If you were in a project meeting and00:32:29.584 --> 00:32:31.360 you feel you're not adding value,00:32:31.360 --> 00:32:34.550 you have little to contribute.00:32:34.550 --> 00:32:36.272 Haven't worked on Project recently or00:32:36.272 --> 00:32:38.506 don't have any tasks in the Sprint for it.00:32:38.510 --> 00:32:39.682 It is your responsibility00:32:39.682 --> 00:32:41.147 message through and say hey,00:32:41.150 --> 00:32:42.893 I don't feel like I'm adding value00:32:42.893 --> 00:32:44.893 and I'm going to and I'm going to00:32:44.893 --> 00:32:46.610 drop and then dropped from the call.00:32:46.610 --> 00:32:47.930 Before starting your day note00:32:47.930 --> 00:32:49.740 meetings you have on your calendar,00:32:49.740 --> 00:32:51.404 if you have a meetings that leave you00:32:51.404 --> 00:32:53.355 with one hour or less in between messages,00:32:53.360 --> 00:32:54.710 the meeting organizer to see if00:32:54.710 --> 00:32:56.445 you're required to be there or request00:32:56.445 --> 00:32:57.750 that the meeting be rescheduled.00:32:57.750 --> 00:32:59.550 In most cases you completing tasks00:32:59.550 --> 00:33:01.128 efficiently will be more important00:33:01.128 --> 00:33:03.048 to you than attending the meeting.00:33:09.130 --> 00:33:12.609 Thank you very much. Uh, yeah, so I.00:33:12.609 --> 00:33:14.874 I'm well aware that uh,00:33:14.880 --> 00:33:16.944 meetings are one of the biggest00:33:16.944 --> 00:33:18.742 drains on a developer's efficiency,00:33:18.742 --> 00:33:20.647 so I really want people00:33:20.647 --> 00:33:22.430 to take this to heart.00:33:22.430 --> 00:33:23.960 And, you know, I'm gonna give.00:33:23.960 --> 00:33:25.360 I'm gonna drop this by the way,00:33:25.360 --> 00:33:27.430 after this I'm going to drop it in the00:33:27.430 --> 00:33:29.210 channel so everybody can have have it.00:33:29.210 --> 00:33:29.942 And you know,00:33:29.942 --> 00:33:31.406 if you want to review anything.00:33:33.420 --> 00:33:37.081 But these. You know you almost never00:33:37.081 --> 00:33:42.000 have to attend a meeting, I mean.00:33:42.000 --> 00:33:44.142 Even your even your review with me00:33:44.142 --> 00:33:46.159 or Caroline if you just say, hey,00:33:46.159 --> 00:33:47.911 this is I got a meeting heavy day00:33:47.911 --> 00:33:49.914 and I'd really like to get this done.00:33:49.920 --> 00:33:51.192 Can we reschedule this?00:33:51.192 --> 00:33:55.878 It's going to be a yes like 99% of the time.00:33:55.880 --> 00:33:57.200 Now it will be rescheduled.00:33:57.200 --> 00:33:58.248 Eventually, you'll have to.00:33:58.248 --> 00:34:00.256 You'll have to do it, but point is,00:34:00.256 --> 00:34:02.220 I just want to make sure that you00:34:02.220 --> 00:34:03.888 guys feel empowered to say like,00:34:03.890 --> 00:34:06.179 hey, I have too many meetings today.00:34:06.180 --> 00:34:08.287 This is a problem I don't know.00:34:08.290 --> 00:34:09.358 I know on podbay.00:34:09.358 --> 00:34:10.693 I'm not sure in potty,00:34:10.700 --> 00:34:12.962 but if you ever say during00:34:12.962 --> 00:34:14.093 Tuesday or Thursday,00:34:14.100 --> 00:34:16.788 stand up in front of Daniel like hey.00:34:19.210 --> 00:34:21.980 I, uh, I have a, you know,00:34:21.980 --> 00:34:22.905 a lot of meetings today.00:34:22.910 --> 00:34:23.806 Daniel, be like what?00:34:23.806 --> 00:34:25.393 Let's look at that and he'll try00:34:25.393 --> 00:34:26.730 to get you out of the meeting.00:34:26.730 --> 00:34:28.932 So it's definitely something that we're00:34:28.932 --> 00:34:31.280 all passionate about trying to make better,00:34:31.280 --> 00:34:33.600 so don't feel like you00:34:33.600 --> 00:34:35.920 have to attend a meeting.00:34:35.920 --> 00:34:37.145 Uh, just because you were00:34:37.145 --> 00:34:38.370 added to that meeting you,00:34:38.370 --> 00:34:40.638 you are allowed to decline meetings,00:34:40.640 --> 00:34:43.084 particularly same day meetings.00:34:43.084 --> 00:34:46.139 I would encourage everybody to00:34:46.139 --> 00:34:48.587 decline any same day meeting00:34:48.590 --> 00:34:50.466 unless it's absolutely urgent,00:34:50.466 --> 00:34:54.790 beat me to exactly what I was about to say.00:34:54.790 --> 00:34:57.662 I look at my calendar the night before00:34:57.662 --> 00:34:59.965 like before I before I go to bed.00:34:59.970 --> 00:35:02.154 I look at my calendar and if there's00:35:02.154 --> 00:35:04.696 a if a new meeting appears on my00:35:04.696 --> 00:35:07.252 calendar on the same day that I didn't00:35:07.252 --> 00:35:10.310 know about and that isn't super important.00:35:10.310 --> 00:35:13.014 I'm not gonna go to it because I00:35:13.014 --> 00:35:15.190 plan out what I'm gonna work on and00:35:15.253 --> 00:35:17.365 that kind of stuff gets in the way.00:35:17.370 --> 00:35:19.630 Uhm, and I very strongly00:35:19.630 --> 00:35:21.890 recommend the same for everybody,00:35:21.890 --> 00:35:24.180 and if it happens consistently.00:35:24.180 --> 00:35:25.206 Uhm, definitely tell.00:35:25.206 --> 00:35:26.916 Tell somebody about it so00:35:26.916 --> 00:35:28.927 we can figure out you know.00:35:28.930 --> 00:35:30.498 Why that keeps happening?00:35:30.498 --> 00:35:30.890 Uh,00:35:30.890 --> 00:35:32.874 if it's a specific person that's doing it,00:35:32.880 --> 00:35:34.142 just message them and say, hey,00:35:34.142 --> 00:35:35.540 just so you know, uh,00:35:35.540 --> 00:35:37.160 I don't do same day meetings.00:35:37.160 --> 00:35:39.070 I need some heads up so I can plan around00:35:39.123 --> 00:35:40.899 it and make sure that I actually have,00:35:40.900 --> 00:35:41.574 you know,00:35:41.574 --> 00:35:44.270 work I can get done in a day00:35:44.270 --> 00:35:46.190 because I've definitely had days00:35:46.190 --> 00:35:48.545 where the whole the whole day00:35:48.545 --> 00:35:50.314 gets consumed with meetings that00:35:50.314 --> 00:35:52.673 were added at 9:00 in the morning.00:35:52.680 --> 00:35:54.927 That happened at 11 in the morning.00:35:57.930 --> 00:36:00.156 Absolutely. And if we only have like00:36:00.156 --> 00:36:02.509 three meetings and they're all spaced now,00:36:02.510 --> 00:36:04.520 we're apart. I can record a.00:36:06.570 --> 00:36:08.271 Yep, and that's exactly what we need00:36:08.271 --> 00:36:10.417 to kill and or at least be aware of it.00:36:10.420 --> 00:36:12.590 And I mean you you can sort of imagine this00:36:12.646 --> 00:36:14.767 happening if you've ever thought about it,00:36:14.770 --> 00:36:17.370 but like obviously project managers00:36:17.370 --> 00:36:19.810 like they live for meetings, right?00:36:19.810 --> 00:36:22.498 That's what they do whether it's a developer00:36:22.498 --> 00:36:24.610 and it like another internal meeting,00:36:24.610 --> 00:36:25.910 invoicing, meeting, client meeting,00:36:25.910 --> 00:36:27.870 whatever it is, they always have them.00:36:27.870 --> 00:36:29.095 So when they're going to00:36:29.095 --> 00:36:30.192 schedule a meeting, this is.00:36:30.192 --> 00:36:32.266 This is why I want you guys to feel empowered00:36:32.266 --> 00:36:34.289 when they're going to schedule a meeting.00:36:34.290 --> 00:36:37.186 They're trying to fit it into their calendar.00:36:37.190 --> 00:36:40.617 Which is meeting heavy right and the one00:36:40.617 --> 00:36:43.195 time slot that they could fit it in is00:36:43.195 --> 00:36:45.427 most likely not going to work for you,00:36:45.430 --> 00:36:49.990 so you know you can absolutely say like,00:36:49.990 --> 00:36:51.790 hey, that you know that this00:36:51.790 --> 00:36:53.489 is really a problem for me.00:36:53.490 --> 00:36:57.180 Can we please move this meeting and you know?00:36:57.180 --> 00:36:59.931 Just I wanna make sure that you00:36:59.931 --> 00:37:02.880 guys feel empowered. To do that?00:37:02.880 --> 00:37:07.490 Alright, uh billable work OK.00:37:07.490 --> 00:37:11.234 This one is this. One is kind of tricky.00:37:11.240 --> 00:37:13.389 So, uh, but if you're doing something00:37:13.389 --> 00:37:14.860 because the client needs it,00:37:14.860 --> 00:37:15.786 it's billable.00:37:15.786 --> 00:37:16.249 However,00:37:16.249 --> 00:37:19.490 the intent behind seven billable hours per00:37:19.563 --> 00:37:22.590 day is to match what's in your Sprint, right?00:37:22.590 --> 00:37:25.110 The requirement is 7 billable hours a00:37:25.110 --> 00:37:27.918 day and seven ticketed hours per day,00:37:27.920 --> 00:37:30.818 and that they match back to the whole burnup.00:37:30.820 --> 00:37:34.780 Matching what's in your easy projects.00:37:34.780 --> 00:37:36.286 Total hours that would need to00:37:36.286 --> 00:37:37.960 be worked over two weeks is 80.00:37:37.960 --> 00:37:39.645 Obviously if you're somebody who00:37:39.645 --> 00:37:40.993 has a different schedule,00:37:41.000 --> 00:37:42.813 you can do the math and you00:37:42.813 --> 00:37:44.139 know whatever figure that out.00:37:44.140 --> 00:37:44.796 Uhm?00:37:44.796 --> 00:37:49.388 There are 7.5 hours of scheduled meetings00:37:49.390 --> 00:37:51.610 forever that everybody has to attend.00:37:51.610 --> 00:37:53.598 Sprint planning two hours00:37:53.598 --> 00:37:55.586 Friday trainings 4 hours,00:37:55.590 --> 00:37:56.650 two of them over Sprint,00:37:56.650 --> 00:37:58.450 so it's six hours biweekly.00:37:58.450 --> 00:38:01.468 Dev review OPS Review Sprint retro.00:38:01.470 --> 00:38:04.518 That's another hour and a half.00:38:04.520 --> 00:38:06.325 Maybe pushing two so it's00:38:06.325 --> 00:38:08.859 seven and a half to 8 hours,00:38:08.860 --> 00:38:11.600 which leaves 72 hours remaining.00:38:11.600 --> 00:38:13.172 Right, and that 2 1/2 hours00:38:13.172 --> 00:38:15.138 can be used for like you know,00:38:15.140 --> 00:38:16.368 logging time, updating tickets,00:38:16.368 --> 00:38:18.210 other meetings that may come up,00:38:18.210 --> 00:38:20.345 which means that everybody should00:38:20.345 --> 00:38:22.830 be able to relatively easily hit.00:38:22.830 --> 00:38:24.990 The uh billable hour mark,00:38:24.990 --> 00:38:27.600 even without making Sprint planning billable.00:38:29.890 --> 00:38:31.606 And I accidentally went to the00:38:31.606 --> 00:38:35.360 next slide there. Uhm? So.00:38:37.510 --> 00:38:41.110 There's been like some people will will mark.00:38:41.110 --> 00:38:44.267 Sprint planning is billable, and that's OK.00:38:44.270 --> 00:38:45.670 If you're, you know,00:38:45.670 --> 00:38:48.134 for any project you're on, like if00:38:48.134 --> 00:38:51.320 you're on RX1 and it takes PJ minute PJ,00:38:51.320 --> 00:38:52.766 15 minutes and Sprint planning to00:38:52.766 --> 00:38:54.877 go through all of our X1 and you're00:38:54.877 --> 00:38:56.242 paying attention that entire time,00:38:56.250 --> 00:38:58.602 like yeah .25 RX.00:38:58.602 --> 00:39:01.276 One meeting billable, that's fine.00:39:01.276 --> 00:39:04.447 Doesn't really go towards your goal though,00:39:04.450 --> 00:39:07.626 right? Because your goal is 7 billable hours.00:39:07.630 --> 00:39:08.802 And seven ticketed hours.00:39:08.802 --> 00:39:10.560 And we don't create a ticket00:39:10.622 --> 00:39:11.708 for Sprint planning.00:39:11.710 --> 00:39:14.820 We account for Sprint planning.00:39:14.820 --> 00:39:17.916 To be a part of these scheduled meetings00:39:17.916 --> 00:39:19.656 of potentially non billable time.00:39:19.656 --> 00:39:22.360 But we can you can think of this00:39:22.432 --> 00:39:24.587 as non ticketable time really.00:39:24.590 --> 00:39:26.650 Uhm?00:39:26.650 --> 00:39:29.026 So I just wanted to be clear on that.00:39:29.030 --> 00:39:31.196 Basically your your your goal of00:39:31.196 --> 00:39:33.658 seven billable hours per day is to00:39:33.658 --> 00:39:35.560 match seven ticketed hours per day.00:39:35.560 --> 00:39:37.102 So when you're going through and00:39:37.102 --> 00:39:39.118 doing your time logs at the end of00:39:39.118 --> 00:39:40.516 the day and updating your tickets,00:39:40.520 --> 00:39:44.000 the seven hours that you enter into easy00:39:44.000 --> 00:39:47.546 projects or whatever it is that's billable.00:39:47.550 --> 00:39:49.365 You should immediately be able00:39:49.365 --> 00:39:51.952 to go over into Azure and Mark00:39:51.952 --> 00:39:53.697 7 hours of completed time.00:39:53.700 --> 00:39:54.057 Uh,00:39:54.057 --> 00:39:55.128 on your tickets.00:39:57.260 --> 00:39:59.294 I know this is kind of one that's been00:39:59.294 --> 00:40:01.638 confusing, so I'll stop there to see00:40:01.638 --> 00:40:04.580 if anybody has any questions on that.00:40:04.580 --> 00:40:06.050 Does that make sense to everybody?00:40:12.490 --> 00:40:16.180 Alright. JL You got something just00:40:16.180 --> 00:40:18.592 gonna throw out something like a throw00:40:18.592 --> 00:40:20.608 this thing out there quite a bit.00:40:20.610 --> 00:40:23.832 This little time logs like Excel00:40:23.832 --> 00:40:26.970 spreadsheet that I use 'cause it has00:40:26.970 --> 00:40:29.657 our lets you mark every period that you00:40:29.657 --> 00:40:32.384 record on there as a billable or a noble.00:40:32.390 --> 00:40:34.210 And then I've also taken the marking00:40:34.210 --> 00:40:35.750 things that are technically building00:40:35.750 --> 00:40:37.880 that ticketed as billich with little00:40:37.880 --> 00:40:39.660 question mark after the bill it'll00:40:39.660 --> 00:40:41.563 properly not show that in your main00:40:41.563 --> 00:40:43.428 billable accounts for that day.00:40:43.430 --> 00:40:46.142 I let me just grab that so I00:40:46.142 --> 00:40:48.050 can pop in the chat.00:40:48.050 --> 00:40:50.522 Yeah, it took my original time00:40:50.522 --> 00:40:52.670 for hours down from like.00:40:52.670 --> 00:40:55.764 At 3030 to 45 minutes a day00:40:55.764 --> 00:40:57.900 sounds like this 15 ish.00:40:57.900 --> 00:41:01.610 If I can just find where I put the template.00:41:01.610 --> 00:41:02.714 Awesome, thanks for that.00:41:02.714 --> 00:41:04.659 I just wanted to let everybody know00:41:04.659 --> 00:41:06.515 that there is a small blue macaroni in00:41:06.515 --> 00:41:08.377 the bottom left corner of the slide.00:41:12.940 --> 00:41:15.054 Looks like it could use some Velveeta.00:41:15.060 --> 00:41:17.940 Jeez Alex, you had your hand up first.00:41:17.940 --> 00:41:20.170 I think what you got.00:41:20.170 --> 00:41:22.000 Yeah, so where does uh,00:41:22.000 --> 00:41:25.857 assisting other people go into these hours?00:41:25.860 --> 00:41:28.072 So like if I randomly get a00:41:28.072 --> 00:41:29.570 message during the Sprint?00:41:29.570 --> 00:41:30.728 Hey I need help with this.00:41:30.730 --> 00:41:32.935 Can you help me? I spend maybe00:41:32.935 --> 00:41:35.180 one hour or two hours assisting.00:41:35.180 --> 00:41:37.930 How does this go into?00:41:37.930 --> 00:41:41.150 Uh, these hours that you have listed.00:41:41.150 --> 00:41:41.810 Let me ask,00:41:41.810 --> 00:41:43.981 let me let me respond to that with a00:41:43.981 --> 00:41:45.983 question before the other guys answer it.00:41:45.990 --> 00:41:47.988 What do you think Alex like?00:41:47.990 --> 00:41:49.200 If you had to guess,00:41:49.200 --> 00:41:53.256 I would just counted as billable.00:41:53.260 --> 00:41:56.090 But uhm.00:41:56.090 --> 00:41:57.400 I'm unsure like a way00:41:57.400 --> 00:41:59.180 to put it in like Azure,00:41:59.180 --> 00:42:00.620 for example where you don't00:42:00.620 --> 00:42:03.550 have an assist ticket, so.00:42:03.550 --> 00:42:08.110 My personal recommendation, UM is hey,00:42:08.110 --> 00:42:09.980 if it's happening frequently enough?00:42:09.980 --> 00:42:12.062 UM, like if you're if you're00:42:12.062 --> 00:42:13.875 spending an appreciable number of00:42:13.875 --> 00:42:15.690 hours every Sprint helping people,00:42:15.690 --> 00:42:18.567 you should probably have an assist ticket.00:42:18.570 --> 00:42:20.340 If that's happening a lot.00:42:20.340 --> 00:42:21.448 But if you don't,00:42:21.448 --> 00:42:24.238 you can make a ticket in your own Sprint.00:42:24.240 --> 00:42:25.280 Typically there's a user00:42:25.280 --> 00:42:26.840 story that all of us have.00:42:26.840 --> 00:42:29.846 That's called all unplanned work items.00:42:29.850 --> 00:42:32.118 Uhm, it's usually tored the top.00:42:32.120 --> 00:42:33.928 If something like that comes up for me,00:42:33.930 --> 00:42:36.890 I usually make a new ticket there and00:42:36.890 --> 00:42:39.690 I'll give it whatever client it's on.00:42:39.690 --> 00:42:41.967 Put that bracket at the front and then say,00:42:41.970 --> 00:42:43.395 assist with whoever.00:42:43.395 --> 00:42:46.160 So if it's if it's, you know.00:42:46.160 --> 00:42:47.525 If I was asking you for help,00:42:47.530 --> 00:42:47.847 Alex,00:42:47.847 --> 00:42:49.749 you'd make a ticket that says00:42:49.750 --> 00:42:51.166 and we were working on RO.00:42:51.170 --> 00:42:52.802 It would say row assist with00:42:52.802 --> 00:42:54.538 Bell and you would leave the00:42:54.538 --> 00:42:56.013 original and remaining as zero00:42:56.013 --> 00:42:57.911 and in the completed put however00:42:57.911 --> 00:43:00.137 long you're in the call that way.00:43:00.140 --> 00:43:02.524 It's at least reflected in your burn up.00:43:02.530 --> 00:43:03.057 Uhm,00:43:03.057 --> 00:43:06.746 and the PM's can see that oh00:43:06.750 --> 00:43:09.174 something came up that he had to help00:43:09.174 --> 00:43:11.426 with and we have to do some flex.00:43:11.430 --> 00:43:14.398 Now that being said.00:43:14.400 --> 00:43:17.856 If you're spending a lot of time assisting,00:43:17.860 --> 00:43:20.415 that's not ticketed, that can be prop.00:43:20.420 --> 00:43:21.280 That can be a problem,00:43:21.280 --> 00:43:23.352 because you know we we we assign the00:43:23.352 --> 00:43:25.668 work in the Sprint planning with the00:43:25.668 --> 00:43:27.999 expectation that it's going to get done.00:43:28.000 --> 00:43:29.908 And if everybody is asking one00:43:29.908 --> 00:43:31.936 specific person for help that doesn't00:43:31.936 --> 00:43:34.018 have actual allocated time to help,00:43:34.020 --> 00:43:35.058 that person is not going to00:43:35.058 --> 00:43:36.230 get any of their stuff done.00:43:36.230 --> 00:43:37.610 So if you're getting a lot00:43:37.610 --> 00:43:38.987 of requests for help and you00:43:38.987 --> 00:43:40.394 don't have the time to do it,00:43:40.400 --> 00:43:42.512 or you can foresee that it's actively going00:43:42.512 --> 00:43:44.748 to stop you from completing other tasks.00:43:44.750 --> 00:43:46.055 You should probably.00:43:46.055 --> 00:43:46.490 Uh,00:43:46.490 --> 00:43:48.230 politely politely redirected them00:43:48.230 --> 00:43:50.916 to like James Gray office hours or00:43:50.916 --> 00:43:53.245 or somebody else that that actually00:43:53.245 --> 00:43:55.454 usually has allocation specifically00:43:55.454 --> 00:43:59.498 for these kind of assist sessions.00:43:59.500 --> 00:44:02.727 OK, thank you. Yeah, great job Brandon.00:44:02.730 --> 00:44:03.426 Thank you.00:44:03.426 --> 00:44:04.470 Yeah essentially Alex,00:44:04.470 --> 00:44:05.975 it has to be in a ticket.00:44:05.980 --> 00:44:08.748 UM, it's the really short answer to that.00:44:08.750 --> 00:44:09.896 As Brendan said.00:44:09.896 --> 00:44:12.188 And then I think KB yeah,00:44:12.190 --> 00:44:14.424 go for it man. Hey yeah, uh,00:44:14.424 --> 00:44:17.169 so one of the things I do is I try00:44:17.169 --> 00:44:19.836 to reach out to the project manager00:44:19.836 --> 00:44:22.322 for whoever I'm assisting on their00:44:22.322 --> 00:44:24.674 project and I'm I let the project00:44:24.674 --> 00:44:26.983 manager to know that I've kind of00:44:26.983 --> 00:44:28.860 jumped into a working session.00:44:28.860 --> 00:44:31.780 And you know, for instance.00:44:31.780 --> 00:44:33.910 One of the other developers we00:44:33.910 --> 00:44:35.800 spent 45 minutes on a working00:44:35.800 --> 00:44:37.861 session in the check back up on00:44:37.861 --> 00:44:39.709 me and then we had to jump into00:44:39.777 --> 00:44:41.777 another problem solving session.00:44:41.780 --> 00:44:43.644 So it took about an hour and a00:44:43.644 --> 00:44:45.146 half and I just let the project00:44:45.146 --> 00:44:46.270 manager know and be like,00:44:46.270 --> 00:44:47.071 hey you know,00:44:47.071 --> 00:44:48.940 can you give me a ticket for00:44:49.013 --> 00:44:50.771 the this system work or whatever00:44:50.771 --> 00:44:53.283 if you if you reach out to the00:44:53.283 --> 00:44:54.873 project manager and then they00:44:54.873 --> 00:44:56.775 can worry about moving stuff out00:44:56.775 --> 00:44:58.350 with the other project managers,00:44:58.350 --> 00:45:00.078 it's going to be super helpful00:45:00.078 --> 00:45:01.230 to your burn down.00:45:03.930 --> 00:45:06.975 Awesome thanks man. And then Brandon flirty.00:45:11.330 --> 00:45:16.840 Uh, well. One thing, uh, that.00:45:16.840 --> 00:45:19.290 I'm not saying that unbillable00:45:19.290 --> 00:45:22.480 hours don't need to be locked,00:45:22.480 --> 00:45:24.601 but I don't understand the the reason00:45:24.601 --> 00:45:26.888 behind that why they have to be logged?00:45:29.100 --> 00:45:33.250 The non billable hours uhm.00:45:33.250 --> 00:45:34.242 Yeah, that's a great.00:45:34.242 --> 00:45:35.920 That's a that's a good question to,00:45:35.920 --> 00:45:37.276 uh, basically like.00:45:37.276 --> 00:45:39.536 If somebody there are people00:45:39.536 --> 00:45:42.468 that are currently not in Friday00:45:42.468 --> 00:45:44.306 training right now, right?00:45:44.306 --> 00:45:46.186 Whether it's they had something00:45:46.186 --> 00:45:48.369 else or they they you know,00:45:48.370 --> 00:45:50.281 message me and they needed to like00:45:50.281 --> 00:45:51.966 leave early there doctors appointment00:45:51.966 --> 00:45:54.379 or whatever and and technically,00:45:54.379 --> 00:45:57.577 while this is not billable time,00:45:57.580 --> 00:45:59.385 this is time that you're00:45:59.385 --> 00:46:01.190 getting paid for by clarity.00:46:01.190 --> 00:46:04.086 So if you're not in this Friday training,00:46:04.090 --> 00:46:06.106 that's two less hours that you've worked.00:46:06.110 --> 00:46:08.762 And if you don't make that up technically.00:46:08.762 --> 00:46:10.422 You would need to take00:46:10.422 --> 00:46:12.190 PTO for those two hours.00:46:16.410 --> 00:46:20.462 OK. Uhm? Cool, alright,00:46:20.462 --> 00:46:24.760 and then we'll go ahead and go00:46:24.891 --> 00:46:28.280 to the next one and. Uh, maybe.00:46:30.650 --> 00:46:34.990 Oh my gosh, it's out of control00:46:34.990 --> 00:46:37.818 man. Alright, uh could be.00:46:40.340 --> 00:46:41.978 Oh he he already went KB.00:46:41.980 --> 00:46:44.866 Did you have something else though?00:46:44.870 --> 00:46:48.240 No, no, sorry about that, uh.00:46:48.240 --> 00:46:52.550 Thanks all right. David Frederick.00:46:52.550 --> 00:46:55.016 Yeah, near thank you alright cool.00:46:55.020 --> 00:46:57.300 Can you read this next one for me?00:46:57.300 --> 00:46:59.404 What the top three?00:46:59.404 --> 00:47:01.030 Uh, I mean those are short.00:47:01.030 --> 00:47:03.556 Let's do like the first six or six.00:47:03.556 --> 00:47:05.640 Oh man come on. OK alright.00:47:05.640 --> 00:47:07.715 Only projects here on why00:47:07.715 --> 00:47:09.669 does the client want it?00:47:09.670 --> 00:47:11.294 What are they going to use it for?00:47:11.300 --> 00:47:13.530 Be a resource for other00:47:13.530 --> 00:47:15.314 developers on the project.00:47:15.320 --> 00:47:18.920 So no, it's going on on your projects.00:47:18.920 --> 00:47:22.063 A long time well enough that you00:47:22.063 --> 00:47:24.979 never get pinged by the OPS team.00:47:24.980 --> 00:47:28.022 Update tickets daily and keep it00:47:28.022 --> 00:47:30.580 consistent with your time logs.00:47:30.580 --> 00:47:31.966 Communicate before tasks.00:47:31.966 --> 00:47:34.276 Go over and explain why.00:47:34.280 --> 00:47:36.380 Participate in Sprint retro00:47:36.380 --> 00:47:39.005 ask about a career plan.00:47:39.010 --> 00:47:40.078 Why do you want?00:47:40.078 --> 00:47:42.649 What do you want to do that clarity?00:47:47.450 --> 00:47:50.380 Awesome, awesome, uh and then,00:47:50.380 --> 00:47:53.266 uh, let's go with Michael Perez.00:47:53.270 --> 00:47:54.608 Can you read the next three?00:47:54.610 --> 00:47:55.930 Actually, just do the next five.00:47:55.930 --> 00:47:57.379 You got it, man, I have faith in you.00:47:59.590 --> 00:48:01.294 Right, great documentation.00:48:01.294 --> 00:48:04.134 Do something that was challenging.00:48:04.140 --> 00:48:06.583 Write a new, clean article so that00:48:06.583 --> 00:48:08.577 next time someone has to do it,00:48:08.580 --> 00:48:11.040 it won't be as challenging.00:48:11.040 --> 00:48:13.630 Get help from another developer.00:48:13.630 --> 00:48:16.150 Write a stack overflow posts and provide00:48:16.150 --> 00:48:18.378 the answers so that another developer00:48:18.378 --> 00:48:20.898 can search for it in the future.00:48:20.900 --> 00:48:23.612 Project is in trouble.00:48:23.612 --> 00:48:26.462 Demo tomorrow, work late and shred00:48:26.462 --> 00:48:29.435 on it and don't work on another00:48:29.435 --> 00:48:32.710 project until this one is good to go.00:48:32.710 --> 00:48:34.194 Be comfortable troubleshooting in00:48:34.194 --> 00:48:37.103 the front end or back end if you're00:48:37.103 --> 00:48:39.252 a back end or front end developer.00:48:39.260 --> 00:48:40.916 Take your shot.00:48:40.916 --> 00:48:43.676 Problems are opportunities in disguise.00:48:43.680 --> 00:48:45.696 Have a task that nobody at00:48:45.696 --> 00:48:47.040 clarity has done before.00:48:47.040 --> 00:48:48.410 It's your time to shine.00:48:51.690 --> 00:48:53.130 Michael, that was moving.00:48:53.130 --> 00:48:55.599 That was awesome dude. I love that.00:48:55.599 --> 00:48:58.000 So basically this is just a little00:48:58.077 --> 00:49:00.993 short thing on on how you can look good.00:49:01.000 --> 00:49:03.670 These are not necessarily requirements,00:49:03.670 --> 00:49:06.235 right? Like nobody is going to get mad at00:49:06.235 --> 00:49:08.989 you for not participating in Sprint retro,00:49:08.990 --> 00:49:12.938 but these if you do these things00:49:12.940 --> 00:49:14.948 you there will be no limit to the00:49:14.948 --> 00:49:17.026 amount of money you make it clarity.00:49:17.030 --> 00:49:18.914 It will just keep going and00:49:18.914 --> 00:49:20.640 going and going and going.00:49:20.640 --> 00:49:23.874 Uh, so this this this screen00:49:23.874 --> 00:49:26.030 right here is probably.00:49:26.030 --> 00:49:27.498 Probably the most important00:49:27.498 --> 00:49:29.700 for your for your bottom line.00:49:29.700 --> 00:49:31.144 Your personal bottom line,00:49:31.144 --> 00:49:32.678 if you take, you know.00:49:32.678 --> 00:49:34.470 Hopefully you take a lot away from this,00:49:34.470 --> 00:49:36.675 but I guess if you take nothing00:49:36.675 --> 00:49:38.874 else away this slide will should00:49:38.874 --> 00:49:40.829 be of interest to everybody.00:49:40.830 --> 00:49:42.702 The problems one is a really00:49:42.702 --> 00:49:44.630 big one in my opinion.00:49:44.630 --> 00:49:47.395 I like I like problem solving personally,00:49:47.400 --> 00:49:53.049 but from a career standpoint it's huge too.00:49:53.050 --> 00:49:55.220 Find a problem or or or come00:49:55.220 --> 00:49:57.360 across a problem that's that blocks00:49:57.360 --> 00:50:00.128 you and being the one that says,00:50:00.130 --> 00:50:01.090 well, you know what.00:50:01.090 --> 00:50:03.331 I'll try to figure it out and you know00:50:03.331 --> 00:50:04.933 probably sometimes you're going to go00:50:04.933 --> 00:50:07.058 over on a task as long as you communicate.00:50:07.060 --> 00:50:10.350 It's mostly OK, just don't.00:50:10.350 --> 00:50:12.856 You know, don't waste too much time,00:50:12.860 --> 00:50:14.140 but just put in that.00:50:14.140 --> 00:50:16.462 Put in that extra level of effort of like.00:50:16.470 --> 00:50:18.408 I mean, this is my job.00:50:18.410 --> 00:50:20.050 I might as well see if I can00:50:20.050 --> 00:50:22.183 figure this thing out and I can.00:50:22.183 --> 00:50:24.589 I can tell you with certainty00:50:24.589 --> 00:50:26.949 that the more you do that,00:50:26.950 --> 00:50:30.210 the more valuable you are.00:50:30.210 --> 00:50:30.514 And.00:50:30.514 --> 00:50:31.426 It it is,00:50:31.426 --> 00:50:34.060 it is noticed and it is rewarded.00:50:37.850 --> 00:50:40.559 Awesome thanks man.00:50:40.560 --> 00:50:45.416 Alright, and then go into the next one.00:50:45.420 --> 00:50:47.682 Let's let's go with oh a00:50:47.682 --> 00:50:50.940 TMC sorry man, go ahead.00:50:50.940 --> 00:50:53.712 Yeah, so sorry surfer dude last00:50:53.712 --> 00:50:55.447 second there, now you're good.00:50:55.447 --> 00:50:57.330 I'll go back on good terms with00:50:57.389 --> 00:50:59.237 the new Clean Articles and stuff.00:50:59.240 --> 00:51:01.232 Like I I don't mind writing00:51:01.232 --> 00:51:02.918 documentation stuff about let's say00:51:02.918 --> 00:51:04.676 problems or even let's say there's00:51:04.676 --> 00:51:06.651 a new feature or something or like00:51:06.651 --> 00:51:08.770 for example do it for the installer.00:51:11.310 --> 00:51:13.810 I feel as though and I know I'm a noob,00:51:13.810 --> 00:51:16.547 so my opinions are pretty much irrelevant,00:51:16.550 --> 00:51:19.970 but I feel as though if some of that00:51:19.970 --> 00:51:21.982 could be depending on the situation.00:51:21.982 --> 00:51:23.948 Of course, if some of that could be00:51:23.948 --> 00:51:25.730 counted towards some kind of billable time,00:51:25.730 --> 00:51:28.660 it might incentivize people to.00:51:28.660 --> 00:51:30.516 Put effort into that,00:51:30.516 --> 00:51:32.836 and that would probably make.00:51:32.840 --> 00:51:33.840 Not Even so much,00:51:33.840 --> 00:51:34.840 just for on boarding,00:51:34.840 --> 00:51:36.820 just for other developers like hey,00:51:36.820 --> 00:51:38.932 if you could look up half the stuff00:51:38.932 --> 00:51:41.098 you run into and it was someone00:51:41.098 --> 00:51:42.354 already dealt with it.00:51:42.360 --> 00:51:44.866 That would be that would save a00:51:44.866 --> 00:51:47.745 bunch of time and you know it would00:51:47.745 --> 00:51:49.442 alleviate the the communication stress00:51:49.442 --> 00:51:51.999 of having to reach out to people all00:51:51.999 --> 00:51:54.238 the time to help you were hired about00:51:54.238 --> 00:51:57.114 one month after we set up a document00:51:57.114 --> 00:51:59.134 that specifies exactly those things00:51:59.134 --> 00:52:02.874 we have a we have a bounty at bounty topics.00:52:02.880 --> 00:52:05.730 Document that specifies sort of the.00:52:05.730 --> 00:52:07.330 Uh, the highest priority things.00:52:07.330 --> 00:52:09.688 The team wants documentation for me?00:52:09.690 --> 00:52:12.858 Uh, and a handful of us actually do get00:52:12.858 --> 00:52:16.129 Sprint allocation for writing documentation.00:52:16.130 --> 00:52:18.170 That document I didn't know about00:52:18.170 --> 00:52:20.598 that you know that's a good question.00:52:20.600 --> 00:52:21.503 I don't actually.00:52:21.503 --> 00:52:22.406 It's in here.00:52:22.410 --> 00:52:23.355 Brooke has it.00:52:23.355 --> 00:52:24.615 Uhm, I don't I.00:52:24.620 --> 00:52:25.928 I'm sure that there's a place00:52:25.928 --> 00:52:27.348 that lives that we can get at,00:52:27.350 --> 00:52:28.855 but I don't remember where it is.00:52:28.860 --> 00:52:30.672 Do you want like the information00:52:30.672 --> 00:52:32.939 on the bounty or the spreadsheet?00:52:32.940 --> 00:52:34.630 With all the the spreadsheet00:52:34.630 --> 00:52:36.664 would probably be the the ideal00:52:36.664 --> 00:52:38.840 one that we could get it and see.00:52:38.840 --> 00:52:41.756 But yeah, Brendan, this was that.00:52:41.760 --> 00:52:42.456 If you remember,00:52:42.456 --> 00:52:44.080 I think this was about a month.00:52:44.080 --> 00:52:46.624 Maybe it was like two months ago even.00:52:46.630 --> 00:52:48.730 Where we in a Friday training we00:52:48.730 --> 00:52:51.190 all voted on a bunch of different00:52:51.190 --> 00:52:53.045 topics in a huge spreadsheet.00:52:53.050 --> 00:52:53.501 UM,00:52:53.501 --> 00:52:56.658 and there were a bunch of different00:52:56.658 --> 00:52:58.835 documentation topics that were like00:52:58.835 --> 00:53:01.621 soffron incept back in connect PM OPS,00:53:01.630 --> 00:53:04.622 stuff like that and we all voted on00:53:04.622 --> 00:53:07.395 different ones that we wanted to see00:53:07.395 --> 00:53:09.998 documentation for and now this final list,00:53:09.998 --> 00:53:12.747 the one that broke just sent is sort00:53:12.747 --> 00:53:15.044 of tallied up with where most of those00:53:15.044 --> 00:53:17.449 votes were spent so you can see the topics.00:53:17.450 --> 00:53:19.460 Are most looking forward to.00:53:19.460 --> 00:53:22.410 Uhm so.00:53:22.410 --> 00:53:24.258 Uhm, that is.00:53:24.258 --> 00:53:27.670 Excuse me, sorry, that is actually it's.00:53:27.670 --> 00:53:29.430 It's funny that you mentioned that you know.00:53:29.430 --> 00:53:31.050 Like I said you you,00:53:31.050 --> 00:53:32.834 you came in right after we kind of00:53:32.834 --> 00:53:34.456 started to get that set up exactly00:53:34.456 --> 00:53:36.150 pretty much exactly as you described it,00:53:36.150 --> 00:53:38.880 which is providing allocation and00:53:38.880 --> 00:53:41.610 incentive to get the documentation.00:53:41.610 --> 00:53:43.050 To actually, yes.00:53:43.050 --> 00:53:44.490 Having said that,00:53:44.490 --> 00:53:47.176 that is not what this is about, right?00:53:47.176 --> 00:53:49.861 So like that is 100% true.00:53:49.861 --> 00:53:51.116 That'll be in that situation00:53:51.116 --> 00:53:52.530 will be in your Sprint.00:53:52.530 --> 00:53:55.570 This is a CHEAT SHEET for you to look good.00:53:55.570 --> 00:53:56.176 Right now.00:53:56.176 --> 00:53:56.782 I mean,00:53:56.782 --> 00:53:58.297 if you complete good documentation00:53:58.297 --> 00:54:00.774 in your Sprint, that's that's good.00:54:00.774 --> 00:54:01.750 That's fine,00:54:01.750 --> 00:54:04.126 but what will look even better00:54:04.130 --> 00:54:06.594 is if you run into something and00:54:06.594 --> 00:54:07.650 you just do00:54:07.730 --> 00:54:09.618 it right and you end up working00:54:09.618 --> 00:54:11.600 9 or 10 hours in the day.00:54:11.600 --> 00:54:13.520 That's the situation I'm referring to.00:54:13.520 --> 00:54:15.936 Here again, you don't have to do that.00:54:15.940 --> 00:54:17.380 This is just a hey,00:54:17.380 --> 00:54:19.099 you want to look good and make more money.00:54:19.100 --> 00:54:22.670 Here's your playbook right here, boom.00:54:22.670 --> 00:54:24.630 So it's still internal billable.00:54:24.630 --> 00:54:27.762 Whether you have a task for it or not.00:54:27.770 --> 00:54:28.670 But if you don't have it,00:54:28.670 --> 00:54:30.510 ask for it back to what we were00:54:30.510 --> 00:54:31.786 talking about before you know if00:54:31.786 --> 00:54:32.850 you don't have a task for it,00:54:32.850 --> 00:54:34.488 it's not, you know it it?00:54:34.490 --> 00:54:36.569 Yeah, it's internal billable, but it's not.00:54:36.570 --> 00:54:38.388 It shouldn't be what you use00:54:38.388 --> 00:54:39.930 going toward your billable goal,00:54:39.930 --> 00:54:41.982 and you can ask for a task for it.00:54:41.990 --> 00:54:43.802 But what would look even better00:54:43.802 --> 00:54:45.470 is if you just do it.00:54:45.470 --> 00:54:47.045 And then paying the channel and say,00:54:47.050 --> 00:54:48.818 hey, I ran into this and I made00:54:48.818 --> 00:54:50.402 a new clean oh article because00:54:50.402 --> 00:54:52.320 it was a pain in the ***.00:54:58.890 --> 00:55:01.445 Alright, and then Isaiah, could you read00:55:01.445 --> 00:55:04.096 the the quick and dirty here for me?00:55:04.100 --> 00:55:07.720 After set front end developers00:55:07.720 --> 00:55:10.510 understand how to create directives in00:55:10.592 --> 00:55:13.178 Angular JS and components in React.00:55:13.180 --> 00:55:14.812 Step back and developers00:55:14.812 --> 00:55:16.852 understand how to create endpoints,00:55:16.860 --> 00:55:19.788 workflows and providers.00:55:19.790 --> 00:55:22.065 I know the basics of Git branching,00:55:22.070 --> 00:55:23.948 committing, pulling, pushing,00:55:23.948 --> 00:55:27.078 make sure you understand what00:55:27.078 --> 00:55:30.326 a task is asking you to do.00:55:30.330 --> 00:55:33.718 Lastly, create a PR when a task00:55:33.718 --> 00:55:36.830 is completed or multiple tasks.00:55:36.830 --> 00:55:37.660 When related.00:55:40.460 --> 00:55:41.860 That was just a quick thing I00:55:41.860 --> 00:55:43.058 put together there at the end00:55:43.058 --> 00:55:44.168 because I wanted to go ahead,00:55:44.170 --> 00:55:45.365 burn, and you're probably we're00:55:45.365 --> 00:55:46.560 probably on the same wavelength.00:55:46.560 --> 00:55:49.296 Go for it. I was gonna say, UM,00:55:49.296 --> 00:55:51.026 one little quick and dirty.00:55:51.030 --> 00:55:53.685 I'll add is on those first two bullet points.00:55:53.690 --> 00:55:55.172 You can alternate.00:55:55.172 --> 00:55:58.136 The dash is a little bit.00:55:58.140 --> 00:55:59.982 As in, everything after the dash00:55:59.982 --> 00:56:02.059 can be inverted on those top two00:56:02.060 --> 00:56:03.698 and it still stands front end.00:56:03.700 --> 00:56:04.790 Developers may not need to00:56:04.790 --> 00:56:05.880 know how to create endpoints,00:56:05.880 --> 00:56:07.125 workflows and providers,00:56:07.125 --> 00:56:09.615 but you should absolutely know what00:56:09.615 --> 00:56:11.855 those things are and how to debug,00:56:11.860 --> 00:56:13.836 at least at a basic level and on00:56:13.836 --> 00:56:15.181 the inverse back end developers00:56:15.181 --> 00:56:17.029 may not need to know how to00:56:17.087 --> 00:56:18.827 create directives in AngularJS,00:56:18.830 --> 00:56:20.272 but you need to know what they00:56:20.272 --> 00:56:21.629 are and how to debug them.00:56:21.630 --> 00:56:23.422 We everybody works better as a team00:56:23.422 --> 00:56:25.449 when we have at least a passing00:56:25.449 --> 00:56:27.725 understanding of what we're all doing and.00:56:27.725 --> 00:56:30.100 I think not only that,00:56:30.100 --> 00:56:32.098 it's just a massive career opportunity00:56:32.098 --> 00:56:34.717 for you to be good at both sides,00:56:34.720 --> 00:56:37.156 so don't pigeonhole yourself into saying,00:56:37.160 --> 00:56:38.714 oh I'm I'm back and I don't.00:56:38.720 --> 00:56:39.860 I don't know anything about Angular.00:56:39.860 --> 00:56:42.359 That's not my job and vice versa.00:56:42.360 --> 00:56:43.680 Don't do that if your friend or something.00:56:43.680 --> 00:56:45.165 I don't know anything about00:56:45.165 --> 00:56:46.056 migrations or workflows,00:56:46.060 --> 00:56:49.508 that's that's all back and stuff you know,00:56:49.508 --> 00:56:51.200 feel, feel free,00:56:51.200 --> 00:56:56.564 even to be well versed in both and and.00:56:56.570 --> 00:56:57.872 Just put in that little bit00:56:57.872 --> 00:56:58.523 of extra knowledge.00:57:01.620 --> 00:57:05.204 Yeah, 100%, I I can say with certainty00:57:05.204 --> 00:57:08.578 that that me and Brandon Lyon and00:57:08.578 --> 00:57:11.710 I I believe Brandon Flarity as well00:57:11.710 --> 00:57:15.766 can in SEV do the obviously back end.00:57:15.770 --> 00:57:18.425 But the front end passively enough that00:57:18.425 --> 00:57:20.630 when we're because we're just one person00:57:20.630 --> 00:57:23.089 and we know exactly what's going on,00:57:23.090 --> 00:57:26.548 we basically render like a front end00:57:26.548 --> 00:57:29.490 developer useless for that user story.00:57:29.490 --> 00:57:31.394 In other words, like we're so efficient.00:57:31.400 --> 00:57:34.030 Edit that we can almost do it in half the00:57:34.095 --> 00:57:36.746 time because we it's just one person, right?00:57:36.746 --> 00:57:38.678 Like you know exactly what you did.00:57:38.680 --> 00:57:41.116 If you think about how inefficient00:57:41.116 --> 00:57:44.832 it is to pass off like, OK, I did.00:57:44.832 --> 00:57:47.040 This part of this of this user story.00:57:47.040 --> 00:57:48.804 I created the endpoint and then you00:57:48.804 --> 00:57:50.819 pass it to a front end developer.00:57:50.820 --> 00:57:52.512 What if the front end developer00:57:52.512 --> 00:57:54.667 doesn't work on it that same day and00:57:54.667 --> 00:57:56.256 then they wait two days and then00:57:56.256 --> 00:57:58.046 they reach back out and they say hey00:57:58.046 --> 00:57:59.830 I don't know where this is and as00:57:59.830 --> 00:58:01.450 the back end developer you like.00:58:01.450 --> 00:58:02.458 Oh my gosh.00:58:02.458 --> 00:58:02.794 Seriously.00:58:02.794 --> 00:58:03.466 Or conversely,00:58:03.470 --> 00:58:04.772 if you're a front end developer00:58:04.772 --> 00:58:06.273 and you're waiting on a back end00:58:06.273 --> 00:58:07.645 developer and you've asked them to do00:58:07.694 --> 00:58:09.128 something and they haven't done it,00:58:09.130 --> 00:58:11.860 and you've you've started and stopped twice,00:58:11.860 --> 00:58:13.988 you know if you're Jesse who can go00:58:13.988 --> 00:58:16.468 into the back end and actually do stuff,00:58:16.470 --> 00:58:18.950 then you know he can render a back00:58:18.950 --> 00:58:20.784 end developer useless on a feature00:58:20.784 --> 00:58:22.219 or on a user story.00:58:22.220 --> 00:58:25.526 So it is definitely very powerful00:58:25.526 --> 00:58:28.438 and just super efficient.00:58:28.438 --> 00:58:32.368 Yep, imagine the scenario where.00:58:32.370 --> 00:58:33.942 You're working on a new component00:58:33.942 --> 00:58:36.038 or a new thing for the front end,00:58:36.040 --> 00:58:39.296 and you find that you need to slightly00:58:39.296 --> 00:58:42.280 adjust the behavior of some endpoint00:58:42.280 --> 00:58:44.480 instead of blocking the task,00:58:44.480 --> 00:58:45.825 probably having to wait another00:58:45.825 --> 00:58:47.765 Sprint to get it back under assigned00:58:47.765 --> 00:58:49.110 the task to change it,00:58:49.110 --> 00:58:51.670 and then you know all that time later,00:58:51.670 --> 00:58:53.776 potentially up to four weeks later.00:58:53.780 --> 00:58:55.047 You have to come back to task.00:58:55.050 --> 00:58:56.138 You had to stop in the middle of00:58:56.138 --> 00:58:56.600 and you're like.00:58:56.600 --> 00:58:58.456 I don't know what I was doing here.00:58:58.460 --> 00:59:02.650 Instead, imagine having the the.00:59:02.650 --> 00:59:04.862 The knowledge of the ability and the00:59:04.862 --> 00:59:07.230 initiative to just go and look at it.00:59:07.230 --> 00:59:09.580 I mean programming is programming.00:59:09.580 --> 00:59:10.590 If you're good with one,00:59:10.590 --> 00:59:11.750 you'll probably be able to,00:59:11.750 --> 00:59:12.356 you know,00:59:12.356 --> 00:59:14.477 at least fumble your way through another.00:59:14.480 --> 00:59:16.316 Uhm, and there's plenty of samples00:59:16.316 --> 00:59:18.350 of things where you can say, oh,00:59:18.350 --> 00:59:20.342 I see how that works and change00:59:20.342 --> 00:59:21.697 whatever you need to change.00:59:21.700 --> 00:59:22.597 In worst case,00:59:22.597 --> 00:59:24.690 you waste 15 minutes looking at it.00:59:24.690 --> 00:59:26.216 You're like alright, this looks like Greek.00:59:26.220 --> 00:59:27.820 I don't not going to figure it out.00:59:27.820 --> 00:59:29.449 And then you do as you would have done,00:59:29.450 --> 00:59:31.330 blocked the task and say hey I need00:59:31.330 --> 00:59:33.178 it back in here to look at this.00:59:33.180 --> 00:59:35.140 But best case you look at it and you're like,00:59:35.140 --> 00:59:36.028 oh, I see,00:59:36.028 --> 00:59:38.100 fix it and you've just saved everybody.00:59:38.100 --> 00:59:39.148 Four weeks of waiting.00:59:41.340 --> 00:59:42.528 Yeah, and real quick.00:59:42.528 --> 00:59:44.740 Before I let Brendan Flair to go00:59:44.740 --> 00:59:46.188 just connect developers imagine00:59:46.188 --> 00:59:48.418 there's something on you it says00:59:48.418 --> 00:59:50.218 connect developers do the thing.00:59:50.220 --> 00:59:54.960 Habit. Red and clarity go ahead.00:59:54.960 --> 01:00:00.800 Biggest UM efficiency issue I see with.01:00:00.800 --> 01:00:03.014 Uh, not knowing the other end01:00:03.014 --> 01:00:05.756 is a lot of times, uh, you know,01:00:05.756 --> 01:00:07.117 a front runner will say, oh,01:00:07.117 --> 01:00:09.196 this is a back end issue and01:00:09.196 --> 01:00:10.780 they'll stop working on it.01:00:10.780 --> 01:00:12.996 And then you know the back end are01:00:12.996 --> 01:00:15.509 goes in and takes a little get it and01:00:15.509 --> 01:00:17.891 you know it is a back end issue and01:00:17.891 --> 01:00:20.400 they fix it or it isn't a back end issue.01:00:20.400 --> 01:00:21.793 And I say you know it's it's01:00:21.793 --> 01:00:22.879 actually a front end issue.01:00:22.880 --> 01:00:25.664 There's these issues that it's not01:00:25.664 --> 01:00:27.946 happening correctly and there's that01:00:27.946 --> 01:00:30.403 back and forth and that really can.01:00:30.410 --> 01:00:32.482 Can a waste a lot of people a01:00:32.482 --> 01:00:34.798 lot of time on for the project.01:00:37.230 --> 01:00:38.658 Yeah, if that back and forth.01:00:38.660 --> 01:00:39.724 If you're ever participating01:00:39.724 --> 01:00:41.054 in that back and forth,01:00:41.060 --> 01:00:44.288 something has gone wrong, right like?01:00:44.290 --> 01:00:46.261 Please let me know and let me into that01:00:46.261 --> 01:00:48.705 so that we can sort of dive into that01:00:48.705 --> 01:00:50.154 situation because that that should01:00:50.154 --> 01:00:52.128 definitely not be happening at the at01:00:52.130 --> 01:00:55.217 the minimum as a front end developer.01:00:55.220 --> 01:00:56.935 You gotta know when something01:00:56.935 --> 01:00:58.650 is obviously actually back in01:00:58.709 --> 01:01:00.593 issue and conversely the same for01:01:00.593 --> 01:01:02.429 a back end developer for sure,01:01:02.430 --> 01:01:03.780 especially if you're if you're going01:01:03.780 --> 01:01:05.618 to pass that off to another developer,01:01:05.620 --> 01:01:07.144 you you gotta be sure beyond01:01:07.144 --> 01:01:08.590 a shadow of a doubt.01:01:11.330 --> 01:01:12.932 Alright, so any questions on that01:01:12.932 --> 01:01:15.180 any of that so far or any comments?01:01:15.180 --> 01:01:16.284 Uh, it looks like I am going to01:01:16.284 --> 01:01:18.120 take all that. I'm sorry Brendan.01:01:18.120 --> 01:01:20.382 Uh, but uh, we're almost done here,01:01:20.382 --> 01:01:22.339 but any questions on any of that so far?01:01:26.810 --> 01:01:28.784 Alright, now we're gonna get into some01:01:28.784 --> 01:01:31.068 situation in the adventures of Bobby tables.01:01:31.070 --> 01:01:33.326 My guy grew up to be a developer.01:01:33.330 --> 01:01:35.400 He's just he's average skill.01:01:35.400 --> 01:01:36.234 OK, he's not.01:01:36.234 --> 01:01:38.156 It's nothing special, just just average.01:01:38.156 --> 01:01:39.966 You're running the middle developer,01:01:39.970 --> 01:01:43.198 but he's a good clarity developer.01:01:43.200 --> 01:01:44.978 So Bobby tables been a front end01:01:44.978 --> 01:01:46.510 developer at clarity for six months.01:01:46.510 --> 01:01:47.925 He's learned how to create01:01:47.925 --> 01:01:49.057 directives in Angular JS.01:01:49.060 --> 01:01:50.824 He can attach to the back end,01:01:50.830 --> 01:01:52.948 complete basic self tests and he01:01:52.948 --> 01:01:54.640 understands what his limitations are.01:01:54.640 --> 01:01:56.117 He works 9:00 AM to 6:00 PM.01:01:56.120 --> 01:01:58.040 Central time usually logs on01:01:58.040 --> 01:02:00.619 around 8:50 AM every day to prep.01:02:00.620 --> 01:02:02.486 Looks at Azure and a Sprint01:02:02.486 --> 01:02:03.730 board briefly checks teams01:02:03.795 --> 01:02:05.697 channel for the projects he's on.01:02:05.700 --> 01:02:07.716 Doesn't seem to be anything on fire.01:02:07.720 --> 01:02:09.045 He looks through the priorities01:02:09.045 --> 01:02:09.840 on his tickets,01:02:09.840 --> 01:02:11.205 notices that half of them01:02:11.205 --> 01:02:12.297 have a high priority.01:02:12.300 --> 01:02:13.640 He muttered something to himself.01:02:13.640 --> 01:02:15.626 About nothing being a priority if01:02:15.626 --> 01:02:17.630 everything is not getting the clarity he01:02:17.630 --> 01:02:19.580 needs from teams or ticket priorities,01:02:19.580 --> 01:02:21.548 he thinks back to recent discussions01:02:21.548 --> 01:02:23.360 about the projects and recalls.01:02:23.360 --> 01:02:25.080 The demo will be upcoming.01:02:25.080 --> 01:02:27.355 For the clarity project that he's on,01:02:27.360 --> 01:02:29.418 he looks through the user stories assigned01:02:29.418 --> 01:02:31.861 to him and chooses 4 tickets each two01:02:31.861 --> 01:02:34.029 hours belonging to the same user story.01:02:34.030 --> 01:02:35.750 Looking at the children in the user story,01:02:35.750 --> 01:02:37.584 he sees that a back end developer01:02:37.584 --> 01:02:39.265 whose name is Jeff also has01:02:39.265 --> 01:02:40.660 tasks for this user story.01:02:40.660 --> 01:02:43.522 He moves us four tests to active in Azure.01:02:43.530 --> 01:02:45.578 Any messages Jeff to see if he would01:02:45.578 --> 01:02:47.538 have time to work on this together.01:02:47.540 --> 01:02:50.179 Today he looks at his calendar and01:02:50.179 --> 01:02:52.279 immediately shutters too many meetings.01:02:52.280 --> 01:02:54.107 He messages the organizer of the two,01:02:54.110 --> 01:02:55.510 two of the meetings lets them know01:02:55.510 --> 01:02:56.669 that he's going to skip them,01:02:56.670 --> 01:02:58.678 which will give him a nice five hour01:02:58.678 --> 01:03:00.864 block for heads down work by 9:10 AM.01:03:00.864 --> 01:03:01.936 He's ready to go.01:03:04.810 --> 01:03:07.115 Alright, Bobby has 50 minutes01:03:07.115 --> 01:03:10.720 until stand up so he gets started.01:03:10.720 --> 01:03:12.736 He goes to the project folder for clarity.01:03:12.740 --> 01:03:14.258 Make sure he's on support clients.01:03:14.260 --> 01:03:16.150 Clarity QA does get status to01:03:16.150 --> 01:03:18.503 see what he has on his local01:03:18.503 --> 01:03:20.208 to chagrin he has changes.01:03:20.210 --> 01:03:21.510 Upon looking into this,01:03:21.510 --> 01:03:24.010 he realizes they were for this feature.01:03:24.010 --> 01:03:27.740 What should Bobby do next?01:03:27.740 --> 01:03:29.115 Anybody want to volunteer or01:03:29.115 --> 01:03:31.070 I will just pick on somebody?01:03:42.160 --> 01:03:43.960 Alright, just over what should01:03:43.960 --> 01:03:46.864 Bobby do OK B he saved you he01:03:46.864 --> 01:03:49.670 saved you KB what should he do?01:03:49.670 --> 01:03:51.326 You should at least message the01:03:51.326 --> 01:03:53.149 other developer to see what changes.01:03:53.150 --> 01:03:55.850 If it's quick for that developer01:03:55.850 --> 01:03:59.188 to relay those in a short message,01:03:59.190 --> 01:04:01.590 or you can actually review01:04:01.590 --> 01:04:04.480 the code or review the app.01:04:04.480 --> 01:04:07.210 The pool that you just pulled into01:04:07.210 --> 01:04:09.988 your local by going with Azure01:04:09.988 --> 01:04:12.528 and seeing what changes actually.01:04:12.530 --> 01:04:14.780 So he hasn't actually pulled yet, right?01:04:14.780 --> 01:04:16.860 So he what he basically did is he01:04:16.860 --> 01:04:18.999 went to his local and he sees that01:04:18.999 --> 01:04:20.599 he himself made changes like will01:04:20.599 --> 01:04:22.879 say like a week ago and he forgot.01:04:22.879 --> 01:04:25.374 Yeah but committed were uncommitted01:04:25.374 --> 01:04:28.820 work but he has to pull from QA.01:04:28.820 --> 01:04:29.690 So what should he do?01:04:32.300 --> 01:04:35.720 And, uh, do cool absolutely01:04:35.720 --> 01:04:39.626 changes or later on. Yep,01:04:39.626 --> 01:04:42.770 Yep, awesome. Thank you Sir.01:04:46.460 --> 01:04:51.130 Alright, Bobby goes to meetings.01:04:51.130 --> 01:04:53.128 Uh, Bobby hit stand up and then he has01:04:53.128 --> 01:04:55.088 15 minutes until the next meeting.01:04:55.090 --> 01:04:56.710 He uses this time till August.01:04:56.710 --> 01:04:58.982 I'm so far today which looks like this01:04:58.982 --> 01:05:00.524 Jenner admin looking through Sprint01:05:00.524 --> 01:05:03.170 deciding what to work on .5 hour clarity,01:05:03.170 --> 01:05:04.133 task and description.01:05:04.133 --> 01:05:06.059 So we worked on that for01:05:06.059 --> 01:05:07.410 points at that project.01:05:07.410 --> 01:05:09.642 4.75 hours and then he went to the stand01:05:09.642 --> 01:05:12.410 up .25 hour Bobby get some waters.01:05:12.410 --> 01:05:14.293 The meaning is just a few minutes01:05:14.293 --> 01:05:16.129 away and then hops on the call.01:05:16.130 --> 01:05:17.500 This meeting is about another01:05:17.500 --> 01:05:19.453 project that Bobby is on and after01:05:19.453 --> 01:05:21.301 being in the meeting for 15 minutes01:05:21.301 --> 01:05:22.889 that's supposed to last an hour,01:05:22.890 --> 01:05:25.767 he realizes he doesn't have much input.01:05:25.770 --> 01:05:26.520 Josh stover.01:05:26.520 --> 01:05:28.020 What should Bobby do?01:05:31.200 --> 01:05:34.900 Leave a message and drop hell.01:05:34.900 --> 01:05:38.270 Yeah get out of there.01:05:38.270 --> 01:05:40.100 And I hope you guys all01:05:40.100 --> 01:05:41.320 appreciated this graphic because01:05:41.376 --> 01:05:42.760 that is 100% what happens.01:05:49.210 --> 01:05:52.050 All right, Bobby gets stuck.01:05:52.050 --> 01:05:53.765 Bobby was sure he could figure out01:05:53.765 --> 01:05:55.406 that task, but when he looked into it.01:05:58.310 --> 01:05:59.420 It was far more complicated01:05:59.420 --> 01:06:00.710 than he thought it would be,01:06:00.710 --> 01:06:02.090 because you know, Seth.01:06:02.090 --> 01:06:04.160 From the time he got stuck,01:06:04.160 --> 01:06:05.847 he spent 20 minutes spinning his wheels,01:06:05.850 --> 01:06:08.447 but luckily Bobby knows that's the limit.01:06:08.450 --> 01:06:09.354 When making no progress.01:06:09.354 --> 01:06:10.710 So he reaches out for help01:06:10.757 --> 01:06:11.905 and he knows who to go to.01:06:11.910 --> 01:06:12.708 Cornelius Vanderbilt,01:06:12.708 --> 01:06:14.304 a more experienced developer01:06:14.304 --> 01:06:16.220 who knows Seth extremely well.01:06:16.220 --> 01:06:17.490 He messages Cornelius and asked01:06:17.490 --> 01:06:19.285 if he would have a few minutes01:06:19.285 --> 01:06:21.157 tell them and they jump on a call.01:06:21.160 --> 01:06:22.762 He's unstuck in another half hour01:06:22.762 --> 01:06:24.791 because he was able to isolate and01:06:24.791 --> 01:06:26.603 explain the exact problem to Cornelius,01:06:26.610 --> 01:06:29.346 which led to a quick resolution.01:06:29.350 --> 01:06:34.186 Basically, when he went for help.01:06:34.190 --> 01:06:35.690 He knew exactly what lines01:06:35.690 --> 01:06:37.450 of code he was stuck on.01:06:37.450 --> 01:06:39.571 He didn't just call the more experienced01:06:39.571 --> 01:06:41.789 developer and say I don't know what to do.01:06:41.790 --> 01:06:45.108 That's a critical critical thing there.01:06:45.110 --> 01:06:45.437 However,01:06:45.437 --> 01:06:48.053 this resulted in Bobby going over the task.01:06:48.060 --> 01:06:49.558 He ended up spending three hours on01:06:49.558 --> 01:06:51.425 a 2 hour task and was so caught up01:06:51.425 --> 01:06:53.266 in what he was doing he forgot to01:06:53.266 --> 01:06:54.784 message the PM before going over.01:06:54.790 --> 01:06:57.470 What should Bobby do?01:06:57.470 --> 01:06:59.890 Oh Josh, what you got?01:06:59.890 --> 01:07:00.199 Oh,01:07:00.199 --> 01:07:02.362 just real quick shameless plug on the01:07:02.362 --> 01:07:04.300 asking other people for help thing.01:07:04.300 --> 01:07:07.576 We have a document for that now.01:07:07.580 --> 01:07:09.596 You wanna you wanna go get it and drop01:07:09.596 --> 01:07:11.893 it in here do and it is a good document.01:07:11.900 --> 01:07:15.174 I like that one just yeah on01:07:15.174 --> 01:07:18.005 that01:07:18.005 --> 01:07:20.460 you're going to ask for help.01:07:20.460 --> 01:07:24.084 You need to provide more than just a.01:07:24.090 --> 01:07:25.430 Hey, I'm having this issue.01:07:27.500 --> 01:07:28.724 I need you if you're asking01:07:28.724 --> 01:07:29.930 me for help or relief.01:07:29.930 --> 01:07:31.226 Asking anybody for help.01:07:31.226 --> 01:07:33.170 We need more information than that.01:07:33.170 --> 01:07:34.878 It would be terrific,01:07:34.878 --> 01:07:38.510 at the very least you could say hey,01:07:38.510 --> 01:07:41.390 I'm having an issue with XYZ.01:07:41.390 --> 01:07:43.125 I'm getting this error message01:07:43.125 --> 01:07:45.340 in the console or this exception01:07:45.340 --> 01:07:47.674 is being thrown or I check01:07:47.674 --> 01:07:49.882 system log table and found this.01:07:49.890 --> 01:07:51.731 It looks like it might be relevant01:07:51.731 --> 01:07:53.469 just a little something that might01:07:53.469 --> 01:07:55.245 help because I think a handful01:07:55.245 --> 01:07:57.247 of people can probably attest to.01:07:57.250 --> 01:07:59.248 If you give if you give01:07:59.248 --> 01:08:00.247 me enough information,01:08:00.250 --> 01:08:01.864 I'll probably be able to figure01:08:01.864 --> 01:08:03.540 out what it is without having01:08:03.540 --> 01:08:05.409 to get on a call with you.01:08:05.410 --> 01:08:08.254 Last week, Brandon had one where it was like.01:08:08.260 --> 01:08:09.804 Uh, I think it was like logging in01:08:09.804 --> 01:08:11.111 wasn't working and I was like, well,01:08:11.111 --> 01:08:12.857 there's a million causes for that.01:08:12.860 --> 01:08:14.980 And then he sent me a specific line01:08:14.980 --> 01:08:17.694 of code and said this is null and I01:08:17.694 --> 01:08:19.658 immediately knew what the problem was.01:08:19.660 --> 01:08:21.908 And just that little extra bit of detail01:08:21.908 --> 01:08:23.999 is enough sometimes where it's like,01:08:24.000 --> 01:08:24.172 oh,01:08:24.172 --> 01:08:25.548 we don't have to jump in a call01:08:25.548 --> 01:08:26.868 and then you share your screen01:08:26.868 --> 01:08:28.265 and we step through the whole01:08:28.265 --> 01:08:29.480 thing and waste 15 minutes.01:08:29.480 --> 01:08:31.804 If you provide enough information up front,01:08:31.810 --> 01:08:34.730 you can skip the whole the whole thing.01:08:34.730 --> 01:08:36.585 And sometimes we can just01:08:36.585 --> 01:08:38.069 get the solution quickly.01:08:40.720 --> 01:08:42.310 Yeah, and I've often found,01:08:42.310 --> 01:08:44.460 particularly for the front end,01:08:44.460 --> 01:08:47.770 it often comes down to like a block of code.01:08:47.770 --> 01:08:48.790 And just like I,01:08:48.790 --> 01:08:51.069 I just have no idea what it's doing.01:08:51.070 --> 01:08:53.030 You know, especially when I first started,01:08:53.030 --> 01:08:55.334 so you can almost drill it down to that01:08:55.334 --> 01:08:57.237 level of detail where you're like.01:08:57.240 --> 01:08:58.565 I'm really just stuck on01:08:58.565 --> 01:09:00.230 this like this block of code.01:09:00.230 --> 01:09:02.782 I have no idea why it's not working01:09:02.782 --> 01:09:04.993 or what it's doing and getting01:09:04.993 --> 01:09:07.258 that explanation can help so,01:09:07.260 --> 01:09:09.420 but in this case he got caught up.01:09:09.420 --> 01:09:11.744 He went over the task so01:09:11.744 --> 01:09:12.760 he finished the task.01:09:12.760 --> 01:09:14.050 He spent three hours doing it,01:09:14.050 --> 01:09:15.340 it was a 2 hour task.01:09:15.340 --> 01:09:16.755 What should what's the very01:09:16.755 --> 01:09:18.170 next thing he should do?01:09:18.170 --> 01:09:19.140 Michael Perez.01:09:23.140 --> 01:09:25.488 Message that PM immediately.01:09:27.780 --> 01:09:33.428 Yes, Sir. Awesome message the PM and say.01:09:33.430 --> 01:09:37.930 You know? Hey, I went over on this task.01:09:37.930 --> 01:09:41.094 Was heads down. It wasn't, you know,01:09:41.094 --> 01:09:42.450 didn't wasn't paying attention to that.01:09:42.450 --> 01:09:44.482 I'm sorry about that but just wanna let01:09:44.482 --> 01:09:46.840 you know fantastic all right now it's01:09:46.840 --> 01:09:49.909 time for Bobby and Jeff to do the thing,01:09:49.910 --> 01:09:51.302 so it's time for Bobby to01:09:51.302 --> 01:09:53.189 help him do a call with Jeff.01:09:53.190 --> 01:09:55.286 So he calls him and they briefly discuss01:09:55.286 --> 01:09:57.699 what each other had done for this user story.01:09:57.700 --> 01:10:00.124 So again, Jeff is the back end are01:10:00.124 --> 01:10:02.770 on this user story and Bobby is the01:10:02.770 --> 01:10:05.148 front end are Jeff will have back01:10:05.148 --> 01:10:07.647 end code that Bobby needs and they01:10:07.647 --> 01:10:09.546 both pulled from QA that morning.01:10:09.546 --> 01:10:11.154 So they decided that Jeff will.01:10:11.160 --> 01:10:13.592 Push his code when he has it wrapped01:10:13.592 --> 01:10:16.194 up and Bobby will merge it into his01:10:16.194 --> 01:10:18.890 branch so he can complete his tasks.01:10:18.890 --> 01:10:20.762 Bobby is able to do some UI work01:10:20.762 --> 01:10:22.475 while waiting for the back end01:10:22.475 --> 01:10:23.369 functionality from Jeff.01:10:23.370 --> 01:10:24.738 They're able to take turns sharing01:10:24.738 --> 01:10:26.190 their screens to help one another,01:10:26.190 --> 01:10:28.248 and I'm working together for two hours.01:10:28.250 --> 01:10:30.356 They cleared the way for each01:10:30.356 --> 01:10:32.590 other to complete the user story.01:10:32.590 --> 01:10:33.899 Uh, so I wanted to talk about01:10:33.899 --> 01:10:34.840 this for a minute,01:10:34.840 --> 01:10:38.340 a sort of the concept of either01:10:38.340 --> 01:10:41.106 sharing a branch or merging01:10:41.106 --> 01:10:44.006 what somebody else has done.01:10:44.010 --> 01:10:45.130 You know, with their branch,01:10:45.130 --> 01:10:47.092 once they push it up, and, uh,01:10:47.092 --> 01:10:49.164 I mean, I know Brandon Lyon has,01:10:49.170 --> 01:10:50.862 so you can speak on it if you want.01:10:50.870 --> 01:10:52.694 Or if anyone else has just kind of01:10:52.694 --> 01:10:54.518 talk about your experience with that.01:10:57.980 --> 01:11:02.016 KB. Hey yeah I've had a good01:11:02.016 --> 01:11:03.550 screen it says with that.01:11:03.550 --> 01:11:06.814 Uh, I would have and I were working01:11:06.814 --> 01:11:09.820 on the same branch actually and01:11:09.820 --> 01:11:12.810 he would push his stuff up.01:11:12.810 --> 01:11:15.442 And I've merged into my local and we01:11:15.442 --> 01:11:17.699 have that constant communication and01:11:17.699 --> 01:11:20.568 it was really great experience up.01:11:20.568 --> 01:11:23.112 And then you know you have the other01:11:23.112 --> 01:11:25.135 situation where you are basically01:11:25.135 --> 01:11:27.175 pulling down stuff and constantly01:11:27.175 --> 01:11:29.485 making sure that you're up to date01:11:29.485 --> 01:11:32.150 with your bird isn't everything.01:11:32.150 --> 01:11:34.240 It works great both ways.01:11:34.240 --> 01:11:37.066 Just depending on how much communication.01:11:41.090 --> 01:11:42.962 Awesome man thanks.01:11:42.962 --> 01:11:46.430 Yeah 100% if you does any can anybody?01:11:46.430 --> 01:11:48.610 Let's see. Let's see who can I pick on here,01:11:48.610 --> 01:11:55.230 uhm. For Sev, uh Alex Vega,01:11:55.230 --> 01:11:58.386 what is are like naming convention01:11:58.386 --> 01:12:01.300 when you create a branch?01:12:01.300 --> 01:12:04.676 It's the ticket number.01:12:04.676 --> 01:12:09.380 Dash, UM, like what you're doing.01:12:09.380 --> 01:12:14.870 And you would put that under. Uhm?01:12:14.870 --> 01:12:17.174 I don't think he has a good yeah yeah.01:12:17.180 --> 01:12:19.220 I mean no, not really,01:12:19.220 --> 01:12:21.138 but that that could actually be correct.01:12:21.140 --> 01:12:22.862 I don't know, but historically what a01:12:22.862 --> 01:12:24.767 lot of people would do is they'll do,01:12:24.770 --> 01:12:29.946 you know, support clients you know RX one01:12:29.946 --> 01:12:33.990 slash feature slash name of the feature.01:12:33.990 --> 01:12:35.460 And what I was going to point01:12:35.460 --> 01:12:36.809 out is that what KB said,01:12:36.810 --> 01:12:38.895 like you can absolutely share01:12:38.895 --> 01:12:40.900 that branch with somebody, uhm?01:12:40.900 --> 01:12:43.540 You know, because in in that case you're01:12:43.540 --> 01:12:46.149 going to be working on the same feature.01:12:46.150 --> 01:12:49.948 So sharing that branch is, you know, I.01:12:49.948 --> 01:12:51.696 I mean, I love that KB.01:12:51.696 --> 01:12:53.590 I love that I've done that with.01:12:53.590 --> 01:12:54.946 I've done that with Brendan when01:12:54.946 --> 01:12:56.610 we both work on back end stuff,01:12:56.610 --> 01:12:58.320 we've done it with Jesse where01:12:58.320 --> 01:12:59.829 we have different parts of it,01:12:59.830 --> 01:13:01.600 like front and back end.01:13:01.600 --> 01:13:03.004 And it is man.01:13:03.004 --> 01:13:04.759 It is so efficient there's01:13:04.759 --> 01:13:06.788 no other way to say it.01:13:06.790 --> 01:13:10.570 Yeah, it's super successful and.01:13:10.570 --> 01:13:12.390 Not to call the other person out,01:13:12.390 --> 01:13:16.192 but like AT and I we were literally01:13:16.192 --> 01:13:19.170 working on the same page and I was like,01:13:19.170 --> 01:13:19.778 alright, cool.01:13:19.778 --> 01:13:20.690 You know what?01:13:20.690 --> 01:13:23.506 I see some stuff that I can01:13:23.506 --> 01:13:24.946 take care of for you.01:13:24.950 --> 01:13:26.534 I'm going to go ahead and knock it01:13:26.534 --> 01:13:28.256 out for you and then we both push01:13:28.256 --> 01:13:29.680 up emergency QA and we're done.01:13:32.610 --> 01:13:37.641 Yeah. Awesome. Alright,01:13:37.641 --> 01:13:40.346 Bobby gets thrown a curveball.01:13:40.350 --> 01:13:42.270 Uh, Bobby and Jeff had been off their01:13:42.270 --> 01:13:43.928 call for 15 minutes and Bobby was01:13:43.928 --> 01:13:45.683 in the zone when a newer developer01:13:45.683 --> 01:13:47.405 reached out to ask for help.01:13:47.410 --> 01:13:49.180 Bobby had typed a message declining01:13:49.180 --> 01:13:50.970 to help this newer developer,01:13:50.970 --> 01:13:51.874 but before hitting send,01:13:51.874 --> 01:13:53.938 he realized that he had to pay it forward.01:13:53.940 --> 01:13:55.722 What if Cornelius had turned him01:13:55.722 --> 01:13:57.330 down earlier, so he told this new01:13:57.330 --> 01:13:58.560 developer that he would help him.01:13:58.560 --> 01:14:00.710 He ended up being in a call for an hour,01:14:00.710 --> 01:14:02.131 but he was able to help get01:14:02.131 --> 01:14:02.740 the task finished.01:14:02.740 --> 01:14:04.060 It felt great to have helped,01:14:04.060 --> 01:14:05.566 but he wasn't on that project01:14:05.566 --> 01:14:06.990 and doesn't have a ticket.01:14:06.990 --> 01:14:08.822 Till August I'm toward,01:14:08.822 --> 01:14:09.511 uh, Alex.01:14:09.511 --> 01:14:11.590 I know I'm going to pick on you again,01:14:11.590 --> 01:14:12.808 but we just had this earlier.01:14:12.810 --> 01:14:13.618 What should he do?01:14:23.370 --> 01:14:24.942 Alex is like I'm not paying01:14:24.942 --> 01:14:26.422 attention anymore. There's no01:14:26.422 --> 01:14:29.278 way he's picking on me again.01:14:29.280 --> 01:14:30.904 It's because my name is at the top.01:14:34.570 --> 01:14:38.605 Uhm? So he helps someone he01:14:38.605 --> 01:14:40.190 doesn't have a ticket for it.01:14:40.190 --> 01:14:43.850 What should he do? Oh, he just asked.01:14:43.850 --> 01:14:45.125 Either make a ticket for01:14:45.125 --> 01:14:46.628 the in the unplanned work,01:14:46.630 --> 01:14:49.038 or just ask a PM for ticket.01:14:49.040 --> 01:14:51.240 Yep, absolutely. Good job.01:14:57.400 --> 01:14:59.188 Bobby finishes out his day with01:14:59.188 --> 01:15:01.039 about 3 hours remaining in his day.01:15:01.040 --> 01:15:02.517 Bobby has five hours worth of tasks01:15:02.517 --> 01:15:04.256 left that he wanted to try to finish.01:15:04.260 --> 01:15:06.162 He modified his expectations based on01:15:06.162 --> 01:15:08.258 how the day went and chose the one01:15:08.258 --> 01:15:09.500 that would be pushed to tomorrow.01:15:09.500 --> 01:15:10.920 He completed two more tasks,01:15:10.920 --> 01:15:12.549 but in nearly all the time he had for01:15:12.549 --> 01:15:14.136 the day, which worked out perfectly.01:15:14.136 --> 01:15:16.570 He knew exactly what to work on tomorrow01:15:16.570 --> 01:15:18.698 morning and then hit the ground running.01:15:18.700 --> 01:15:19.908 He got some help,01:15:19.908 --> 01:15:20.814 help someone himself,01:15:20.820 --> 01:15:21.603 worked with Jeff,01:15:21.603 --> 01:15:22.908 and ultimately finished six hours01:15:22.908 --> 01:15:24.380 worth of tasks that he wanted01:15:24.380 --> 01:15:25.736 to finish in seven hours total.01:15:25.740 --> 01:15:28.080 He exceeded his billable and ticketable.01:15:28.080 --> 01:15:29.907 Goal of seven hours spending 8 total01:15:29.907 --> 01:15:31.696 between the user story he worked on01:15:31.696 --> 01:15:33.643 and the assist he provided to the newer01:15:33.643 --> 01:15:35.851 developer with a feeling of a job well done.01:15:35.851 --> 01:15:38.028 Bobby shut his computer down for the01:15:38.028 --> 01:15:40.028 night and got up from his chair.01:15:45.090 --> 01:15:46.910 Only to turn his computer back on,01:15:46.910 --> 01:15:48.050 Bobby had forgotten to finish.01:15:48.050 --> 01:15:50.115 This time logs and update us tickets.01:15:50.120 --> 01:15:51.710 Bobby updated his tickets first,01:15:51.710 --> 01:15:52.690 as that would be quick,01:15:52.690 --> 01:15:53.533 completed four tickets,01:15:53.533 --> 01:15:56.054 the three from the user story he worked on01:15:56.054 --> 01:15:58.062 that day and the ticket that was created01:15:58.112 --> 01:16:00.068 for him by assisting another developer.01:16:00.070 --> 01:16:01.546 Then Bobby turned to easy projects01:16:01.546 --> 01:16:02.800 to finish logging his time.01:16:02.800 --> 01:16:03.928 By the time it was done,01:16:03.930 --> 01:16:05.406 it looked like this.01:16:05.406 --> 01:16:07.251 General admin looking through Sprint01:16:07.251 --> 01:16:09.491 deciding what to work on .5 Hour01:16:09.491 --> 01:16:10.699 clarity task and descriptions.01:16:10.700 --> 01:16:12.842 7 hours worth of work on01:16:12.842 --> 01:16:14.666 the Clarity project meeting.01:16:14.666 --> 01:16:18.396 Stand up .25 hours Cephei.01:16:18.400 --> 01:16:21.050 That's my 3 year old.01:16:21.050 --> 01:16:21.740 Ah.01:16:31.200 --> 01:16:33.365 A CVA needs reallocation task01:16:33.365 --> 01:16:35.530 and description of the assist.01:16:35.530 --> 01:16:37.750 One hour general admin01:16:37.750 --> 01:16:39.970 logging time updating tickets.01:16:39.970 --> 01:16:43.618 .25 hour Bobby ended up working from roughly01:16:43.618 --> 01:16:46.640 8:50 AM to 6:20 PM Central 9.5 hours.01:16:46.640 --> 01:16:48.400 He had nine hours to log as he01:16:48.460 --> 01:16:50.042 did not log the time that he01:16:50.042 --> 01:16:51.942 went over and got water or any01:16:51.942 --> 01:16:53.402 other breaks throughout the day.01:16:53.410 --> 01:16:55.156 He exceeded an estimate which will01:16:55.156 --> 01:16:56.937 happen sometimes and he assisted another01:16:56.937 --> 01:16:59.185 developer which was not in a Sprint but01:16:59.240 --> 01:17:01.100 Bobby proactively communicated which.01:17:01.100 --> 01:17:03.236 Allowed the scrum master to reflex01:17:03.236 --> 01:17:05.204 quickly on that time Bobby exceeded01:17:05.204 --> 01:17:06.836 his billable goal and worked on01:17:06.836 --> 01:17:08.559 a user story alongside Geoff,01:17:08.560 --> 01:17:10.840 which was both fun and productive.01:17:10.840 --> 01:17:12.984 On top of all that Bobby knows exactly01:17:12.984 --> 01:17:14.997 what he'll start to work on tomorrow,01:17:15.000 --> 01:17:17.144 which will maximize efficiency01:17:17.144 --> 01:17:19.824 right out of the gate.01:17:19.830 --> 01:17:23.134 Now the point behind this story is,01:17:23.140 --> 01:17:25.628 well, first of all that probably I mean.01:17:25.630 --> 01:17:26.780 I mean, it's definitely sounds01:17:26.780 --> 01:17:28.339 familiar to a lot of my days,01:17:28.340 --> 01:17:30.140 and probably some of yours.01:17:30.140 --> 01:17:31.792 But the thing I want to point01:17:31.792 --> 01:17:33.490 out here is nowhere in here.01:17:33.490 --> 01:17:37.408 Did it say that that Bobby.01:17:37.410 --> 01:17:40.740 You know solved any crazy problems?01:17:40.740 --> 01:17:43.716 Right and the point I wanted to make01:17:43.716 --> 01:17:46.413 is this like we're not all going to be01:17:46.413 --> 01:17:49.698 as good as James Gray at writing code, right?01:17:49.698 --> 01:17:54.302 Uhm, but you don't have to be to be01:17:54.302 --> 01:17:56.798 a good developer here at clarity.01:17:56.800 --> 01:17:59.566 The things that we as a01:17:59.566 --> 01:18:02.030 team tend to struggle with.01:18:02.030 --> 01:18:03.596 And this goes for both the01:18:03.596 --> 01:18:05.080 devs and the PM teams.01:18:05.080 --> 01:18:07.740 The things that we tend to struggle01:18:07.740 --> 01:18:10.540 with are are easy things communicating.01:18:10.540 --> 01:18:14.090 You know, just generally speaking,01:18:14.090 --> 01:18:16.848 updating your time logs, logging your time,01:18:16.850 --> 01:18:19.699 like if you really think about it.01:18:19.700 --> 01:18:23.160 Like anybody's burn up that01:18:23.160 --> 01:18:24.400 doesn't match easy projects.01:18:24.400 --> 01:18:25.678 I mean, just think about how,01:18:25.680 --> 01:18:26.796 how easy that is.01:18:26.796 --> 01:18:29.477 Like all you have to do is log your01:18:29.477 --> 01:18:31.668 time and easy projects and then go01:18:31.737 --> 01:18:34.457 assign that to a ticket like go put01:18:34.457 --> 01:18:36.826 completed time to match that Tour de ticket.01:18:36.830 --> 01:18:40.870 These are all like just basic easy things01:18:40.870 --> 01:18:45.492 that if we as a team can lock all this in.01:18:45.500 --> 01:18:48.572 We will immediately see improvement across01:18:48.572 --> 01:18:52.548 the board will see more profit coming in,01:18:52.550 --> 01:18:54.902 and I'm sure that we all have things01:18:54.902 --> 01:18:56.894 that we wish PM's would be doing.01:18:56.894 --> 01:18:59.730 So if we can all start doing these things,01:18:59.730 --> 01:19:02.103 it will provide me with leverage to01:19:02.103 --> 01:19:04.005 start holding the PM's accountable01:19:04.005 --> 01:19:05.629 to doing their thing.01:19:05.630 --> 01:19:08.010 But that's really challenging right01:19:08.010 --> 01:19:11.342 now because all the PM has to do01:19:11.342 --> 01:19:13.770 is point to any one of us who.01:19:13.770 --> 01:19:17.703 You know who's burn up is 28 hours or01:19:17.703 --> 01:19:20.480 something or 31 hours and it's like Oh well,01:19:20.480 --> 01:19:22.460 yeah, they're not even working.01:19:22.460 --> 01:19:24.348 Or at least that's what it looks like.01:19:24.350 --> 01:19:27.310 So the the the whole point of this,01:19:27.310 --> 01:19:28.009 all of this,01:19:28.009 --> 01:19:29.912 which I'll drop this in so that you01:19:29.912 --> 01:19:32.235 guys have it in the chat is that01:19:32.235 --> 01:19:35.593 you don't have to be a C expert or01:19:35.593 --> 01:19:37.969 an angular expert or react expert01:19:38.059 --> 01:19:39.999 to be a good developer.01:19:40.000 --> 01:19:42.808 And focusing on the quote unquote,01:19:42.810 --> 01:19:45.036 easier things or things that are01:19:45.036 --> 01:19:46.520 directly within your control.01:19:46.520 --> 01:19:49.922 Uh are actually a lot easier than you would01:19:49.922 --> 01:19:52.372 think, and I think that we and I know01:19:52.372 --> 01:19:54.546 this happened to me when I first started.01:19:54.550 --> 01:19:57.349 Can get caught up in the fact that Seth01:19:57.349 --> 01:20:00.487 is is a solution with 70 projects in it.01:20:00.490 --> 01:20:03.910 I mean, if anybody who has ever worked with C01:20:03.994 --> 01:20:07.179 sharp should know like that's that's crazy.01:20:07.179 --> 01:20:10.197 Like that is absolutely insane and01:20:10.197 --> 01:20:13.595 that can be overwhelming, uh, to learn.01:20:13.595 --> 01:20:16.220 But at the end of the day,01:20:16.220 --> 01:20:18.108 like the things that are within our control,01:20:18.110 --> 01:20:20.182 or actually the things that the dev and01:20:20.182 --> 01:20:22.726 the PM teams are struggling with the most.01:20:22.730 --> 01:20:24.354 And when I say in your control,01:20:24.360 --> 01:20:26.052 I mean whether you've been here01:20:26.052 --> 01:20:27.830 for a day or 10 years.01:20:27.830 --> 01:20:28.446 Like those,01:20:28.446 --> 01:20:30.602 these things are firmly within our control.01:20:30.610 --> 01:20:33.725 It's just executing on the basics or.01:20:33.730 --> 01:20:35.320 You know the blocking and01:20:35.320 --> 01:20:36.910 tackling if you're into football.01:20:36.910 --> 01:20:38.578 I mean it's not about running.01:20:38.580 --> 01:20:40.206 You know all these crazy plays.01:20:40.210 --> 01:20:42.280 It's literally just about blocking01:20:42.280 --> 01:20:43.108 and tackling.01:20:43.110 --> 01:20:45.478 And if we lock that stuff in a,01:20:45.480 --> 01:20:47.424 I'm sure by now everybody's heard01:20:47.424 --> 01:20:49.214 CR say that we're essentially01:20:49.214 --> 01:20:51.344 flushing money down the toilet01:20:51.344 --> 01:20:53.750 every quarter because we have this.01:20:53.750 --> 01:20:54.682 We could be like,01:20:54.682 --> 01:20:55.148 you know,01:20:55.150 --> 01:20:57.070 we could be making this this01:20:57.070 --> 01:20:59.114 large amount of profit and we're01:20:59.114 --> 01:21:01.190 really never hitting it right now.01:21:01.190 --> 01:21:03.332 And the main reason that we're01:21:03.332 --> 01:21:04.403 not hitting it.01:21:04.410 --> 01:21:06.377 Is it because I'm both the dev01:21:06.377 --> 01:21:07.640 and the PM side?01:21:07.640 --> 01:21:09.415 We're just not doing everything01:21:09.415 --> 01:21:11.190 that we need to do,01:21:11.190 --> 01:21:15.384 so this this document is sort of a hey,01:21:15.390 --> 01:21:16.760 let's start doing this stuff.01:21:16.760 --> 01:21:18.944 Let's hold each other accountable to it.01:21:18.950 --> 01:21:19.448 You know,01:21:19.448 --> 01:21:21.440 if you're working with a new person or01:21:21.500 --> 01:21:23.528 an experienced person and they're like,01:21:23.530 --> 01:21:24.724 man, I gotta.01:21:24.724 --> 01:21:26.714 I gotta log my time,01:21:26.720 --> 01:21:29.289 but I'm not gonna do it say01:21:29.289 --> 01:21:31.290 hey go longer time man.01:21:31.290 --> 01:21:32.606 I don't care if it's James Gray.01:21:32.610 --> 01:21:34.005 If you're in a meeting with James Gray and01:21:34.005 --> 01:21:35.410 James says hey, I'm not logging my time.01:21:35.410 --> 01:21:36.451 Be like dude.01:21:36.451 --> 01:21:38.880 I want you to go longer time.01:21:38.880 --> 01:21:39.501 I want you.01:21:39.501 --> 01:21:40.950 I want you guys to feel empowered01:21:41.000 --> 01:21:42.472 to be able to say that to each01:21:42.472 --> 01:21:43.374 other because it's something01:21:43.374 --> 01:21:44.802 that we all need to do.01:21:44.810 --> 01:21:45.946 And we all need to get better at.01:21:49.780 --> 01:21:52.546 Alright, that's is it for me.