| Topic | Presenter(s) | Summary | Duration | Tags | Certification Quiz | Captions |
| -------------------------------------- | ------------ | ------------------------------------------------------------------------------ | -------- | -------------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Schedule for rolling out CEF v. 2020.1 | James Gray | Brief discussion of the new version and when portions of it will be completed. | 17:05 | #DevTraining, #CEF2020.1, #FridayTrainings, | N/A | 2020.1 Discussion and Schedule_AutoGeneratedCaption.txt |00:00:01.640 --> 00:00:06.335 - OK, so I showed previously and I thought I put it in the room and00:00:06.335 --> 00:00:10.404 - I put a mention about it and it's in the wiki inside teams00:00:10.404 --> 00:00:13.534 - about the same naming convention of the branches because after00:00:13.534 --> 00:00:16.664 - that conversation that we previously had a whole bunch of00:00:16.664 --> 00:00:19.794 - regimes sort of coming in that were not following it.00:00:21.530 --> 00:00:23.920 - CD and.00:00:26.130 --> 00:00:30.610 - I little bit there so I posted all that stuff in the in the00:00:30.610 --> 00:00:34.130 - channel. Everything. I posted this file but just kind of going00:00:34.130 --> 00:00:37.010 - a little bit more into the version numbering itself.00:00:37.010 --> 00:00:40.530 - Version numbers are date based effectively for when I was going00:00:40.530 --> 00:00:44.370 - to make the release and what we were planning to do previously00:00:44.370 --> 00:00:48.210 - was I would have a week of architecture work as being in00:00:48.210 --> 00:00:51.730 - creating of the quarter or I would go into Dubai. Major00:00:51.730 --> 00:00:55.570 - changes if I need to make model renames. Dropping old stuff like00:00:55.570 --> 00:00:57.982 - that. And then I would do 400:00:57.982 --> 00:01:01.533 - three week cycles. So I would have two weeks of features in00:01:01.533 --> 00:01:04.257 - one week of bug fixing. The idea being that I would focus00:01:04.257 --> 00:01:06.527 - really heavily on new things that clients would need, and00:01:06.527 --> 00:01:09.251 - then I would make sure that I would clear my backlog of00:01:09.251 --> 00:01:11.975 - bugs and this is like a loose definition of win. This stuff00:01:11.975 --> 00:01:14.472 - would happen just to make sure that I was trying to00:01:14.472 --> 00:01:16.969 - follow some kind of cycle on how often things should go.00:01:18.520 --> 00:01:21.508 - Well, you see here the features like these two weeks would go00:01:21.508 --> 00:01:23.998 - together and then this would be done release that would00:01:23.998 --> 00:01:26.488 - basically a hotfix released so the even numbers would actually00:01:26.488 --> 00:01:29.476 - of all then bugfix releases and the August would be trying to00:01:29.476 --> 00:01:30.472 - put in new features.00:01:32.150 --> 00:01:36.422 - That's how was I have not had time to physically draw the00:01:36.422 --> 00:01:39.626 - conversation that I had like this morning with Kevin.00:01:40.430 --> 00:01:41.360 - Into this yet?00:01:42.890 --> 00:01:46.340 - Try to make a new release itself functional now, expecting00:01:46.340 --> 00:01:49.100 - Microsoft tic tac message. Essentially, the only thing00:01:49.100 --> 00:01:53.240 - that's going to change here is going to be the second number,00:01:53.240 --> 00:01:57.380 - which is the quarter right? So instead of like 2021 on April00:01:57.380 --> 00:02:00.830 - will be 2020.2 dot, whichever it is that correct, yes?00:02:02.720 --> 00:02:05.366 - And effectively, what's going to happen is at the00:02:05.366 --> 00:02:06.542 - beginning of the quarter.00:02:08.280 --> 00:02:13.747 - The and now I'm going to apologize because this is wonky.00:02:13.747 --> 00:02:15.238 - First stuff office.00:02:17.630 --> 00:02:18.299 - I do that.00:02:21.020 --> 00:02:22.150 - So this will be April.00:02:23.790 --> 00:02:28.080 - Thank you, I think role and then this would be April May, June.00:02:29.360 --> 00:02:29.670 - Hum.00:02:31.560 --> 00:02:34.980 - Whatever I worked on during this quarter would be locked at the00:02:34.980 --> 00:02:38.685 - end of the quarter and then any new clients would be getting the00:02:38.685 --> 00:02:41.820 - code that was done here as they're working in here in00:02:41.820 --> 00:02:43.245 - branching off then doing their00:02:43.245 --> 00:02:46.784 - stuff. Anything that I'm doing during this quarter for the00:02:46.784 --> 00:02:49.820 - new version? None of them would touch until at least the00:02:49.820 --> 00:02:52.580 - end of the quarter starting into the following one, in00:02:52.580 --> 00:02:55.616 - which case at that point that client can decide whether they00:02:55.616 --> 00:02:56.996 - want to pay to upgrade.00:02:59.730 --> 00:03:02.960 - Important thing is that so essentially what James is saying00:03:02.960 --> 00:03:07.482 - is that if a client comes in and they're going to be using 2020.100:03:07.482 --> 00:03:11.358 - then we would not move them over 2022, which would essentially be00:03:11.358 --> 00:03:15.557 - an upgrade and less they pay for it. Just because we all know00:03:15.557 --> 00:03:19.433 - what comes with upgrades, you have to go through and there's a00:03:19.433 --> 00:03:22.017 - lot of different fixes and basically holding. Yeah00:03:22.017 --> 00:03:25.570 - sometimes, but most of the time you know holding onto their00:03:25.570 --> 00:03:28.800 - business logic while bringing forward those core bug fixes and00:03:28.800 --> 00:03:33.550 - upgrading this. Quite a bit of work, so we simply don't want00:03:33.550 --> 00:03:37.160 - to upgrade anybody for free, and you know potentially the00:03:37.160 --> 00:03:40.409 - problem problem that is ultimately if in 2 three00:03:40.409 --> 00:03:44.019 - clients around 2020.1 that has a bug. Fortunately all three00:03:44.019 --> 00:03:46.907 - clients get to pay for the bug fix.00:03:48.270 --> 00:03:51.952 - And we're not going to pull it in then just, you know, it might00:03:51.952 --> 00:03:55.108 - be something that you can go to cherry pick from something or00:03:55.108 --> 00:03:58.264 - talk in person and paste it on another project, but it's going00:03:58.264 --> 00:03:59.316 - to pay for it.00:04:00.920 --> 00:04:03.160 - Rather than just upgrading everything and getting things00:04:03.160 --> 00:04:06.800 - that they don't want and you know so I will, I will be00:04:06.800 --> 00:04:09.880 - working on stuff during this. I'm about to make a branch00:04:09.880 --> 00:04:12.680 - release that effectively gonna call it. I'm gonna call it00:04:12.680 --> 00:04:16.040 - 2020.0 so that I can say that it's everything that we were00:04:16.040 --> 00:04:18.840 - doing with like red and everything up to that point.00:04:18.840 --> 00:04:22.200 - And then I'm going to lock that and make that for this00:04:22.200 --> 00:04:25.560 - quarter. And then I'm going to start working on the actual .100:04:25.560 --> 00:04:28.920 - stuff for the rest of the quarter and we're going to be00:04:28.920 --> 00:04:31.720 - working with Kyle on getting a whole lot of documentation00:04:31.720 --> 00:04:32.000 - built.00:04:34.080 --> 00:04:34.530 - For supper.00:04:36.890 --> 00:04:40.250 - That has been handed off to Jesse Jesse. You're gonna00:04:40.250 --> 00:04:41.258 - be doing that.00:04:44.000 --> 00:04:45.098 - Because you Patrick.00:04:47.420 --> 00:04:48.580 - Um meeting00:04:50.460 --> 00:04:53.918 - so let's see is going to be working with me on making sure00:04:53.918 --> 00:04:57.110 - that we have the proper boot strip for upgrade. As part of00:04:57.110 --> 00:05:00.568 - that, so that by the end of the quarter we will have the00:05:00.568 --> 00:05:02.164 - bootstrap four will be the main00:05:02.164 --> 00:05:06.140 - version. Will be the main booster that we work for from00:05:06.140 --> 00:05:08.975 - here forward lower support who shot 300 legacy client.00:05:08.975 --> 00:05:12.440 - If a client be upgraded they need to be upgraded including00:05:12.440 --> 00:05:14.330 - upgrading their templates. Teacher for sweet.00:05:16.250 --> 00:05:19.660 - On that stuff and secondary Ann I, Chris is already started00:05:19.660 --> 00:05:23.070 - talking about this. I'm going to work with the release schedule00:05:23.070 --> 00:05:26.790 - so that our 'cause we're trying to get to like a software00:05:26.790 --> 00:05:29.890 - service type product client comes in. They buy just the00:05:29.890 --> 00:05:34.230 - license and they then we do some setup for but we don't do like00:05:34.230 --> 00:05:38.260 - full client major work like we do for the clients email so that00:05:38.260 --> 00:05:41.670 - they're just working up a stable platform for an entire quarter.00:05:41.670 --> 00:05:42.910 - Except for emergency hotfixes.00:05:44.280 --> 00:05:47.437 - And then we offered them to upgrade from there for new00:05:47.437 --> 00:05:51.168 - features and then the first version I want to I want to I00:05:51.168 --> 00:05:54.899 - want to like scale down what step is expected to be able to00:05:54.899 --> 00:05:58.056 - do like turning off for instance discounts and and like price00:05:58.056 --> 00:06:00.639 - rules, pricing provider. Like you'd only happened like the00:06:00.639 --> 00:06:03.796 - flat pricing but you only have flat inventory. See things like00:06:03.796 --> 00:06:06.379 - that that are more complicated than just require additional00:06:06.379 --> 00:06:09.249 - documentation in order to do that. No matter how functional00:06:09.249 --> 00:06:12.693 - they maybe I want to make it down towards Justice store that00:06:12.693 --> 00:06:16.640 - sells products. And that way we can say this is what we00:06:16.640 --> 00:06:19.577 - officially signed up for. We didn't sign up with sharp for00:06:19.577 --> 00:06:23.315 - more than we can chew, etc. And then each quarter as I make a00:06:23.315 --> 00:06:25.985 - new major release, that new release will turn those features00:06:25.985 --> 00:06:28.655 - on because we have the additional time to fully verify00:06:28.655 --> 00:06:31.592 - it in bed. It all the different versions of the different00:06:31.592 --> 00:06:34.529 - documentation. All that stuff or end users and Devs and admins00:06:34.529 --> 00:06:35.864 - and all of that stuff.00:06:36.550 --> 00:06:39.756 - I'm just getting back on that way by the end of the year for00:06:39.756 --> 00:06:42.733 - certain. All of our stuff will be turned on. All of the things00:06:42.733 --> 00:06:45.023 - would be capable will have settings that allow you to00:06:45.023 --> 00:06:46.855 - switch between different provider types that you use.00:06:46.855 --> 00:06:49.374 - Like if you want to switch between flat pricing and price00:06:49.374 --> 00:06:52.351 - rules you have to edit the app settings file. You be able to00:06:52.351 --> 00:06:55.557 - like. Use the settings in the admin to go do it kind of thing.00:06:55.557 --> 00:06:58.992 - That's the goal is to make it so that all of this can be done00:06:58.992 --> 00:07:01.969 - from the admin and then plug in your own like URL values without00:07:01.969 --> 00:07:04.717 - getting really more into that. More like we click a button and00:07:04.717 --> 00:07:07.694 - we would also deploy to Azure and that can spin up an entire00:07:07.694 --> 00:07:10.923 - site for somebody. The client to upload their own provider00:07:10.923 --> 00:07:14.102 - DLL and use it. Yeah, I've living their own custom client00:07:14.102 --> 00:07:16.992 - work. Getting to the point where Golden touched on this00:07:16.992 --> 00:07:20.460 - stuff a lot before it is part of the architecture is where00:07:20.460 --> 00:07:24.217 - there's a new get packages of what the core DLL and then the00:07:24.217 --> 00:07:27.107 - client can go write their own stuff by referencing the00:07:27.107 --> 00:07:30.286 - originals and doing overrides, and change is going to have set00:07:30.286 --> 00:07:33.465 - capable of doing things like that, so exactly the same way00:07:33.465 --> 00:07:37.222 - I'm going to find out what's going to work best in with both00:07:37.222 --> 00:07:38.089 - the most maintainable.00:07:39.630 --> 00:07:42.226 - And things like that. So I've already done proof of concepts00:07:42.226 --> 00:07:45.294 - in a lot of this stuff on my local I've got things that00:07:45.294 --> 00:07:47.654 - theoretically work and I'm just trying to get through the00:07:47.654 --> 00:07:50.722 - rigorous to make sure that I can prove to everyone else that it00:07:50.722 --> 00:07:52.374 - works and not just my saying so.00:07:55.880 --> 00:07:58.796 - So we have all that stuff in there, and so the version00:07:58.796 --> 00:08:01.712 - numbers. This is also going to be a loose date things. Well,00:08:01.712 --> 00:08:05.357 - it's not going to be that on April 1st. I said no. We have to00:08:05.357 --> 00:08:08.516 - make lunch right now no matter what state is then it's going to00:08:08.516 --> 00:08:11.432 - wait till we actually have the like. The thing that is approved00:08:11.432 --> 00:08:14.105 - and ready to go. And especially with these first couple of00:08:14.105 --> 00:08:17.021 - quarters, it's probably going to slide. It may even flight up to00:08:17.021 --> 00:08:20.909 - like a month, which is not a big deal for me. But as long as we00:08:20.909 --> 00:08:24.068 - eventually we roll it into that level of we're going to turn it00:08:24.068 --> 00:08:27.290 - into it. Real regular thing that's going to be at each00:08:27.290 --> 00:08:31.350 - quarter and then part of the, you know, the sort of why is the00:08:31.350 --> 00:08:33.670 - version numbers are based updates internally and things00:08:33.670 --> 00:08:37.730 - like that so that I can say this is the progression. This is what00:08:37.730 --> 00:08:42.080 - you were on a branch off of at the time. That it, a Kurd, and00:08:42.080 --> 00:08:45.850 - what else was working on it inside at that time and go OK,00:08:45.850 --> 00:08:49.040 - well for dark six. Didn't have elastic search. I know that.00:08:49.040 --> 00:08:52.520 - Well, 2019 dot two didn't have the whole new JavaScript can fix00:08:52.520 --> 00:08:54.550 - stuff that we did for IA. Where00:08:54.550 --> 00:08:58.020 - we? We wrote how all the settings get absorbed into the00:08:58.020 --> 00:09:01.008 - system instead of how to where we get a lot of defaults00:09:01.008 --> 00:09:03.996 - instead of having to have all the settings in all the files00:09:03.996 --> 00:09:07.233 - coming all over the place. In doing a lot of extra work, so00:09:07.233 --> 00:09:10.221 - will be able to learn and identify a lot of those things00:09:10.221 --> 00:09:13.209 - and get them out. There will also be able to make better00:09:13.209 --> 00:09:14.952 - patching, release notes, feature releases that say00:09:14.952 --> 00:09:17.442 - exactly what's up. It's going to do with Screenshots and00:09:17.442 --> 00:09:19.683 - expectations and positive and negative paths and all that00:09:19.683 --> 00:09:19.932 - stuff.00:09:21.540 --> 00:09:26.595 - Are you going to have to say you release? Are you going to have a00:09:26.595 --> 00:09:30.639 - set of features that you are planning to put in for that00:09:30.639 --> 00:09:34.683 - quarter? Or you just kind of going is like how is that00:09:34.683 --> 00:09:38.727 - working for the first part? It's primarily what fire needs to go00:09:38.727 --> 00:09:43.108 - out. Sure, the second step or so so what's on fire followed by.00:09:44.290 --> 00:09:47.826 - What's gonna be needed as soon as I think you feature by a00:09:47.826 --> 00:09:51.846 - client? And then third is going to be like core features that we00:09:51.846 --> 00:09:54.739 - actually have actually need in order to support the software as00:09:54.739 --> 00:09:57.895 - a service, like I need to build the licensing engines so that00:09:57.895 --> 00:09:59.473 - when we do enable discounts for00:09:59.473 --> 00:10:02.850 - the soft. Surface clients they have to have it in a special00:10:02.850 --> 00:10:05.864 - license that says that they have rights to access the discount00:10:05.864 --> 00:10:06.960 - section of the code.00:10:08.670 --> 00:10:11.992 - For an one of the things that worked well basically have00:10:11.992 --> 00:10:17.120 - Sprint. And so pod, seeing things then we can have Sprint00:10:17.120 --> 00:10:20.828 - planning and actually go through the requirements documents and00:10:20.828 --> 00:10:24.536 - prioritize. Just curious with Mike sense, clarity of the00:10:24.536 --> 00:10:29.068 - client. What's the, you know, the users user stories set by.00:10:30.570 --> 00:10:33.954 - This would be guaranteed, right? Well, I mean, it's kind of going00:10:33.954 --> 00:10:35.364 - to come from a collaboration.00:10:36.940 --> 00:10:39.289 - Internal stakeholders of the platform which looks like Ron00:10:39.289 --> 00:10:42.421 - and Chris etc. Sure they would be coming in and saying these00:10:42.421 --> 00:10:45.292 - are the features we need to discuss. These are what I'm00:10:45.292 --> 00:10:48.685 - going to ask about why in the sales calls or this is what00:10:48.685 --> 00:10:51.556 - we're seeing the most like. Three of the four clients were00:10:51.556 --> 00:10:54.427 - actively working on all trying to do something very similar, or00:10:54.427 --> 00:10:57.298 - they got something that they actually have done in the next00:10:57.298 --> 00:11:00.430 - six months. So let's get that at least the baseline of that00:11:00.430 --> 00:11:03.562 - feature in place. If it, even if it's not necessarily the exact00:11:03.562 --> 00:11:06.694 - perfect version of that client, might use, but make it so that00:11:06.694 --> 00:11:09.772 - it. You know that that that what they're trying to do is00:11:09.772 --> 00:11:12.434 - giving that mind so that you're not recording yourself into a00:11:12.434 --> 00:11:15.580 - corner and have to go back and redo it. Change it too harshly.00:11:17.210 --> 00:11:21.066 - That the directive right now it's just documentation.00:11:24.120 --> 00:11:26.406 - Has all the new team members now like trying?00:11:28.560 --> 00:11:32.292 - Understood, yeah, it was just that I was just curious if like00:11:32.292 --> 00:11:36.335 - you know it's it's Week 7 rolls around or Sprint 7 rolls around,00:11:36.335 --> 00:11:40.689 - it's like, Oh well, we'd like to have this, this and this in and00:11:40.689 --> 00:11:44.421 - you know, are those things set at the very beginning or the00:11:44.421 --> 00:11:47.531 - kind of? Obviously it's always going to be dynamic, but.00:11:49.120 --> 00:11:53.838 - Just like our goal is to be a, you know, planned two or three00:11:53.838 --> 00:11:57.882 - sprints out for client work. Will it be planned 1/4 out for00:11:57.882 --> 00:12:01.926 - that? My hope is to have a a continuous rolling six months00:12:01.926 --> 00:12:05.633 - worth of work plans. That way though, all the estimates and00:12:05.633 --> 00:12:09.340 - all that data is inside the ticket. And if somebody needs00:12:09.340 --> 00:12:13.384 - to move around I will know how much it is physically move00:12:13.384 --> 00:12:14.058 - around accomplished.00:12:16.280 --> 00:12:19.850 - So the idea about all this stuff is to try and reduce the churn00:12:19.850 --> 00:12:22.400 - that's happening in the client project as the client projects00:12:22.400 --> 00:12:25.715 - being worked on and focus it down to at the time that they00:12:25.715 --> 00:12:28.520 - are performed the upgrade. Sure, that will mean that they will00:12:28.520 --> 00:12:31.325 - not have access to features and things for almost an entire00:12:31.325 --> 00:12:34.130 - quarter depending on at that point it was supposed to start,00:12:34.130 --> 00:12:37.190 - and if something got missed in that quarter, it could be that00:12:37.190 --> 00:12:39.740 - the development work will have to happen specifically in that00:12:39.740 --> 00:12:42.800 - client right there. Then pour it back to core after the fact.00:12:44.440 --> 00:12:49.942 - The way I would say it is the the client projects will not be00:12:49.942 --> 00:12:53.479 - upgraded like this with internal directed client projects will00:12:53.479 --> 00:12:57.409 - not be upgraded unless the client received the request to00:12:57.409 --> 00:13:01.732 - do that and they approve the time required to complete that00:13:01.732 --> 00:13:02.911 - request, just like.00:13:04.480 --> 00:13:08.185 - Not crazy and all the time. What do we do about so say00:13:08.185 --> 00:13:11.605 - client comes in Q2? They ask for a feature we've known about00:13:11.605 --> 00:13:15.025 - it and then so another client comes in in Q3. They're asking00:13:15.025 --> 00:13:18.730 - for the same feature, but it's not quite. Is it poor or save?00:13:18.730 --> 00:13:22.150 - Save quiet 3 apps or something and then client things like oh00:13:22.150 --> 00:13:25.855 - we want to change request for this? Is it going to be rebuilt00:13:25.855 --> 00:13:29.845 - in there or is that are they going to be like? Well we can00:13:29.845 --> 00:13:32.980 - do it but we have but you have to be upgraded.00:13:35.350 --> 00:13:38.820 - OK, so will present in the option of. Basically, quote00:13:38.820 --> 00:13:42.637 - Unquote. Possibly some would say being done in, like having the00:13:42.637 --> 00:13:46.801 - same work going on to places, but there's an area with might00:13:46.801 --> 00:13:51.312 - cost that client last month, and then we can. Also, we can factor00:13:51.312 --> 00:13:55.476 - that into and we might say, well, shoot both. The client is00:13:55.476 --> 00:13:58.946 - doing the same thing. We can combine the features together00:13:58.946 --> 00:14:03.457 - and just upgrade them both, and that's part of the pitch to that00:14:03.457 --> 00:14:05.980 - client saying. We have another one who wants to do something00:14:05.980 --> 00:14:08.140 - similar. Do you want to split the cost with them? 'cause that00:14:08.140 --> 00:14:10.300 - will save you money, but that would mean you'll have to wait.00:14:11.870 --> 00:14:14.561 - But if they don't want to wait, then that means that the brunt00:14:14.561 --> 00:14:17.252 - of the fund's going to have to come from them in order to00:14:17.252 --> 00:14:19.736 - cover getting it done sooner and on the time frame that they00:14:19.736 --> 00:14:20.978 - want. I know this is a.00:14:22.790 --> 00:14:24.822 - Your other modules, elders, weather like, yeah, that's00:14:24.822 --> 00:14:27.870 - not gonna be for awhile that we can do that. But if00:14:27.870 --> 00:14:31.172 - you want we can give you a quote to do it for you.00:14:32.670 --> 00:14:33.940 - Put in our road map.00:14:35.980 --> 00:14:39.844 - And I I kind of mentioned this before one of the goals that I00:14:39.844 --> 00:14:42.880 - would like to have is effectively like a user for us00:14:42.880 --> 00:14:46.192 - Type Forum where our clients are people who come in and they00:14:46.192 --> 00:14:48.676 - start buying this autobox platform and they want new00:14:48.676 --> 00:14:52.540 - features. Part of what I would like to have in that is a plug00:14:52.540 --> 00:14:55.576 - system where they will pledge a grand 100 bucks $50 whatever00:14:55.576 --> 00:14:58.612 - towards this particular features and as long as it reaches the00:14:58.612 --> 00:15:01.924 - goal for what that feature would require to get done by however00:15:01.924 --> 00:15:04.684 - many different clients who want to help pay for it.00:15:06.120 --> 00:15:09.396 - We will do the work and they will release as part of that is00:15:09.396 --> 00:15:12.204 - that next quarter, I mean and you know, maybe we. I mean,00:15:12.204 --> 00:15:15.480 - there's a lot of Justice around that, you know, do we give him a00:15:15.480 --> 00:15:18.054 - different way for being a pledge before something goes in? Like00:15:18.054 --> 00:15:20.862 - different amount per hour, kind of stuff and things like that to00:15:20.862 --> 00:15:23.904 - consider too? Yeah, I was just. I know there's more of a sales00:15:23.904 --> 00:15:27.462 - thing, but like. Why, given the option of combining this new00:15:27.462 --> 00:15:28.757 - feature for both of 'em?00:15:30.140 --> 00:15:30.510 - Facebook.00:15:32.070 --> 00:15:34.260 - But that's another. That's a sales thing that could be.00:15:35.760 --> 00:15:36.210 - But00:15:37.940 --> 00:15:38.789 - when it's worth.00:15:40.540 --> 00:15:41.448 - Would you guys agreed?00:15:45.810 --> 00:15:49.938 - Oh yeah, Oh yeah, definitely Oh yeah, yeah,00:15:49.938 --> 00:15:53.034 - yeah, definitely because I think especially00:15:53.034 --> 00:15:56.130 - documentation of current features of current00:15:56.130 --> 00:15:57.678 - workflows of current.00:15:58.990 --> 00:16:03.571 - Tables and entities you know, even just just a00:16:03.571 --> 00:16:06.116 - basic of how the how.00:16:07.430 --> 00:16:11.083 - I think the game so this is something that maybe we can go00:16:11.083 --> 00:16:13.893 - in future trainings for like set specifically of like how00:16:13.893 --> 00:16:16.141 - the run associate workflows works, how the run.00:16:17.740 --> 00:16:20.611 - Just instead of just hitting immediately assigning the right,00:16:20.611 --> 00:16:24.439 - I think that those are those are everywhere in all of the00:16:24.439 --> 00:16:28.267 - entities on the back end, and I think a good understanding of00:16:28.267 --> 00:16:31.776 - how and why it those were on rather than just adding00:16:31.776 --> 00:16:35.285 - everything that we know exists in there would be crucial to00:16:35.285 --> 00:16:40.070 - knowing that OK, I don't have to add an extra hook in here to go00:16:40.070 --> 00:16:43.898 - add this in because it's already being taken care of over here00:16:43.898 --> 00:16:47.407 - automatically, so I think if we can get that those key00:16:47.407 --> 00:16:50.690 - underlying. Workflows documented an trained on.00:16:51.810 --> 00:16:54.040 - That would be a good base base place to start.00:16:55.360 --> 00:16:58.890 - And I would say those as example because I've run00:16:58.890 --> 00:17:01.714 - through those workflows several times and would love00:17:01.714 --> 00:17:03.479 - to understand those little better.