| Topic | Presenter | Summary | Duration | Tags | Certification Quiz | Captions |
| ------------------------------------------ | ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ---- | ----------------------------------------------------------------------------- | -------- |
| How to get answers to questions at Clarity | Chris Reddick | This videos discusses how developers can find answers to questions through sources like Nuclino, StackOverflow and Google. In it, Chris also talks about the importance of memorializing questions and answers for posterity. | 50:12 | | Asking Questions | |00:00:02.190 --> 00:00:06.610 - Try it, try to get started here OK. Hey guys, um, let's see 00:00:06.610 --> 00:00:10.690 - couple of things on the agenda for today. And feel free Erica 00:00:10.690 --> 00:00:15.450 - Krista, correct me on this. Is you guys see fit or add to etc. 00:00:15.450 --> 00:00:19.870 - First of all, we're going to be going over just how to ask. 00:00:19.870 --> 00:00:23.950 - Sorry how to ask a question which seems like such a silly 00:00:23.950 --> 00:00:25.310 - thing to talk about. 00:00:25.860 --> 00:00:30.384 - But being you know, being remote and even even on site, um, it's 00:00:30.384 --> 00:00:34.560 - really important to be able to ask a question and get support. 00:00:34.560 --> 00:00:38.040 - We, you know, we overlap with each other on different 00:00:38.040 --> 00:00:40.476 - specialty areas. Different knowledge that individuals are 00:00:40.476 --> 00:00:45.348 - the best at or have the most exposure to at least. And so we 00:00:45.348 --> 00:00:49.176 - need to know how to communicate optimally with each other and 00:00:49.176 --> 00:00:53.004 - kind of what the norms are so that we're not feeling 00:00:53.004 --> 00:00:55.788 - uncomfortable about raising issues that were running into 00:00:55.788 --> 00:00:57.876 - and how to get past those. 00:00:57.890 --> 00:01:02.810 - So I think it's a really key topic and I and I hope you guys 00:01:02.810 --> 00:01:07.402 - are really focus on that when we go over it should be good um, 00:01:07.402 --> 00:01:11.994 - and then also we're going to be going over a brief review of the 00:01:11.994 --> 00:01:15.602 - theasp.net. I'm sorry that yeah, the asp.net core three, 3.0 and 00:01:15.602 --> 00:01:20.194 - angular nine book just kind of a quick review of that and some of 00:01:20.194 --> 00:01:24.130 - the high level pieces there for Chapter 2. And then we're going 00:01:24.130 --> 00:01:28.394 - to switch gears and we're going to go into some of the connect 00:01:28.394 --> 00:01:32.907 - side of things. And feel free again Eric to let me know if the 00:01:32.907 --> 00:01:36.711 - the plan is otherwise on that, but that's that's kind of the 00:01:36.711 --> 00:01:41.149 - overall plan. And let me see I don't see Eric on here yet, so 00:01:41.149 --> 00:01:45.270 - it OK, so that's the agenda. So with that, unless you guys have 00:01:45.270 --> 00:01:49.391 - anything else to to add to that will go ahead and get started 00:01:49.391 --> 00:01:52.878 - here. OK, let's do this. OK, so really, really, really starting 00:01:52.878 --> 00:01:56.999 - going over questions. OK, so let me just kind of opposed to you 00:01:56.999 --> 00:01:59.218 - what I think happens a lot of 00:01:59.218 --> 00:02:02.931 - times. Really, on any software development team, uhm, and just 00:02:02.931 --> 00:02:04.407 - any team in general. 00:02:05.090 --> 00:02:10.211 - Um? You have some people who are really good at certain things 00:02:10.211 --> 00:02:14.072 - and have a lot of tribal. Anne Anne, just general industry 00:02:14.072 --> 00:02:17.933 - knowledge and you have others who don't and are learning those 00:02:17.933 --> 00:02:21.443 - things and these things kind of overlap in certain areas. 00:02:21.750 --> 00:02:25.481 - I have one team member that's really good on on SQL, and one 00:02:25.481 --> 00:02:31.482 - who, uhm? You know who is really good on HTML, CSS or angular or 00:02:31.482 --> 00:02:34.690 - you know C, Sharp etc. Server infrastructure, security 00:02:34.690 --> 00:02:39.502 - performance, organic SCODNN, the list goes on. There are a lot of 00:02:39.502 --> 00:02:43.316 - specialty areas. Generally speaking, most of the team, 00:02:43.316 --> 00:02:47.176 - especially once they've kind of developed enough of a capability 00:02:47.176 --> 00:02:51.422 - that there what I would call, you know, quote, unquote, worthy 00:02:51.422 --> 00:02:55.668 - of being perceived as the expert on a particular topic or 00:02:55.668 --> 00:02:59.142 - typically perceived as the expert on a particular topic. 00:02:59.680 --> 00:03:01.000 - Are there going to? 00:03:01.840 --> 00:03:05.944 - Essentially, get busy with work in most cases. 00:03:06.680 --> 00:03:10.992 - Um, in an essentially accumulate so much work that they will 00:03:10.992 --> 00:03:16.480 - always be at or over capacity as a norm. I'm not saying that's a 00:03:16.480 --> 00:03:20.008 - requirement, just saying that's probably what will tend to 00:03:20.008 --> 00:03:21.184 - happen. OK, so. 00:03:21.870 --> 00:03:26.215 - Ultimately, the bottom line is you kind of have this like 00:03:26.215 --> 00:03:28.980 - mechanical challenge within an organization with getting 00:03:28.980 --> 00:03:32.535 - information to folks who don't have the information, because 00:03:32.535 --> 00:03:37.275 - the folks who do have it are consistently going to be busy. 00:03:37.275 --> 00:03:41.225 - It's just part of the structure of you know how. 00:03:41.830 --> 00:03:45.262 - Them being good at things is going to tend to keep them busy. 00:03:46.020 --> 00:03:51.165 - So one of the things that I want to say about this is number one. 00:03:51.165 --> 00:03:54.595 - We've really staked our claim with how we're running this 00:03:54.595 --> 00:03:58.368 - business on the idea of building opportunities by and large. Not 00:03:58.368 --> 00:04:02.484 - not 100% across the board, but by and large around team members 00:04:02.484 --> 00:04:06.943 - who are going to come in and learn and grow and build akarere 00:04:06.943 --> 00:04:11.059 - an you know there are a lot of advantages to that approach. 00:04:11.790 --> 00:04:15.330 - It's certainly not the only approach that we're taking. UM, 00:04:15.330 --> 00:04:19.224 - in general, though, that's really a major area of focus for 00:04:19.224 --> 00:04:23.472 - the business, and there are a lot of advantages to it. Number 00:04:23.472 --> 00:04:29.180 - one. I mean kind of the the bottom line is we can build a. 00:04:29.180 --> 00:04:33.500 - We can build team members careers up and give them a lot 00:04:33.500 --> 00:04:36.740 - of upside opportunity within a relatively small company. That 00:04:36.740 --> 00:04:41.060 - makes it very advantageous to each of them as they continue to 00:04:41.060 --> 00:04:44.660 - build and grow their careers, and so there's a commitment 00:04:44.660 --> 00:04:47.540 - there though, and there's kind of an implied. 00:04:47.540 --> 00:04:51.896 - You know, kind of 2 sided deal there where the business itself 00:04:51.896 --> 00:04:56.615 - in the team itself has to help that person you know, grow and 00:04:56.615 --> 00:05:00.971 - build their careers. And it's a two way St. You know everyone. 00:05:00.971 --> 00:05:05.327 - Everyone has to put in the effort in order to make that 00:05:05.327 --> 00:05:09.320 - happen as well. On an individual level. But generally speaking we 00:05:09.320 --> 00:05:13.313 - need the team to be able to optimally support and build 00:05:13.313 --> 00:05:17.669 - those new folks up as best possible. So what I wanted to. 00:05:17.740 --> 00:05:22.216 - Talk about is how do you interact with some of the more 00:05:22.216 --> 00:05:25.946 - senior folks and some of the folks that have specialized 00:05:25.946 --> 00:05:28.930 - knowledge, regardless of seniority? And what's the best 00:05:28.930 --> 00:05:33.406 - way to get feedback and get issues resolved? And so the I 00:05:33.406 --> 00:05:38.255 - guess the biggest part of that is just to tell you that it's 00:05:38.255 --> 00:05:42.731 - number one. It's a very valid thing that you might feel you 00:05:42.731 --> 00:05:46.461 - know concerned about. Asking someone who's very busy for help 00:05:46.461 --> 00:05:50.937 - or support, and you probably may get some responses that kind of. 00:05:51.010 --> 00:05:54.380 - Uhm, you know where they are expressing their stress that 00:05:54.380 --> 00:05:57.750 - they're feeling because they are relatively busy, and so it's 00:05:57.750 --> 00:06:00.446 - it's really just not mechanically a good situation. 00:06:00.446 --> 00:06:04.153 - If you're having to go ask individual folks for support or 00:06:04.153 --> 00:06:08.534 - help. And So what I would suggest is that you do a couple 00:06:08.534 --> 00:06:12.915 - of key things. So let me so the first thing that I always 00:06:12.915 --> 00:06:17.296 - recommend that you do here is try to get an answer to your 00:06:17.296 --> 00:06:21.003 - question or the topic that you're working on. An really try 00:06:21.003 --> 00:06:24.500 - to get. Get yourself exposed to what information we do have 00:06:24.500 --> 00:06:28.530 - available right out of the gate, so that probably the best way to 00:06:28.530 --> 00:06:32.250 - do that for clarity, specific knowledge is to go in and look 00:06:32.250 --> 00:06:33.800 - at our new clean. Oh. 00:06:34.690 --> 00:06:38.733 - If you don't have access to earn a clean, oh please make sure 00:06:38.733 --> 00:06:42.465 - that you get access. You can ping your manager, you can ping 00:06:42.465 --> 00:06:46.508 - myself and you can ping any of the OPS team members and we 00:06:46.508 --> 00:06:48.685 - should be able to get you access 00:06:48.685 --> 00:06:52.510 - to Nicolino. And so anyway, one of the best things about new 00:06:52.510 --> 00:06:56.449 - clean now is you can come in here and type anything and you 00:06:56.449 --> 00:06:59.782 - do. You'll see kind of different experience with new clean house. 00:06:59.782 --> 00:07:01.297 - So if I type in. 00:07:01.300 --> 00:07:06.158 - Let's see 500, so I just want to point out. I guess the first 00:07:06.158 --> 00:07:10.669 - thing if you type in 500 and you don't hit enter you get 00:07:10.669 --> 00:07:12.404 - different results. Then if you 00:07:12.404 --> 00:07:15.884 - hit enter. Basically, when you're just typing it in my 00:07:15.884 --> 00:07:19.712 - understanding is it's looking at the titles when you hit enter, 00:07:19.712 --> 00:07:23.888 - it searches the contents. So if you've tried to look for things 00:07:23.888 --> 00:07:28.760 - you like, yeah, I didn't see it in there. Hit enter if you don't 00:07:28.760 --> 00:07:33.284 - see it right away, and that way you can dig into the contents 00:07:33.284 --> 00:07:34.676 - themselves and then basically. 00:07:35.420 --> 00:07:38.900 - Whenever you're looking inside of the content content's one of 00:07:38.900 --> 00:07:43.076 - the things that I'll point out is if you're working with the 00:07:43.076 --> 00:07:46.904 - team member on a project and you're showing them that hey, 00:07:46.904 --> 00:07:49.340 - I've gone and looked at this new 00:07:49.340 --> 00:07:53.355 - clean. Oh. And then the next thing that I would recommend 00:07:53.355 --> 00:07:56.640 - would be our stackoverflow. Uhm, so again, let's let's 00:07:56.640 --> 00:08:00.290 - say hypothetically I've got a 500 error indianen, so I 00:08:00.290 --> 00:08:03.940 - don't see any anything talking about a 500 error in 00:08:03.940 --> 00:08:06.130 - here. Maybe I can look for. 00:08:07.510 --> 00:08:11.371 - OK, this might actually be helpful. Oh yeah, OK, here's my 00:08:11.371 --> 00:08:15.934 - issue. Uhm, well, that's not quite it. OK, let me go. Look at 00:08:15.934 --> 00:08:19.677 - Stackoverflow. Let me go into the clarity team so if you don't 00:08:19.677 --> 00:08:23.361 - have access to the clarity team, make sure that you let again 00:08:23.361 --> 00:08:27.352 - your manager myself for the OPS team now and will get you in 00:08:27.352 --> 00:08:32.516 - here. Uhm, but we basically want you to come in and do searching 00:08:32.516 --> 00:08:36.454 - within you clean. Oh, and the stack overflow inside of the 00:08:36.454 --> 00:08:40.520 - clarity team. Uhm, you know if you think it has a reasonable 00:08:40.520 --> 00:08:43.808 - shot of being answered in here, uhm, I would recommend going in 00:08:43.808 --> 00:08:47.644 - and taking a look at these two quickly. I think you can get it 00:08:47.644 --> 00:08:51.480 - down to where your searches take you like 10 seconds or so to do 00:08:51.480 --> 00:08:55.042 - a search in both really fast. I mean you can boom Papa surgeon 00:08:55.042 --> 00:08:56.412 - hit enter, boom, Papa searching 00:08:56.412 --> 00:09:00.960 - hit enter. And so one of the things that I would recommend 00:09:00.960 --> 00:09:06.208 - that you do is just go ahead and pin these. If you pin a tab in 00:09:06.208 --> 00:09:09.488 - Chrome in it for example, it will reload whenever your 00:09:09.488 --> 00:09:12.440 - machine restarts, or whatever, bookmark it. Get yourself a 00:09:12.440 --> 00:09:15.392 - little clarity developer dashboard where you have all of 00:09:15.392 --> 00:09:18.344 - your tabs available that you're going to commonly use. 00:09:19.020 --> 00:09:22.392 - And so really, the first thing is try to get the questions 00:09:22.392 --> 00:09:25.483 - answered inside of our clarity resources. OK, and so that's the 00:09:25.483 --> 00:09:29.136 - first thing, and then the next thing of course, is to go look 00:09:29.136 --> 00:09:31.103 - at the googs. So we're going to 00:09:31.103 --> 00:09:36.211 - say DNN 500. And so we'll just do a search for that and just 00:09:36.211 --> 00:09:39.943 - see if we can. You know, in this hypothetical scenario, find the 00:09:39.943 --> 00:09:43.304 - solution. Of course, stack overflow is really, really 00:09:43.304 --> 00:09:45.838 - awesome, just in general. Outside of clarity, 00:09:45.838 --> 00:09:49.096 - stackoverflow as well, so I highly recommend looking at 00:09:49.096 --> 00:09:54.526 - this, and the idea would be that what we want you to do is spend 00:09:54.526 --> 00:09:58.508 - a couple of minutes taking a specific error or a specific 00:09:58.508 --> 00:10:02.490 - thing that you're working on and trying to figure out the 00:10:02.490 --> 00:10:06.110 - keywords to search within our internal and then within Google 00:10:06.110 --> 00:10:09.730 - resources and there from Google like stack overflow for example. 00:10:10.290 --> 00:10:13.306 - One of the things that I've seen about some of the best problem 00:10:13.306 --> 00:10:16.554 - solvers who I've worked with and a lot of you can attest to this 00:10:16.554 --> 00:10:17.714 - with certainty. Members on our 00:10:17.714 --> 00:10:22.268 - team right now. As they don't have a lot of quote Unquote 00:10:22.268 --> 00:10:26.325 - Pedigree. To be able to solve really challenging problems, but 00:10:26.325 --> 00:10:30.940 - there are a couple of folks on our team that literally based on 00:10:30.940 --> 00:10:34.845 - their background and pedigree, should not be able to solve any 00:10:34.845 --> 00:10:39.460 - of the problems that they solve. But one of the things that they 00:10:39.460 --> 00:10:43.010 - mechanically do is they think about the right keyword phrases 00:10:43.010 --> 00:10:46.560 - to search for inside of Google and Stackoverflow and other 00:10:46.560 --> 00:10:51.175 - resources in the other thing I want to say is they typically go 00:10:51.175 --> 00:10:52.595 - to specific error messages. 00:10:53.160 --> 00:10:57.600 - Event IDs very specific things that can be searched on and can 00:10:57.600 --> 00:11:02.040 - give you very specific responses so that you can see how to 00:11:02.040 --> 00:11:06.110 - problem solve something. A lot of times too. They're kind of 00:11:06.110 --> 00:11:10.550 - thinking about it as a set of variables and they're trying to 00:11:10.550 --> 00:11:14.620 - eliminate those variables, so a lot of times with problems it's 00:11:14.620 --> 00:11:19.430 - very helpful too. If you say have a problem with the DNN 500 00:11:19.430 --> 00:11:23.500 - error, well I can tell you from my personal experience there 00:11:23.500 --> 00:11:27.200 - could be about 100 different things that would cause that, 00:11:27.200 --> 00:11:31.255 - OK? But the most common are these. You know these types of 00:11:31.255 --> 00:11:34.940 - things over here, and this is just from my experience. It's 00:11:34.940 --> 00:11:38.960 - going to be a this module or this feature or this permission 00:11:38.960 --> 00:11:39.965 - in order to. 00:11:40.490 --> 00:11:44.606 - Well, as you start to develop your knowledge of what types of 00:11:44.606 --> 00:11:48.036 - things could cause problems, what I would recommend that you 00:11:48.036 --> 00:11:51.123 - do is essentially try to eliminate wide swaths of 00:11:51.123 --> 00:11:52.838 - variables from your testing in 00:11:52.838 --> 00:11:57.871 - your debugging. One of the things that I see I see some of 00:11:57.871 --> 00:12:01.622 - the back end team members doing with new providers, is there 00:12:01.622 --> 00:12:05.373 - literally building out a simple application in order to test a 00:12:05.373 --> 00:12:09.124 - new plugin or provider that we're building. So for one of 00:12:09.124 --> 00:12:12.534 - the new payment providers we literally built just a separate 00:12:12.534 --> 00:12:15.944 - application to test that direct integration to the provider 1st, 00:12:15.944 --> 00:12:20.036 - and then we're bringing it into the E Commerce platform and that 00:12:20.036 --> 00:12:23.446 - eliminates a lot of variables within the E Commerce platform 00:12:23.446 --> 00:12:24.810 - before we start actually. 00:12:24.830 --> 00:12:28.070 - Integrating that payment provider into our E Commerce and 00:12:28.070 --> 00:12:32.750 - so that line of thought process is what we want the team to 00:12:32.750 --> 00:12:35.990 - adopt whenever you're working on problem solving. If you're 00:12:35.990 --> 00:12:41.030 - working on a DNN project, see if you can get the DNN project to 00:12:41.030 --> 00:12:45.710 - be so simplified down. A lot of times I see issues with skin 00:12:45.710 --> 00:12:49.310 - files conflicts in files within the physical HTML, CSS, and 00:12:49.310 --> 00:12:52.910 - JavaScript that's on the page that's causing all the problems. 00:12:52.910 --> 00:12:56.150 - And because it's complicated, we have so many variables. 00:12:56.150 --> 00:12:59.750 - Sometimes you can just change the skin file for 10. 00:12:59.840 --> 00:13:02.942 - Sing something and see if you can. You know, determine that? 00:13:02.942 --> 00:13:05.198 - Oh yes, it is. The skin file is 00:13:05.198 --> 00:13:09.079 - causing the problem. So anyway, the point is to eliminate 00:13:09.079 --> 00:13:13.006 - variables regardless of the context and try to do that in 00:13:13.006 --> 00:13:16.576 - wide swaths. If you're not confident about getting into the 00:13:16.576 --> 00:13:19.789 - precision specific issue that Chris Please on another, another 00:13:19.789 --> 00:13:24.787 - good testing tip on that is a lot of stuff, stuff, at least on 00:13:24.787 --> 00:13:29.428 - the back end for sure. I don't know about the front end is 00:13:29.428 --> 00:13:33.355 - much, but I would assume the typescript is similar. Is copy 00:13:33.355 --> 00:13:36.568 - paste from some other thing that does something similar? 00:13:36.600 --> 00:13:39.810 - Or exact thing, but maybe a different thing. You know 00:13:39.810 --> 00:13:43.020 - slightly different if if you're having issues making that work, 00:13:43.020 --> 00:13:46.872 - like with you made the copy to paste and you're getting some 00:13:46.872 --> 00:13:51.366 - error, see if you can go break the one that you know is working 00:13:51.366 --> 00:13:55.539 - that you copied from in the same manner of the error that you're 00:13:55.539 --> 00:13:59.070 - getting and that'll that'll help you like reduce some of those 00:13:59.070 --> 00:14:02.922 - variables. Like maybe this isn't right, so see if you'd go change 00:14:02.922 --> 00:14:06.774 - that in the working code and it might. It might it might. 00:14:06.860 --> 00:14:10.164 - Like lead you down the path of where you need to go, or at 00:14:10.164 --> 00:14:12.760 - least eliminate areas that you don't need to be looking at. 00:14:14.610 --> 00:14:16.070 - Great point, thank you. 00:14:16.710 --> 00:14:20.706 - Yeah, and I mean ultimately that's the name of the game with 00:14:20.706 --> 00:14:23.370 - problem solving is you're literally trying to give 00:14:23.370 --> 00:14:27.366 - yourself big chunks of kind of things that are working? Um, an 00:14:27.366 --> 00:14:32.361 - in ideas so that you can kind of unblock it. And if you kind of 00:14:32.361 --> 00:14:37.509 - go back to. You know, I, I tend to think about like algebra, an 00:14:37.509 --> 00:14:40.799 - uhm, calculus and some of these other mathematical things that 00:14:40.799 --> 00:14:45.076 - we used to do in school in science class where you kind of 00:14:45.076 --> 00:14:49.353 - have to build up to a solution and you might have to have 00:14:49.353 --> 00:14:53.301 - several steps in order to go about solving the problem and so 00:14:53.301 --> 00:14:57.249 - you're literally doing the same thing here with a lot of these 00:14:57.249 --> 00:15:00.539 - problems. And if you can give yourself that opportunity to 00:15:00.539 --> 00:15:04.158 - think about it mechanically, it can be very helpful, and so 00:15:04.158 --> 00:15:05.803 - ultimately the idea here in 00:15:05.803 --> 00:15:09.510 - general. Is we want everyone to be a excellent problem solver. 00:15:10.090 --> 00:15:14.620 - No, the reality is like no one on the team is an island, and in 00:15:14.620 --> 00:15:18.546 - fact so much so that I won't really want to focus around what 00:15:18.546 --> 00:15:21.868 - you do. Whenever you've done these things and kind of, you 00:15:21.868 --> 00:15:24.888 - know, reasonably exhausted some of these opportunities to try to 00:15:24.888 --> 00:15:26.700 - solve a problem on your own. 00:15:27.270 --> 00:15:31.610 - So this is going to happen very, very often. An even for the more 00:15:31.610 --> 00:15:35.330 - senior folks on the team. This is going to happen very, very 00:15:35.330 --> 00:15:38.740 - often. OK, there's there should be 0 stigma with asking a 00:15:38.740 --> 00:15:42.460 - question, and in fact what I should. what I should say is 00:15:42.460 --> 00:15:44.320 - there should be stigma with not 00:15:44.320 --> 00:15:48.483 - asking a question. Annum, really. It's up to each person 00:15:48.483 --> 00:15:53.280 - on the call an you know in this meeting and on the development 00:15:53.280 --> 00:15:57.708 - team at large to encourage that kind of culture and continue to 00:15:57.708 --> 00:15:58.815 - maintain the culture. 00:15:59.450 --> 00:16:01.019 - Interaction by interaction. 00:16:01.730 --> 00:16:05.566 - It is so important to be able to ask questions now. One of the 00:16:05.566 --> 00:16:08.854 - things that I think that we should kind of, you know, focus 00:16:08.854 --> 00:16:10.772 - our ire toward if we're going to 00:16:10.772 --> 00:16:15.752 - have it. Is when those questions don't then get memorialized and 00:16:15.752 --> 00:16:20.032 - whenever the answers don't get memorialized, OK, so to me 00:16:20.032 --> 00:16:24.740 - that's where any ire should be focused. and I think sometimes 00:16:24.740 --> 00:16:29.020 - some of our experts get frustrated because they are so 00:16:29.020 --> 00:16:32.444 - busy by that, but they'll unintentionally, you know 00:16:32.444 --> 00:16:36.724 - they're busy and they're focusing on trying to get all 00:16:36.724 --> 00:16:40.576 - the things done. And they're. They're kind of, maybe 00:16:40.576 --> 00:16:43.572 - unintentionally, you know, creating some stress because 00:16:43.572 --> 00:16:46.547 - they're feeling. Anxious about getting those tasks done and 00:16:46.547 --> 00:16:50.159 - also being you know, being able to answer all the questions that 00:16:50.159 --> 00:16:54.072 - might be coming up. So that would be my thing to you if 00:16:54.072 --> 00:16:56.781 - you're asking the question is you take ownership of 00:16:56.781 --> 00:17:00.393 - memorializing the question and the answer and I see a lot of 00:17:00.393 --> 00:17:04.306 - the team doing this really well. So the point is, is the first 00:17:04.306 --> 00:17:07.918 - thing you want to do is check these resources next what you 00:17:07.918 --> 00:17:12.132 - want to do if you don't see a solution in general would be to 00:17:12.132 --> 00:17:15.142 - go ahead and ask the question and the clarity team. 00:17:15.150 --> 00:17:20.220 - Stack overflow. I think that it would be really, really 00:17:20.220 --> 00:17:24.070 - reasonable for us to see somewhere between 10 to 20 00:17:24.070 --> 00:17:27.535 - questions asked every single week inside of our stack 00:17:27.535 --> 00:17:31.679 - overflow. And I think that that will probably. I mean, it should 00:17:31.679 --> 00:17:34.269 - reasonably be just like an endless stream of topics that 00:17:34.269 --> 00:17:35.564 - are going on in here. 00:17:36.110 --> 00:17:39.150 - Um, really, ultimately the concept would be that if you're 00:17:39.150 --> 00:17:41.886 - running into something, you're dealing with something we want 00:17:41.886 --> 00:17:44.926 - to make sure that it gets memorialized because it is 00:17:44.926 --> 00:17:47.966 - absolutely going to benefit somebody else on the team at 00:17:47.966 --> 00:17:49.790 - some point, and probably in the 00:17:49.790 --> 00:17:54.400 - near future. So please, if you don't know the answer to a 00:17:54.400 --> 00:17:57.710 - question, go into stackoverflow in general and go ahead and 00:17:57.710 --> 00:18:02.013 - document it as a question and then go ahead and at the people 00:18:02.013 --> 00:18:06.316 - if you haven't done this before, it's pretty easy to put in team 00:18:06.316 --> 00:18:10.619 - members names you can see and you can add the people that you 00:18:10.619 --> 00:18:12.605 - think might be able to answer 00:18:12.605 --> 00:18:17.830 - the question. Um, as best you can type in tags that makes 00:18:17.830 --> 00:18:22.131 - sense for a particular topic, and then of course your title 00:18:22.131 --> 00:18:23.304 - and your details. 00:18:24.160 --> 00:18:27.928 - Ideally, if you can generic size it so it's not very client 00:18:27.928 --> 00:18:31.382 - specific, that would be optimal. We really don't want to have 00:18:31.382 --> 00:18:35.150 - granular client details in here, but put the question in here is 00:18:35.150 --> 00:18:38.918 - reasonably quickly as you can, and then the next step is to 00:18:38.918 --> 00:18:43.314 - take that question and post it in the dev channel or post it to 00:18:43.314 --> 00:18:46.768 - a small subset of developers if you think that it's more 00:18:46.768 --> 00:18:48.338 - appropriate to post to them. 00:18:48.920 --> 00:18:53.820 - And if you don't know how to do this to a small subset of 00:18:53.820 --> 00:18:58.020 - developers, what you do is inside of teams at the left of 00:18:58.020 --> 00:19:02.920 - the search bar, there's a little pencil icon on top of like a box 00:19:02.920 --> 00:19:08.170 - or a piece of paper, and you can click on that and it. Let's make 00:19:08.170 --> 00:19:12.720 - a new chat and then you can enter the names of one or 00:19:12.720 --> 00:19:16.920 - multiple folks, and so that's a really quick way that you can 00:19:16.920 --> 00:19:18.670 - kind of generate a specific 00:19:18.670 --> 00:19:22.008 - subgroup chat. If you need to, but generally speaking we would 00:19:22.008 --> 00:19:25.220 - like everyone to be posting if they get stuck on something 00:19:25.220 --> 00:19:27.848 - other, dealers something posted into stackoverflow and then post 00:19:27.848 --> 00:19:31.936 - it to the Dev Channel and then you can just add in the dev 00:19:31.936 --> 00:19:37.037 - channel as needed. Now, the reason that we want to do this 00:19:37.037 --> 00:19:40.867 - is because there is nothing. There is nothing like knowing 00:19:40.867 --> 00:19:44.697 - that what you're answering question on is going to be 00:19:44.697 --> 00:19:49.293 - usable in the future compared to. I mean just, you know, think 00:19:49.293 --> 00:19:53.123 - about it. If you're answering the same question more than 00:19:53.123 --> 00:19:56.187 - once, it's subconsciously frustrating. I mean, that's just 00:19:56.187 --> 00:20:00.783 - the nature of dealing with, you know, a small business that has 00:20:00.783 --> 00:20:04.613 - a very tight timelines and relatively small margins on some 00:20:04.613 --> 00:20:05.762 - of the projects. 00:20:05.800 --> 00:20:09.859 - You know, we all are feeling the pressure of that naturally 00:20:09.859 --> 00:20:14.656 - within the business, and so this is all part of the DNA of 00:20:14.656 --> 00:20:17.608 - operating any company that's growing in building the 00:20:17.608 --> 00:20:20.560 - organization is. There's naturally going to be some 00:20:20.560 --> 00:20:24.250 - friction around anything that's repeated or double work or etc. 00:20:24.250 --> 00:20:27.940 - And frankly, it's intellectually boring to say the same thing 00:20:27.940 --> 00:20:32.368 - over and over right? So does that make sense to everyone? Let 00:20:32.368 --> 00:20:36.796 - me just see if you guys have questions. It's kind of a 00:20:36.796 --> 00:20:37.903 - monotonous extra step. 00:20:37.950 --> 00:20:41.980 - And it might feel like it's like really kind of, you know, in 00:20:41.980 --> 00:20:45.390 - some cases not necessary. The idea that would be. It's almost 00:20:45.390 --> 00:20:50.040 - like a a key or an entry point, or like the cost of, you know, 00:20:50.040 --> 00:20:54.380 - asking question if you wanted to say it in and it kind of a 00:20:54.380 --> 00:20:57.480 - negative way, but my encouragement to you would be if 00:20:57.480 --> 00:21:01.200 - you're willing to do this. What you're ending up doing is you're 00:21:01.200 --> 00:21:04.300 - sharing this knowledge that you're getting some time for to 00:21:04.300 --> 00:21:08.330 - get support from the team you're sharing it with the rest of the 00:21:08.330 --> 00:21:13.244 - group later. And on top of that, you're also a sensually 00:21:13.244 --> 00:21:15.148 - gamifying this process because. 00:21:16.300 --> 00:21:20.404 - If you post this to the whole team, the whole development team 00:21:20.404 --> 00:21:23.824 - originally you might have only asked someone like Eric and 00:21:23.824 --> 00:21:27.928 - Eric's dealing with 27 of these questions in his teams and you 00:21:27.928 --> 00:21:33.058 - may or may not be aware of that. But if you put it in the 00:21:33.058 --> 00:21:36.478 - development channel, the best person to answer it might be 00:21:36.478 --> 00:21:39.556 - Brendan and Brendan's literally sitting on the perfect answer 00:21:39.556 --> 00:21:42.634 - and can answer it within seconds. An literally knows 00:21:42.634 --> 00:21:46.396 - exactly what's going on based on the information you share an. 00:21:46.410 --> 00:21:50.582 - So just getting it out to the whole team is is a much better 00:21:50.582 --> 00:21:54.158 - approach in general than just keeping it to one person. Let me 00:21:54.158 --> 00:21:57.734 - just pause and see if you guys have any questions or feedback 00:21:57.734 --> 00:22:00.714 - on that, 'cause my expectation would be that behavior would 00:22:00.714 --> 00:22:03.396 - dramatically change toward a lot of questions and stackoverflow. 00:22:03.396 --> 00:22:07.568 - It's not a hard requirement, is not the end of the world, but I 00:22:07.568 --> 00:22:10.548 - really, really think it makes sense. And Chris and Eric, 00:22:10.548 --> 00:22:14.720 - please let me know and let you know. Let the team know if this 00:22:14.720 --> 00:22:16.508 - makes sense to you as well. 00:22:16.560 --> 00:22:19.577 - Or if you think I'm off my 00:22:19.577 --> 00:22:22.378 - rocker. Posting this in this stackoverflow so we can 00:22:22.378 --> 00:22:25.338 - accumulate it and then posting it to the Dev Channel. 00:22:26.270 --> 00:22:28.700 - I personally think it's really great up just because like 00:22:28.700 --> 00:22:31.859 - whenever I started, I didn't really have a lot of that, so it 00:22:31.859 --> 00:22:34.289 - was just like asking everyone. And then sometimes people have 00:22:34.289 --> 00:22:36.962 - different answers and stuff and it's all a lot of tribal 00:22:36.962 --> 00:22:39.392 - knowledge. So something like this is really cool for new 00:22:39.392 --> 00:22:42.065 - people and really, just anyone that here, even if you're not 00:22:42.065 --> 00:22:44.738 - you, just because instead of having it just tribal stuff or 00:22:44.738 --> 00:22:47.654 - stuff that you just learned along the way, it can make it 00:22:47.654 --> 00:22:50.813 - easier and make it faster to build up. So I think it's great 00:22:50.813 --> 00:22:52.514 - and I use it all the time. 00:22:54.150 --> 00:22:58.231 - Yeah, and I just want to personally call Heather out and 00:22:58.231 --> 00:23:01.941 - just encourage you, Heather um, heathers, denigrate job at this 00:23:01.941 --> 00:23:06.764 - an it's really built a lot of the knowledge that we do have, 00:23:06.764 --> 00:23:10.103 - and certainly the team members that are responding and 00:23:10.103 --> 00:23:11.216 - answering heathers stack 00:23:11.216 --> 00:23:16.734 - overflows. And I do want to tell you guys that there are some 00:23:16.734 --> 00:23:20.172 - Easter eggs based on your point accumulation and stackoverflow 00:23:20.172 --> 00:23:21.700 - that will be, um. 00:23:21.700 --> 00:23:25.209 - Cash bonuses, um Easter eggs that will be paid out upon 00:23:25.209 --> 00:23:28.080 - hitting certain levels within Stackoverflow. Ann, I know that 00:23:28.080 --> 00:23:31.270 - that's probably not the world's most motivating thing, but just 00:23:31.270 --> 00:23:35.098 - so you know, they're going to be there once we hit certain 00:23:35.098 --> 00:23:38.288 - levels for a team. And for individuals, you'll open up 00:23:38.288 --> 00:23:42.116 - those Easter eggs and that will be something that will be kind 00:23:42.116 --> 00:23:45.625 - of a nice surprise for those who are really engaging in 00:23:45.625 --> 00:23:49.453 - this. And then Chris, you were going to say something as well. 00:23:50.640 --> 00:23:54.314 - Yeah, absolutely. Just wanted a iterate on a guys might have 00:23:54.314 --> 00:23:58.656 - seen me. You know post in the general channel or even on the 00:23:58.656 --> 00:24:02.998 - team's Channel and it's like I'm a one line parrot where I'm just 00:24:02.998 --> 00:24:07.006 - like hey can you post this to stack overflow? You know almost 00:24:07.006 --> 00:24:11.014 - like the paper clip and word or something like that, but The 00:24:11.014 --> 00:24:15.356 - thing is that you know, I think we all have even seen multiple 00:24:15.356 --> 00:24:19.030 - renditions of the same question kind of asked and teams and 00:24:19.030 --> 00:24:22.370 - unfortunately you know that that is not very searchable and 00:24:22.370 --> 00:24:23.706 - people you don't search. 00:24:23.710 --> 00:24:27.150 - Natively think the search teams for any kind of technical 00:24:27.150 --> 00:24:31.622 - questions or anything like that. And even if you do know where it 00:24:31.622 --> 00:24:35.750 - is I personally found that it's kind of hard or difficult to 00:24:35.750 --> 00:24:39.190 - search teams for any kind of technical knowledge. So that's 00:24:39.190 --> 00:24:42.630 - basically why we have the new cleaner in the stackoverflow, 00:24:42.630 --> 00:24:47.446 - and I think everybody is as far as Devs go is on stack overflow. 00:24:47.446 --> 00:24:51.230 - At least I guarantee you right now everybody has a stack 00:24:51.230 --> 00:24:53.638 - overflow tab open, if not 30 of 00:24:53.638 --> 00:24:58.786 - them so. Um, the big thing is that we want to, you know, 00:24:58.786 --> 00:25:02.350 - definitely post as many questions as much knowledge and 00:25:02.350 --> 00:25:05.518 - stackoverflow that we can, because just like normal 00:25:05.518 --> 00:25:08.686 - stackoverflow like I've literally never really had to 00:25:08.686 --> 00:25:11.854 - ask a question and typical stackoverflow, just because 00:25:11.854 --> 00:25:16.210 - there's always like 3 versions of the same question that is 00:25:16.210 --> 00:25:22.150 - related to my bug or problem. So we want to get to that point as 00:25:22.150 --> 00:25:24.130 - far as the clarity stackoverflow 00:25:24.130 --> 00:25:28.260 - so. We rarely are even asking questions because most of them 00:25:28.260 --> 00:25:33.070 - have been asked or a variant of that question has been asked and 00:25:33.070 --> 00:25:37.880 - our own stack overflow and you know, we do have some things do 00:25:37.880 --> 00:25:42.690 - change from time to time as far as like stuff from, you know 00:25:42.690 --> 00:25:47.500 - some of you have worked on 4.7 two, 2021 in wall things or 00:25:47.500 --> 00:25:52.310 - maybe cool an async now. Or you know there's a lot less configs 00:25:52.310 --> 00:25:54.530 - dad in to get everything built 00:25:54.530 --> 00:25:58.570 - up. A lot of this stuff still stays the same. You know. Uhm, 00:25:58.570 --> 00:26:01.925 - and there's some. There's some stuff that you know that are 00:26:01.925 --> 00:26:04.975 - just building blocks of the application, either on the dot 00:26:04.975 --> 00:26:09.550 - net side or on that you know the angular JS side or on the DNA 00:26:09.550 --> 00:26:12.905 - inside that are probably not going to change too much just 00:26:12.905 --> 00:26:16.870 - from the paradigm that they were built on or built around. So a 00:26:16.870 --> 00:26:20.225 - lot of it will still be pretty relevant with the technologies 00:26:20.225 --> 00:26:23.580 - that we work with, so just wanted to iterate. Please post 00:26:23.580 --> 00:26:25.410 - as much as possible and just. 00:26:25.420 --> 00:26:28.800 - The link in general or share the link in the appropriate team or 00:26:28.800 --> 00:26:31.920 - in the development team, or even you know. While you can tag 00:26:31.920 --> 00:26:35.300 - people on this, you know you can even shoot the link directly to 00:26:35.300 --> 00:26:38.160 - somebody via teams as well, just so they can answer it. 00:26:39.670 --> 00:26:43.362 - Awesome, thank you and feel free if anyone else wants to make a 00:26:43.362 --> 00:26:45.066 - comment on it, it sounds like. 00:26:45.640 --> 00:26:51.160 - The other things that I'll point out about this in general are. 00:26:51.170 --> 00:26:53.690 - There are some pretty interesting features that are 00:26:53.690 --> 00:26:56.840 - part of stackoverflow that I I don't know if everyone's 00:26:56.840 --> 00:26:57.785 - used these before. 00:26:58.850 --> 00:27:05.270 - So you can actually go in and, um, say that you know it was a 00:27:05.270 --> 00:27:09.978 - good question. It was a good answer. Mark Mark the particular 00:27:09.978 --> 00:27:14.686 - answer as accepted. You can also add comments and then comments 00:27:14.686 --> 00:27:16.398 - themselves can be upvoted. 00:27:16.530 --> 00:27:22.228 - And in Downvoted too, if you want, um, so you can kind of do 00:27:22.228 --> 00:27:25.891 - those things and it actually increases that team members 00:27:25.891 --> 00:27:27.519 - points that they have. 00:27:27.520 --> 00:27:32.239 - Bye bye you doing that. Uhm so you can see here for for 00:27:32.239 --> 00:27:36.595 - heathers reputation she's really had a lot of questions and a lot 00:27:36.595 --> 00:27:40.588 - of reputation increase and this is something that I think is 00:27:40.588 --> 00:27:44.944 - really great as a team to encourage those of us who kind 00:27:44.944 --> 00:27:50.026 - of are asking a lot of questions to go in and just give some 00:27:50.026 --> 00:27:53.656 - upvotes to somebody who asked something that you thought was 00:27:53.656 --> 00:27:57.286 - useful or an answer that you thought was useful, etc. 00:27:58.060 --> 00:28:02.950 - So I just I just want you guys to take some time, get, get your 00:28:02.950 --> 00:28:07.514 - questions in here. Uhm and in my kind of statement to you as if 00:28:07.514 --> 00:28:11.426 - you put the questions here and then put them in the development 00:28:11.426 --> 00:28:14.360 - channel. You know my encouragement to the team at 00:28:14.360 --> 00:28:18.272 - large will be that you will get much better support overall by 00:28:18.272 --> 00:28:22.836 - doing that and so just to kind of put my money where my mouth 00:28:22.836 --> 00:28:27.074 - is there. First of all, if you do end up meeting with somebody, 00:28:27.074 --> 00:28:28.378 - a lot of these. 00:28:28.430 --> 00:28:32.606 - Issues that we run into. They're not, you know. They're not easy 00:28:32.606 --> 00:28:36.434 - to resolve over stackoverflow, right? You end up having like a 00:28:36.434 --> 00:28:40.262 - teams meeting an, so you're going to post the question here 00:28:40.262 --> 00:28:44.786 - and then you're going to end up with the teams meaning a screen 00:28:44.786 --> 00:28:47.918 - share or pretty detailed teams chat that goes on. 00:28:48.550 --> 00:28:50.389 - OK so um. 00:28:50.910 --> 00:28:54.699 - That's fine, uh, but that information doesn't end up 00:28:54.699 --> 00:28:58.909 - coming back into stackoverflow very easily, so it might take 00:28:58.909 --> 00:29:03.961 - some time for you to kind of memorialize what you guys did, 00:29:03.961 --> 00:29:08.171 - and then how you resolve the issue. It's absolutely critical 00:29:08.171 --> 00:29:13.223 - though, that if we're going to take advantage of this, that the 00:29:13.223 --> 00:29:17.854 - actual answer get posted. So once again, you can see exactly 00:29:17.854 --> 00:29:21.643 - what the what the approach would be here so. 00:29:21.700 --> 00:29:25.363 - Heather, in this example posted the question and then she posted 00:29:25.363 --> 00:29:29.026 - the answer and you can actually get credit for posting the 00:29:29.026 --> 00:29:33.355 - question and posting the answer and so that again if you look at 00:29:33.355 --> 00:29:37.266 - Heather's profile. She just got more points because I just 00:29:37.266 --> 00:29:42.170 - uploaded that. An the UM, the ideal scenario would be that 00:29:42.170 --> 00:29:46.170 - within the subject matter areas we kind of developed these 00:29:46.170 --> 00:29:49.770 - Stackoverflow Czars who are really really good at their 00:29:49.770 --> 00:29:53.770 - specific subject matter areas, so I'm very happy to approve 00:29:53.770 --> 00:29:58.170 - from a management perspective. The time that you might need to 00:29:58.170 --> 00:30:03.370 - go put a nice detailed post in a stack overflow with content that 00:30:03.370 --> 00:30:07.770 - answers what you had to do to resolve a particular issue. 00:30:08.450 --> 00:30:12.333 - Um, especially if you know that it's tribal knowledge. I mean, 00:30:12.333 --> 00:30:15.510 - if it's something that's already answered on stackoverflow or 00:30:15.510 --> 00:30:19.040 - Google, we don't want to repeat, you know, literally everything 00:30:19.040 --> 00:30:22.217 - under the sun and just be in Stackoverflow repeating 00:30:22.217 --> 00:30:25.394 - everything that's already out there, but anything that's you 00:30:25.394 --> 00:30:28.924 - know clarity specific. And it doesn't just have to be 00:30:28.924 --> 00:30:32.807 - development related, it can be processes. It can be, you know 00:30:32.807 --> 00:30:36.690 - where to find things, how we handle certain things, etc. And 00:30:36.690 --> 00:30:39.161 - so any of the time that you 00:30:39.161 --> 00:30:42.663 - need. To kind of memorialize that back into stackoverflow is 00:30:42.663 --> 00:30:46.480 - something that you know as long as it's somewhat reasonable and 00:30:46.480 --> 00:30:50.644 - I am struggling to think of a scenario where that wouldn't be 00:30:50.644 --> 00:30:54.808 - the case, we're happy to support the time that you're putting in 00:30:54.808 --> 00:30:57.237 - as part of your kind of your 00:30:57.237 --> 00:31:01.741 - course schedule. Um, so is the management as the manager team 00:31:01.741 --> 00:31:03.386 - members? If you guys see. 00:31:03.890 --> 00:31:07.994 - You know, a lot of these big chunks of time coming through 00:31:07.994 --> 00:31:12.440 - that are related to that. Just let me know and I can improve 00:31:12.440 --> 00:31:16.202 - that time an you know will certainly be looking for the 00:31:16.202 --> 00:31:20.306 - team to put more effort into as you kind of get questions 00:31:20.306 --> 00:31:21.332 - answered. Documenting things 00:31:21.332 --> 00:31:24.892 - into stackoverflow. And ultimately, uh, the other thing 00:31:24.892 --> 00:31:29.598 - that I want to point out is if you would please record your 00:31:29.598 --> 00:31:33.218 - meetings when you're you're having them with. With some of 00:31:33.218 --> 00:31:36.476 - these different, quote, quote unquote, expert team members. If 00:31:36.476 --> 00:31:40.096 - you're doing a screen share or you're going over something 00:31:40.096 --> 00:31:45.310 - technical. If you can record the session um and I know that there 00:31:45.310 --> 00:31:49.450 - might be some things that you might say jokingly or you know 00:31:49.450 --> 00:31:52.900 - you might be just talking about random topics while you're 00:31:52.900 --> 00:31:56.350 - working. That's fine, but if you can save this sessions. 00:31:56.910 --> 00:32:00.166 - One of the things that we're going to be doing with 00:32:00.166 --> 00:32:02.534 - everything that's in Stackoverflow is bringing it in. 00:32:02.534 --> 00:32:04.014 - Memorializing it into new clean 00:32:04.014 --> 00:32:09.452 - oh. So the idea is to, you know, just throw spaghetti against the 00:32:09.452 --> 00:32:13.062 - wall and Stackoverflow. So this should literally be the place 00:32:13.062 --> 00:32:17.033 - where you just put everything that happens tossed in the Dev 00:32:17.033 --> 00:32:21.004 - Channel and then at people so that you get responses OK. 00:32:21.550 --> 00:32:25.216 - Once you get something solved then you go post what you did or 00:32:25.216 --> 00:32:28.882 - what the solution was here, even if you're the one who has to 00:32:28.882 --> 00:32:32.830 - post the answer and a lot of times it's going to be the case. 00:32:33.800 --> 00:32:35.558 - And then, once you've done that. 00:32:36.540 --> 00:32:41.363 - The plan and we have resources to do this is to literally come 00:32:41.363 --> 00:32:44.702 - back through Stackoverflow roughly once a month and then 00:32:44.702 --> 00:32:49.154 - bring that back into new clean. Oh, in a very organized fashion. 00:32:49.154 --> 00:32:53.606 - And so our wiki will contain the more organized content. So it's 00:32:53.606 --> 00:32:58.058 - got better structure and it's, you know, it's just a very nice 00:32:58.058 --> 00:33:02.510 - clean, you know, infrastructure to be able to go find things and 00:33:02.510 --> 00:33:05.849 - have some hierarchy and just general structure to it. 00:33:05.890 --> 00:33:07.338 - In addition to that. 00:33:07.840 --> 00:33:13.468 - Uh, any videos that you guys have that we can use in? And we 00:33:13.468 --> 00:33:17.488 - can memorialize will also be cleaning those up and then 00:33:17.488 --> 00:33:21.508 - posting those two are LMS system so LMS Learning Management 00:33:21.508 --> 00:33:26.734 - System and the idea is that if you take videos and record the 00:33:26.734 --> 00:33:30.352 - screen while you're doing something and you know reviewing 00:33:30.352 --> 00:33:33.568 - something detailed, we can accumulate that knowledge into 00:33:33.568 --> 00:33:36.784 - our internal LMS system and we're creating certification 00:33:36.784 --> 00:33:38.392 - around those different topics. 00:33:38.450 --> 00:33:42.064 - And I, I'm not saying that all of our knowledge is gonna come 00:33:42.064 --> 00:33:44.844 - from random meetings where you have some you know really 00:33:44.844 --> 00:33:49.770 - specific error. I'm just saying if it's if it's reasonably 00:33:49.770 --> 00:33:54.067 - convenient recorded. Um, one of the team members I was working 00:33:54.067 --> 00:33:57.510 - with today was telling me about some specific settings and stuff 00:33:57.510 --> 00:34:01.892 - that they were going over and it was just kind of an ad hoc 00:34:01.892 --> 00:34:04.709 - review session, but it turned into a really detailed 00:34:04.709 --> 00:34:07.526 - comprehensive phone call that covered all of the config 00:34:07.526 --> 00:34:12.010 - settings. And so that was a great opportunity. If you know 00:34:12.010 --> 00:34:15.600 - if that session was recorded, that would be a great 00:34:15.600 --> 00:34:18.831 - opportunity to kind of have this memorialized information that 00:34:18.831 --> 00:34:22.421 - then can be parlayed into knowledge that everyone on the 00:34:22.421 --> 00:34:26.729 - team can easily access. And one of the really cool things about 00:34:26.729 --> 00:34:30.319 - recording is we've got a really nice transcription process that 00:34:30.319 --> 00:34:34.986 - can get all of the content out of the recordings and then parse 00:34:34.986 --> 00:34:39.294 - it so we can store it in a documented format. That's easy 00:34:39.294 --> 00:34:40.371 - for you to. 00:34:40.430 --> 00:34:44.368 - Text search on so the goal, the overarching goal from the 00:34:44.368 --> 00:34:47.948 - management team and from the technical leadership team is to 00:34:47.948 --> 00:34:51.886 - try to get all the information that we're just sharing and 00:34:51.886 --> 00:34:56.182 - trading with each other to be in in a more formal process 00:34:56.182 --> 00:35:00.478 - starting from the ground up with stack overflow and you want to 00:35:00.478 --> 00:35:03.700 - think of stack overflow is throwing spaghetti against the 00:35:03.700 --> 00:35:08.354 - wall, and then once you kind of get the solution coming back in 00:35:08.354 --> 00:35:10.502 - and posting the answer to the 00:35:10.502 --> 00:35:15.780 - solution. And I just want to encourage you that if you are in 00:35:15.780 --> 00:35:20.235 - fact putting you know doing the work inside of stack overflow, 00:35:20.235 --> 00:35:25.905 - you will be reported for that. Uhm, you know I want you to see 00:35:25.905 --> 00:35:30.360 - it as number one, job security, #2 Easter eggs, #3 quarterly 00:35:30.360 --> 00:35:33.600 - reviews, #4 leadership opportunities. All of us have 00:35:33.600 --> 00:35:37.650 - the opportunity to build this company and to help deliver 00:35:37.650 --> 00:35:41.295 - solutions for our clients and bring value to clients. 00:35:41.320 --> 00:35:46.375 - And man I have to tell you one of the number one things that I 00:35:46.375 --> 00:35:50.419 - talk with our board about that is a huge challenge for this 00:35:50.419 --> 00:35:53.452 - business model is sharing tribal knowledge effectively and I 00:35:53.452 --> 00:35:58.170 - think everyone on this call will agree with me an each of us has 00:35:58.170 --> 00:36:02.551 - to do that, So what I'm telling you is you know carte Blanche 00:36:02.551 --> 00:36:07.269 - take the time and I'm you know, I'm not looking for you to stop 00:36:07.269 --> 00:36:09.965 - everything your doing but incrementally together, we can 00:36:09.965 --> 00:36:11.313 - build this content an? 00:36:11.400 --> 00:36:15.840 - Over the course of the next 6 to 12 months, you know, be 20 to 00:36:15.840 --> 00:36:19.392 - 40% better and boy wouldn't you be so much happier. If this 00:36:19.392 --> 00:36:22.056 - tribal knowledge hearing challenge was 20 to 40% better, 00:36:22.056 --> 00:36:25.608 - wouldn't that be an awesome thing? So let me take a breather 00:36:25.608 --> 00:36:29.160 - and see if you guys have any questions or comments on that, 00:36:29.160 --> 00:36:32.712 - and then I'll kind of switch gears to another topic here. I 00:36:32.712 --> 00:36:36.560 - have a comment so so that you just had a pretty deep call 00:36:36.560 --> 00:36:40.704 - about the Configs. Was it for 2020.1 yeah it was OK. Cool so I 00:36:40.704 --> 00:36:44.552 - posted up a a new cleaner about how to update those configs, but 00:36:44.552 --> 00:36:46.328 - I think that video of you. 00:36:46.410 --> 00:36:49.280 - Already LinkedIn there, so whoever you run that with, could 00:36:49.280 --> 00:36:52.150 - you maybe put that in there? That could be helpful. 00:36:52.870 --> 00:36:54.955 - Yeah, that would be great. 00:36:54.955 --> 00:36:58.956 - Search 2020.1. It unfortunately was not recorded, so it wasn't 00:36:58.956 --> 00:37:02.760 - horrible, but it's OK. I mean, we're all human I'm I'm looking 00:37:02.760 --> 00:37:07.198 - at, you know, no one is perfect. I'm at the top of that. Not 00:37:07.198 --> 00:37:11.002 - perfect list, but yeah, we we definitely plan to have a review 00:37:11.002 --> 00:37:15.123 - around that. and I I think this is great. Thank you for posting 00:37:15.123 --> 00:37:16.708 - this. This is really detailed. 00:37:16.708 --> 00:37:22.290 - Looks really good. So that that is kind of the next topic is 00:37:22.290 --> 00:37:27.022 - like how to create a new new clean. Oh, and we already went 00:37:27.022 --> 00:37:31.026 - over Stackoverflow and I promise you guys, I'm almost done with 00:37:31.026 --> 00:37:33.210 - my soapbox here and going over 00:37:33.210 --> 00:37:37.326 - this. But let me see if anyone else has comments here before I 00:37:37.326 --> 00:37:40.714 - wrap up. OK, pretty basic stuff. You know, rocket science here. 00:37:41.340 --> 00:37:46.845 - So if you are gonna go up if you are going to go post something 00:37:46.845 --> 00:37:51.616 - that you know you really want to stick and you know it's really 00:37:51.616 --> 00:37:56.387 - valuable and a lot of people are talking about it, new clean oh 00:37:56.387 --> 00:38:01.158 - is ultimately the this place where you want it to go to be 00:38:01.158 --> 00:38:05.562 - very persistent and searchable. Kind of as a topic or a pretty 00:38:05.562 --> 00:38:08.865 - thorough coverage of something. So ultimately the process would 00:38:08.865 --> 00:38:11.067 - be throw it against the wall 00:38:11.067 --> 00:38:15.468 - here. Get it out in into this forum if it's a question or an 00:38:15.468 --> 00:38:19.752 - error or a bug or any kind of blocker, throw it in here. Try 00:38:19.752 --> 00:38:24.036 - to generic size it posted to the dev team. There you go once you 00:38:24.036 --> 00:38:27.402 - get your answer or you work through it. Come back, summarize 00:38:27.402 --> 00:38:32.298 - it, and if you need time. If it takes a lot of time for you to 00:38:32.298 --> 00:38:35.970 - get that posted here, let your manager know. Will get some time 00:38:35.970 --> 00:38:39.948 - approved for you so that you can have time for doing that work. 00:38:39.948 --> 00:38:41.172 - It's absolutely critical for 00:38:41.172 --> 00:38:44.907 - your. For the rest of the team and for the business that we do, 00:38:44.907 --> 00:38:47.497 - that the second thing is, once you kind of crystallized 00:38:47.497 --> 00:38:50.087 - something, or you know you're very familiar, you're seeing it 00:38:50.087 --> 00:38:52.677 - happen it over and over. Your hearing other people talking 00:38:52.677 --> 00:38:56.562 - about it. We do want to post a new clean, a post about it, and 00:38:56.562 --> 00:38:59.929 - so really all you need to do for new kleinos go to the 00:38:59.929 --> 00:39:03.037 - appropriate area. A lot of the things that we're going to be 00:39:03.037 --> 00:39:04.591 - doing, you're going to be inside 00:39:04.591 --> 00:39:09.506 - the development area. So let's just say we're gonna go in and 00:39:09.506 --> 00:39:13.620 - do troubleshooting how TOS are also very helpful. And let's say 00:39:13.620 --> 00:39:18.482 - we're going to make a new a new piece of content. You will 00:39:18.482 --> 00:39:22.222 - generally want to navigate to the appropriate area. There are 00:39:22.222 --> 00:39:25.962 - different ways to kind of navigate the content. You can 00:39:25.962 --> 00:39:29.702 - see they're kind of different visual presentations of the same 00:39:29.702 --> 00:39:31.572 - content. There's also this kind 00:39:31.572 --> 00:39:36.450 - of interesting. Movie The Matrix so you can kind of navigate the 00:39:36.450 --> 00:39:40.399 - content with different methods and this has a little zoom in 00:39:40.399 --> 00:39:45.066 - and zoom out and it's kind of hard over this Prezzo. But Long 00:39:45.066 --> 00:39:49.374 - story short, you can kind of see the content in different ways. 00:39:49.580 --> 00:39:53.188 - Generally speaking though, I would use the. You know, one of 00:39:53.188 --> 00:39:57.452 - these kind of standard areas and just kind of drill in and then 00:39:57.452 --> 00:40:02.372 - kind of go into the area and then you can add a section or a 00:40:02.372 --> 00:40:05.980 - page and they call it a subcluster here so you can 00:40:05.980 --> 00:40:07.292 - create a sub cluster. 00:40:08.010 --> 00:40:11.418 - And so this would be, uhm, you know. 00:40:13.800 --> 00:40:14.900 - I don't know, uh? 00:40:16.980 --> 00:40:18.090 - She says. 00:40:19.890 --> 00:40:24.422 - And just generally, when you're writing titles as your call, um. 00:40:24.960 --> 00:40:27.193 - The titles themselves are searchable without hitting 00:40:27.193 --> 00:40:31.340 - enter, so if you can try to be as Descriptive as possible. That 00:40:31.340 --> 00:40:35.487 - can be really helpful for folks. So one of the things that I 00:40:35.487 --> 00:40:37.082 - would do is just go. 00:40:37.930 --> 00:40:38.590 - Hum. 00:40:39.770 --> 00:40:44.628 - Get the full name for that OK and then now you have your your 00:40:44.628 --> 00:40:49.139 - cluster as they call it and then you can create pages under any 00:40:49.139 --> 00:40:52.956 - cluster. So now I can say you know what it is. 00:40:54.700 --> 00:40:59.848 - OK, so none of this is complicated, I I do want to say 00:40:59.848 --> 00:41:04.204 - in general though, that it's pretty easy to add content here. 00:41:04.204 --> 00:41:08.560 - I get kind of intimidated with something that's new. You can 00:41:08.560 --> 00:41:14.104 - see that all I had to do was login, click a few buttons like 00:41:14.104 --> 00:41:18.856 - plus is over here and then start typing. You can paste pretty 00:41:18.856 --> 00:41:22.816 - much anything in here, including pictures, so you literally can 00:41:22.816 --> 00:41:24.796 - take a picture I've got. 00:41:24.820 --> 00:41:28.890 - Two, I've got a a picture on my my desktop. 00:41:30.600 --> 00:41:35.556 - And you can just drag it onto the thing and bam, there you go. 00:41:35.556 --> 00:41:39.804 - So now you've got your little image in there and you can 00:41:39.804 --> 00:41:44.052 - change the properties of the image and modify it. And it has 00:41:44.052 --> 00:41:47.592 - some really nice capabilities for Bulleting an being able to 00:41:47.592 --> 00:41:49.362 - go in and change formatting. 00:41:50.020 --> 00:41:54.739 - Are you also have chat here? So if you were seeing somebody who 00:41:54.739 --> 00:41:59.095 - you know added content and you think they need to modify it, 00:41:59.095 --> 00:42:03.088 - use the chat tool. You can follow a particular area and 00:42:03.088 --> 00:42:07.807 - kind of see what's changing and so you can generally do a lot 00:42:07.807 --> 00:42:12.163 - with this. You can certainly do other things. You can view the 00:42:12.163 --> 00:42:16.156 - history and kind of see who's modified it etc. But generally 00:42:16.156 --> 00:42:19.423 - speaking the concept is like once it's been memorialized 00:42:19.423 --> 00:42:20.512 - enough and you. 00:42:20.550 --> 00:42:23.982 - Talked about it enough or you've heard it talked about enough. 00:42:23.982 --> 00:42:27.414 - Please go out this content, especially if you kind of become 00:42:27.414 --> 00:42:28.662 - familiar with it enough. 00:42:29.380 --> 00:42:33.260 - Because it absolutely will be helpful down the road and 00:42:33.260 --> 00:42:37.528 - probably many, many times over. So any questions or comments on 00:42:37.528 --> 00:42:42.184 - that? OK, and then the only other thing I wanted to talk 00:42:42.184 --> 00:42:43.736 - about briefly is just.00:42:44.600 --> 00:42:49.652 - If you're not getting a response to questions, uhm, if you're not 00:42:49.652 --> 00:42:54.704 - getting an answer to questions from the team by a kind of 00:42:54.704 --> 00:42:58.072 - taking these approaches or blockers, please just keep 00:42:58.072 --> 00:43:01.440 - renewing your request for support or for help. 00:43:01.450 --> 00:43:04.954 - One of the things that is to me is really helpful is. 00:43:05.760 --> 00:43:09.973 - Um, knowing that you need help knowing that you need support, 00:43:09.973 --> 00:43:14.186 - one of the things that I always tell the management team 00:43:14.186 --> 00:43:15.718 - whenever we're dealing with. 00:43:16.610 --> 00:43:20.383 - Any kind of performance issue with, you know someone on the 00:43:20.383 --> 00:43:24.499 - team is almost always that team member is just not aware or 00:43:24.499 --> 00:43:27.929 - they're not exactly aware they're not sure. They can tell 00:43:27.929 --> 00:43:31.016 - there's something wrong, but they don't actually know for 00:43:31.016 --> 00:43:35.475 - sure what the problem is or if there is a problem there and 00:43:35.475 --> 00:43:39.591 - less we directly tell them, You know, none of us are mind 00:43:39.591 --> 00:43:43.707 - readers. In other words, we cannot read minds, I, I think it 00:43:43.707 --> 00:43:46.794 - would be very interesting and also very scary, right? 00:43:46.880 --> 00:43:53.555 - Hum. And so ultimately, I think the point is that, UM, in it you 00:43:53.555 --> 00:43:56.660 - know in a similar fashion, the management team members, 00:43:56.660 --> 00:43:59.765 - leaders, the technical knowledge you know, the subject matter 00:43:59.765 --> 00:44:03.560 - experts. They can't read your mind and they don't know that 00:44:03.560 --> 00:44:07.355 - you're struggling or that you're stuck on something, or that you 00:44:07.355 --> 00:44:11.840 - need support and less you say it an and sometimes they miss it 00:44:11.840 --> 00:44:12.875 - because they're busy. 00:44:12.930 --> 00:44:16.506 - Everybody, I think on the team has been there. You know you're 00:44:16.506 --> 00:44:19.188 - dealing with something that's pretty stressful or you're just 00:44:19.188 --> 00:44:22.764 - dealing with a lot of different things and going from this to 00:44:22.764 --> 00:44:26.936 - that to this. That and it's you know, so you may just miss it. 00:44:26.936 --> 00:44:30.214 - There are some pretty big differences with how you at in 00:44:30.214 --> 00:44:31.704 - the general channel for the 00:44:31.704 --> 00:44:36.188 - development team. If you just post something and you don't at 00:44:36.188 --> 00:44:39.608 - all, no one's going to generally see the notification very 00:44:39.608 --> 00:44:45.692 - quickly. It's not the best thing in the world to just at general, 00:44:45.692 --> 00:44:49.060 - within the development team channel all the time. 00:44:49.570 --> 00:44:53.974 - But if you have something urgent, do it. Um, I would say, 00:44:53.974 --> 00:44:57.277 - generally speaking, if you can post everything to the 00:44:57.277 --> 00:45:01.314 - development team channel and the posts area, but then go ahead 00:45:01.314 --> 00:45:05.718 - and do an app for specific people. So at Eric at Chris, 00:45:05.718 --> 00:45:10.489 - etc. If you believe that they can help you, and then if you 00:45:10.489 --> 00:45:14.893 - don't get a response quickly then you can add other people or 00:45:14.893 --> 00:45:16.728 - at general within the channel. 00:45:17.300 --> 00:45:20.051 - Uhm, I think just kind of some 00:45:20.051 --> 00:45:24.122 - etiquette. On how to you know how to get people to respond 00:45:24.122 --> 00:45:27.506 - with without being like you know that person who keeps making the 00:45:27.506 --> 00:45:30.044 - little thing flash while everyone's trying to focus? and 00:45:30.044 --> 00:45:33.710 - I really, really like for Chris. Eric had like for you guys to 00:45:33.710 --> 00:45:37.376 - make any comments. If you guys have him and just in general on 00:45:37.376 --> 00:45:40.760 - the team if you guys have feedback on that 'cause I think 00:45:40.760 --> 00:45:43.862 - that I can do something that's fluid and changes, but my 00:45:43.862 --> 00:45:46.964 - suggestion would be you posted to the channel and you add 00:45:46.964 --> 00:45:50.348 - specific people you think can help you and then if you don't 00:45:50.348 --> 00:45:52.040 - get a response within you know. 00:45:52.120 --> 00:45:54.386 - 10 or 15 minutes just go ahead and add the general. 00:45:54.386 --> 00:45:55.828 - What do you guys say to that? 00:45:58.470 --> 00:46:01.935 - Yeah, definitely couldn't agree more. Uhm, you know, and I think 00:46:01.935 --> 00:46:05.715 - that's the thing where it's like I'll see you know posts from 00:46:05.715 --> 00:46:09.495 - time to time were you know nobody is added or anything like 00:46:09.495 --> 00:46:13.590 - that. It's just kind of up in the air question will you know 00:46:13.590 --> 00:46:17.685 - if we kind of go in that model? Nobody gets pinged and nobody 00:46:17.685 --> 00:46:21.150 - gets a notification and just, you know, as as real human 00:46:21.150 --> 00:46:23.985 - beings in this weird technological time we all like 00:46:23.985 --> 00:46:26.505 - to respond to notification. So definitely deadly. Super 00:46:26.505 --> 00:46:28.395 - important and feel free to just. 00:46:28.480 --> 00:46:32.248 - You know, ping more than one person. If it's like a double, 00:46:32.248 --> 00:46:35.388 - you know, kind of double question or something like that, 00:46:35.388 --> 00:46:40.098 - but it's kind of in the same. In the same vein of like you know 00:46:40.098 --> 00:46:43.238 - if you're if you're somewhere and some. For whichever reason 00:46:43.238 --> 00:46:46.378 - an accident happens in your. There's several, you know, say 00:46:46.378 --> 00:46:49.518 - 10 people standing around, you know, hey, somebody call 911. 00:46:50.320 --> 00:46:52.168 - There's nobody will ever do it. 00:46:52.680 --> 00:46:55.470 - So you know, in that situation, under emergency situation you 00:46:55.470 --> 00:46:59.097 - would point at somebody and say you call 911 and it's kind of 00:46:59.097 --> 00:47:02.724 - the same aspect here is that in general it's kind of like, you 00:47:02.724 --> 00:47:05.793 - know, just with human nature. It's kind of like oh somebody 00:47:05.793 --> 00:47:09.420 - somebody will get to that for sure you know. Or like I don't 00:47:09.420 --> 00:47:13.326 - really know a lot about it. You know, I know a little bit about 00:47:13.326 --> 00:47:16.674 - it, but maybe somebody knows more than me, so let them answer 00:47:16.674 --> 00:47:20.301 - it well instead of kind of going off that general if you just 00:47:20.301 --> 00:47:23.370 - point somebody out individually that you think will be able to. 00:47:23.430 --> 00:47:27.126 - You no answer it. They might not be able to answer it, but they 00:47:27.126 --> 00:47:30.822 - might know who will and they can ask them. But yeah, it's I mean 00:47:30.822 --> 00:47:34.254 - it's not. Uh, you know I. I would say that using general is 00:47:34.254 --> 00:47:36.894 - not a bad thing, but generally having your questions more 00:47:36.894 --> 00:47:38.478 - pointed, it would be the first 00:47:38.478 --> 00:47:42.645 - way to go. Thanks and does anyone else have any comments on 00:47:42.645 --> 00:47:44.475 - that or do you want to? 00:47:45.490 --> 00:47:48.100 - Agree, disagree. 00:47:49.890 --> 00:47:55.110 - That does sound good. I uhm. I tend to check the general 00:47:55.110 --> 00:47:59.460 - things later than I guess I should because there's just 00:47:59.460 --> 00:48:05.115 - a lot of them over over the course of the day, so more 00:48:05.115 --> 00:48:06.855 - specific would be better. 00:48:10.050 --> 00:48:12.669 - Yeah, I agree that's what happens to me too. 00:48:13.200 --> 00:48:16.346 - So like if you're not getting a response in the channel. 00:48:16.990 --> 00:48:20.136 - Try to adjust the way that you're pinging in the channel 00:48:20.136 --> 00:48:23.568 - after you've given it, you know a few minutes for folks to 00:48:23.568 --> 00:48:27.362 - respond. Anne, look, I mean if it's something where you're 00:48:27.362 --> 00:48:30.642 - blocked in its urgent posted in stackoverflow, make it quick. 00:48:30.642 --> 00:48:34.250 - Obviously, try to find the solution is best you can, but 00:48:34.250 --> 00:48:37.530 - then posting in stack overflow quickly doesn't have to be 00:48:37.530 --> 00:48:40.482 - perfect. Throw it in the development channel and then 00:48:40.482 --> 00:48:44.090 - directly ping whoever just to make sure that you get a 00:48:44.090 --> 00:48:47.042 - response right away and there's some pretty interesting things 00:48:47.042 --> 00:48:51.634 - you can do I don't know if you guys have seen this yet, I'm 00:48:51.634 --> 00:48:53.274 - guessing most of you have. 00:48:53.990 --> 00:48:57.760 - You can make your pings important and you can also 00:48:57.760 --> 00:49:02.661 - remind people like in your one on one pings, uh, which is quite 00:49:02.661 --> 00:49:07.185 - an interesting thing. Uhm, so if you at the bottom where you're 00:49:07.185 --> 00:49:10.955 - typing underneath where you type your message, click on the 00:49:10.955 --> 00:49:14.725 - exclamation point. There is a standard which is the default 00:49:14.725 --> 00:49:19.920 - important. It will kind of like light up differently, but urgent 00:49:19.920 --> 00:49:24.222 - will actually send somebody have reminder every two minutes. 00:49:24.240 --> 00:49:28.910 - For the next 20 minutes, obviously you wanna use that 00:49:28.910 --> 00:49:31.990 - sparingly. But if you're stuck on something and you know that 00:49:31.990 --> 00:49:34.668 - I'm the one who supposed to be helping you with it, you are 00:49:34.668 --> 00:49:35.904 - welcome to use that with me. 00:49:36.640 --> 00:49:42.520 - An uhm, I guess my point would be like my job is to serve and 00:49:42.520 --> 00:49:45.264 - to help you. That is my number 00:49:45.264 --> 00:49:49.876 - one job. And I think that you know you can discuss with other 00:49:49.876 --> 00:49:52.836 - team members what they're comfortable with, but I want you 00:49:52.836 --> 00:49:56.980 - I want you to get the response that you need. You know the goal 00:49:56.980 --> 00:50:01.124 - isn't to be annoying toward each other, but I want I want you to 00:50:01.124 --> 00:50:04.380 - know like we're not in the office physically. At least most 00:50:04.380 --> 00:50:08.228 - of us or not. But we need to be able to communicate effectively 00:50:08.228 --> 00:50:11.484 - and collaborate effectively. So yeah, so there you go. Any other 00:50:11.484 --> 00:50:12.964 - comments on this? Feel free.