| Topic | Presenter | Summary | Duration | Tags | Quiz | Captions |
| ----------------------------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | -------- |
| What makes a good piece of documentation for StackOverflow and Nuclino? | Chris Black | In this brief video, Chris outlines what and how to document in our StackOverflow and in the Wiki. | 18:14 | #Onboarding, #ClarityTraining, #Documentation, #Stackoverflow, #Nuclino, #ClarityWiki; #BestPractices | | |00:00:01.110 --> 00:00:05.574 - So basically what I'm gonna cover first is just how to write 00:00:05.574 --> 00:00:09.294 - a piece of documentation for stackoverflow or in the wiki 00:00:09.294 --> 00:00:13.386 - i'ma show some great examples that I found and some bad 00:00:13.386 --> 00:00:17.850 - examples that I found and those bad examples are going to be 00:00:17.850 --> 00:00:21.942 - mine, so so there's a couple ways in to write documentation. 00:00:21.942 --> 00:00:26.034 - I want to say that any documentation is better than no 00:00:26.034 --> 00:00:29.754 - documentation, so it's not like there's this like gold standard 00:00:29.754 --> 00:00:33.102 - of like if you don't do documentation this way. 00:00:33.120 --> 00:00:39.028 - Then we don't want it kind of thing. It's like if you can if 00:00:39.028 --> 00:00:43.248 - you just kick out a piece of documentation please like, 00:00:43.248 --> 00:00:47.890 - please do it. So I'm going to cover stackoverflow first since 00:00:47.890 --> 00:00:49.578 - I have it open. 00:00:49.590 --> 00:00:53.106 - And uh, this ones by Heather. Um, it has a nice title. 00:00:53.106 --> 00:00:56.329 - Basically, is what you're looking for. and I know this is 00:00:56.329 --> 00:01:00.431 - kind of like a no brainer and you guys are going to be like 00:01:00.431 --> 00:01:03.654 - Alright we know how to write a stackoverflow thing but just 00:01:03.654 --> 00:01:07.463 - bear with me for a second because I want to show you what 00:01:07.463 --> 00:01:10.979 - a good example looks like and what a poor example looks like. 00:01:10.979 --> 00:01:14.495 - So Heather put in a nice title basically and then added some 00:01:14.495 --> 00:01:18.304 - nice tasks. So Heather put nice title at the top of this and 00:01:18.304 --> 00:01:20.355 - then also put some nice tags in 00:01:20.355 --> 00:01:24.912 - here so. This will kind of, you know, uh, help you be able to 00:01:24.912 --> 00:01:27.520 - search for anything within stackoverflow, so she puts 00:01:27.520 --> 00:01:30.780 - inappropriate ones in your like DNN Orvault Core module or 00:01:30.780 --> 00:01:34.692 - something like that. Just to kind of tagging it out. And then 00:01:34.692 --> 00:01:37.952 - she answered her own question, which is definitely more than 00:01:37.952 --> 00:01:41.538 - acceptable to do so. If you find something that's like difficult 00:01:41.538 --> 00:01:45.776 - to do and you already know the answer to it, you're like man, 00:01:45.776 --> 00:01:49.036 - this really needs to be documented. Just answer your own 00:01:49.036 --> 00:01:50.992 - question with as much detail as 00:01:50.992 --> 00:01:54.450 - possible. And then kind of walking through the body 00:01:54.450 --> 00:01:58.300 - response here is, you know she gives nice explanation, gives 00:01:58.300 --> 00:02:02.535 - you know some code, examples, pictures of what's going on, and 00:02:02.535 --> 00:02:06.770 - then just keeps walking through the entire thing here and then. 00:02:06.770 --> 00:02:10.620 - You know there's some other supporting answers as well. And 00:02:10.620 --> 00:02:15.240 - feel free to comment as much as possible as well as much 00:02:15.240 --> 00:02:19.475 - information as possible is good, but this is basically what you 00:02:19.475 --> 00:02:21.400 - want to do, just pictures. 00:02:21.450 --> 00:02:26.425 - You're amazing. Uh, so yeah, basically just a as much, uh, 00:02:26.425 --> 00:02:30.440 - you know pictures are really nice just to kind of help 00:02:30.440 --> 00:02:34.455 - visualize what the issue is and highlighting like this is also 00:02:34.455 --> 00:02:37.375 - really amazing. Just highlighting and what the issue 00:02:37.375 --> 00:02:41.755 - is, and then it just as much detail as possible, like Heather 00:02:41.755 --> 00:02:46.135 - put in here. Now, something that I did is just, you know. 00:02:46.180 --> 00:02:51.040 - Yeah, what picture tool do you use Heather to capture 00:02:51.040 --> 00:02:52.498 - those awesome pictures? 00:02:54.510 --> 00:02:57.316 - So if 00:02:57.316 --> 00:03:03.318 - it's. OK, hold on, switch it to Heather screen. She needs to 00:03:03.318 --> 00:03:05.408 - show everyone all over stuff. 00:03:05.420 --> 00:03:09.875 - No, no, no. You can stay here. It's not a uh, OK so on this 00:03:09.875 --> 00:03:13.142 - image right here where it's just like there's no markup needed 00:03:13.142 --> 00:03:16.409 - like no squares or circles or anything. It's very clear that 00:03:16.409 --> 00:03:19.379 - this elements highlighted and then in the inspector you can 00:03:19.379 --> 00:03:22.943 - see it's like highlighted over there so that I just use. It's 00:03:22.943 --> 00:03:26.507 - like a shift window S shift window apps will allow you to 00:03:26.507 --> 00:03:30.368 - take a screenshot of your screen and just like any size you kind 00:03:30.368 --> 00:03:33.932 - of like. Drag it and then it just copied to your clipboard. 00:03:33.932 --> 00:03:37.496 - So then you can just paste it anywhere so it's super fast. 00:03:38.260 --> 00:03:41.824 - It's a new version of the windows snipping tool. OK, yeah, 00:03:41.824 --> 00:03:45.388 - something that needs markup then I just use the snipping tool 00:03:45.388 --> 00:03:49.276 - because it's faster than doing that and then saving it and then 00:03:49.276 --> 00:03:53.488 - opening it and paint. So if I need markup then I use the 00:03:53.488 --> 00:03:57.760 - snipping tool. And if you have an Apple, its command shift four 00:03:57.760 --> 00:04:01.504 - and it has its own markup and everything that you can add to 00:04:01.504 --> 00:04:06.553 - it. And uh, and all of this is like very much like markdown in 00:04:06.553 --> 00:04:10.084 - your comments as well. And it even like Stackoverflow is just 00:04:10.084 --> 00:04:14.257 - kind of like there almost as helpful as get that kind of, you 00:04:14.257 --> 00:04:17.788 - know, guide you and help you insert images and stuff like 00:04:17.788 --> 00:04:20.677 - that, so it's pretty. It's pretty straightforward as well. 00:04:20.677 --> 00:04:25.250 - And then. Jumping over to the piece of content I made is 00:04:25.250 --> 00:04:30.260 - obviously not as helpful at all. Um, but so I I I had it. Nice 00:04:30.260 --> 00:04:34.936 - title here. Uh, but you know, I had a couple of tags and then 00:04:34.936 --> 00:04:38.610 - you know, here's my question. And then basically I could have 00:04:38.610 --> 00:04:42.618 - taken the time and added more pictures in here and showed what 00:04:42.618 --> 00:04:47.294 - you know. What is the outcome is like and stuff like that which I 00:04:47.294 --> 00:04:49.298 - could definitely need to go back 00:04:49.298 --> 00:04:52.563 - and revisit. But like I said, any documentation is better than 00:04:52.563 --> 00:04:55.610 - no documentation. So even if you're in a pension, just need 00:04:55.610 --> 00:04:58.380 - to add something to the stack overflow really quickly or 00:04:58.380 --> 00:05:01.150 - anything like that, and you know the answer to it. 00:05:01.760 --> 00:05:04.928 - Adding anything is better than adding nothing, so, uh, you know 00:05:04.928 --> 00:05:08.384 - at the end of the day, if you know you get something. 00:05:09.040 --> 00:05:12.692 - That's you know, like I said, that's better than nothing, so 00:05:12.692 --> 00:05:16.676 - just make sure that we're doing that there. And in the same 00:05:16.676 --> 00:05:21.324 - thing I'm going to jump over to nucla know now just kind of the 00:05:21.324 --> 00:05:25.972 - same area. But you know, I just want to make sure as well that 00:05:25.972 --> 00:05:29.624 - setting the expectation of if you have any kind of question 00:05:29.624 --> 00:05:32.612 - that's like software related or anything DNN related, or 00:05:32.612 --> 00:05:35.268 - anything technically related, please make a stackoverflow post 00:05:35.268 --> 00:05:38.920 - about it, because as we all know, Microsoft team does not 00:05:38.920 --> 00:05:41.654 - the. Best searchable application, and that's exactly 00:05:41.654 --> 00:05:45.594 - what stackoverflow is. You know we all use stackoverflow. I 00:05:45.594 --> 00:05:50.716 - don't know thousands of times a day I'm sure so just make sure 00:05:50.716 --> 00:05:55.444 - that if you guys are asking questions, put it in a stack 00:05:55.444 --> 00:06:00.566 - overflow post and Post that link in teams and then if anybody is 00:06:00.566 --> 00:06:03.324 - answering those questions, please answer in Stackoverflow 00:06:03.324 --> 00:06:08.052 - so we have everything documented so we can just search our own 00:06:08.052 --> 00:06:10.022 - stack overflow for own, you 00:06:10.022 --> 00:06:13.478 - know. Anecdotal problems essentially on our software and 00:06:13.478 --> 00:06:17.718 - RDN instances and stuff like that. Anything that's going to 00:06:17.718 --> 00:06:19.838 - be available to us there. 00:06:20.640 --> 00:06:22.360 - And then jumping over 2. 00:06:22.970 --> 00:06:23.610 - Uh. 00:06:24.990 --> 00:06:28.202 - You clean, oh just kind of zoom in here as well. 00:06:29.540 --> 00:06:34.584 - So here's an article where it's like how to and it's hashing and 00:06:34.584 --> 00:06:39.410 - salting passwords. There's a one cent or two. Sentence is an. It 00:06:39.410 --> 00:06:43.304 - just says that we currently past the data through Microsoft code 00:06:43.304 --> 00:06:47.198 - to do both. Hashing, insulting flashing is done so you can't 00:06:47.198 --> 00:06:51.446 - run a decrypter and reverse it to get the original password to 00:06:51.446 --> 00:06:54.278 - run through Microsoft's identity libraries to ensure the 00:06:54.278 --> 00:06:57.464 - compliance. And while this isn't necessarily untrue, there's just 00:06:57.464 --> 00:07:01.712 - not how to how to hash a password, how to salt the 00:07:01.712 --> 00:07:05.960 - password right? It's just like just two sentence is kind of on 00:07:05.960 --> 00:07:09.390 - the topic. And so if you're going to write a piece of 00:07:09.390 --> 00:07:12.642 - documentation, I would say at least try to add a little bit 00:07:12.642 --> 00:07:15.623 - more detail of how to do something or anything like that, 00:07:15.623 --> 00:07:19.146 - and then I'll pull up a really nice when I found as well. 00:07:19.190 --> 00:07:21.642 - Chris HubSpot integration bit 00:07:21.642 --> 00:07:26.480 - uhm so. There's a, you know. It's really neatly outlined, so 00:07:26.480 --> 00:07:30.440 - you have nice headers of each thing, and this is all marked 00:07:30.440 --> 00:07:34.400 - down again, so you can use all markdown syntax here with making 00:07:34.400 --> 00:07:38.360 - these links or anything like that, which is just put it in 00:07:38.360 --> 00:07:41.660 - array brackets or hard brackets and then put you know. 00:07:41.660 --> 00:07:45.134 - Parentheses around them. So basically you could do something 00:07:45.134 --> 00:07:50.152 - like if you want to make a link, you say your text here 00:07:50.152 --> 00:07:53.509 - basically. And then you would just put your link in 00:07:53.509 --> 00:07:54.151 - here, right? 00:07:55.320 --> 00:07:57.108 - And that should make a link. 00:07:58.250 --> 00:08:01.058 - Or not, nothing goes right whenever you're doing it 00:08:01.058 --> 00:08:03.554 - live. But yeah, it automatically just did it 00:08:03.554 --> 00:08:07.610 - for me. I would just like get a URL and I would just 00:08:07.610 --> 00:08:11.354 - paste it and then it would change it to a nice little 00:08:11.354 --> 00:08:12.602 - name on its own. 00:08:14.040 --> 00:08:17.056 - So it's probably a server WWW or HTTP status in the whole URL 00:08:17.056 --> 00:08:19.376 - from whatever whatever these links are. And then I just 00:08:19.376 --> 00:08:22.624 - pasted it and it just use like us. The title of the page, or 00:08:22.624 --> 00:08:24.944 - so. I'm not sure you could do stack overflow, something, 00:08:24.944 --> 00:08:27.496 - something, something. I'm sure it would show up is just like 00:08:27.496 --> 00:08:35.010 - stackoverflow. Now there you go. Well yeah, just paste it. OK 00:08:35.010 --> 00:08:41.240 - so. Dance into no nothing, just paste it just does it for you, 00:08:41.240 --> 00:08:45.890 - yeah? So, uh, that's even better. Uh, so, uh? Just kind of 00:08:45.890 --> 00:08:49.690 - scrolling through this one. It's laid out really nicely, so 00:08:49.690 --> 00:08:53.870 - everything is really nice to find. You have a nice title. 00:08:53.870 --> 00:08:55.010 - Nice little subsection. 00:08:55.020 --> 00:08:59.110 - Testing steps, which is really nice. Pictures again, you know, 00:08:59.110 --> 00:09:02.791 - just kind of sticking pictures as appropriately as possible, 00:09:02.791 --> 00:09:07.290 - just to kind of give and visualization of the error, the 00:09:07.290 --> 00:09:12.198 - problem or the resolution. Or in this case the testing step and 00:09:12.198 --> 00:09:17.106 - kind of putting the API keys here. It looks like Heather put 00:09:17.106 --> 00:09:22.014 - in API key here, which is which is really nice, appreciate that. 00:09:22.720 --> 00:09:26.430 - And just kind of scrolling through this again, you know 00:09:26.430 --> 00:09:29.398 - there's there's links to everything, there's examples of 00:09:29.398 --> 00:09:33.850 - you know what responses should look like or what the git or 00:09:33.850 --> 00:09:37.931 - post requests should look like, so we're kind of familiar with 00:09:37.931 --> 00:09:42.012 - the syntax, right? In any kind of angular routing, or, you 00:09:42.012 --> 00:09:46.093 - know, kind of similar to it doesn't have hard brackets, but 00:09:46.093 --> 00:09:49.803 - kind of similar to see routing for hitting different API 00:09:49.803 --> 00:09:54.824 - endpoints. Um, nice little highlights over the place up and 00:09:54.824 --> 00:10:00.752 - all that, but there's there's a couple of great ones in here as 00:10:00.752 --> 00:10:05.296 - well. So again, this is in stuff like this is really nice, uh, 00:10:05.296 --> 00:10:09.352 - where it's just? A lot of information, but for a lot of 00:10:09.352 --> 00:10:13.408 - information see how this is not, you know, super broken out and 00:10:13.408 --> 00:10:17.802 - this is, you know, brought over from share point. So it was, you 00:10:17.802 --> 00:10:21.520 - know, nice, nicely kind of configured and had a nice layout 00:10:21.520 --> 00:10:25.238 - before we brought it over. But just during that you know 00:10:25.238 --> 00:10:29.632 - integration that just kind of showed it to a body of text. But 00:10:29.632 --> 00:10:33.012 - if somebody was to actually write this and it wasn't 00:10:33.012 --> 00:10:36.697 - integration. It's kind of just like a big body of boring text 00:10:36.697 --> 00:10:40.261 - where you're like, Oh man, there's a lot going on here and 00:10:40.261 --> 00:10:43.528 - I can't really, you know, consume it, you know, just the 00:10:43.528 --> 00:10:46.201 - way that it's written out something like this HubSpot 00:10:46.201 --> 00:10:49.765 - integration is a lot easier to kind of, just consume just from 00:10:49.765 --> 00:10:50.656 - thinking perspective just 00:10:50.656 --> 00:10:54.560 - because it's. Things you will need. OK, cool, I know exactly 00:10:54.560 --> 00:10:58.280 - what I'm gonna need. Get request post request. You know all these 00:10:58.280 --> 00:11:01.690 - all these good stuff? All this good stuff here. So definitely 00:11:01.690 --> 00:11:05.100 - try to do something like this. Heather is the absolute wizard 00:11:05.100 --> 00:11:08.510 - at documentation. Has all of these examples are hers? Let me 00:11:08.510 --> 00:11:12.230 - see if I can find something that's not heathers so I can 00:11:12.230 --> 00:11:13.780 - give somebody else praise here. 00:11:14.480 --> 00:11:17.624 - Let's go check out James is markdown skills. You zoom in on 00:11:17.624 --> 00:11:19.196 - this little bit of as well. 00:11:19.940 --> 00:11:25.162 - So uhm, and this is just another set configs repo, uh? We kind of 00:11:25.162 --> 00:11:29.638 - saw. I kind of went here pretty quickly, but just in the 00:11:29.638 --> 00:11:32.995 - underscore documentation and that should pop up first just 00:11:32.995 --> 00:11:35.979 - from filtering alphabetically. Just that underscored will pop 00:11:35.979 --> 00:11:40.828 - up at the top of your folder list. And this is the full 00:11:40.828 --> 00:11:43.812 - environment. Install script markdown file that James wrote, 00:11:43.812 --> 00:11:48.288 - and James was very meticulous in this document. And kind of just 00:11:48.288 --> 00:11:50.153 - went over every single aspect. 00:11:50.200 --> 00:11:55.530 - Of, you know, uh, not only the uh, the install bit, but the 00:11:55.530 --> 00:11:59.630 - preference is that you know most people use as well. 00:11:59.630 --> 00:12:03.158 - So it literally goes from anything from installing Windows 00:12:03.158 --> 00:12:07.470 - 10 just a straight windows install on a server or a 00:12:07.470 --> 00:12:11.986 - computer. And, uh, just go breaks down every single step 00:12:11.986 --> 00:12:15.826 - from the windows settings all the way to installing night 00:12:15.826 --> 00:12:19.666 - night to install several programs all at the same time. 00:12:19.666 --> 00:12:24.658 - So let's see if I can just Scroll down a little bit more. 00:12:24.658 --> 00:12:29.266 - This is the server manager stuff here. Yeah, so and James puts 00:12:29.266 --> 00:12:34.642 - links to all this stuff in the markdown as well, so you can see 00:12:34.642 --> 00:12:38.482 - that it's nice little sections broken out with nice little 00:12:38.482 --> 00:12:42.480 - titles. You know basically what he's running through and why you 00:12:42.480 --> 00:12:47.790 - need to do it, and a link to the website to get the software. Or 00:12:47.790 --> 00:12:49.206 - you know, whatever the. 00:12:49.230 --> 00:12:53.058 - The program could be right or like a linked to some other 00:12:53.058 --> 00:12:55.929 - documentation that you could possibly need, and then it's 00:12:55.929 --> 00:12:59.757 - just all structured out. So this is really easy to consume. You 00:12:59.757 --> 00:13:03.904 - get a nice picture here. On the left you get nice little steps 00:13:03.904 --> 00:13:07.413 - here on the right, so Azure walking through it, you can't 00:13:07.413 --> 00:13:10.922 - really get lost. It's almost impossible to get lost in this 00:13:10.922 --> 00:13:14.112 - documentation just because all the steps are broken out and 00:13:14.112 --> 00:13:17.302 - you're literally going through this sub steps and then looking 00:13:17.302 --> 00:13:19.216 - at pictures of exactly what to 00:13:19.216 --> 00:13:25.021 - click on. And you know, kind of I want to revert back as well to 00:13:25.021 --> 00:13:29.785 - say that not everything has to be this detailed. It would be 00:13:29.785 --> 00:13:33.755 - amazing if everything was, but any documentation is better than 00:13:33.755 --> 00:13:37.725 - no documentation. So even if you don't contribute something this 00:13:37.725 --> 00:13:40.901 - detailed just contribute something. It's a lot better 00:13:40.901 --> 00:13:45.268 - than just hearing the same question five times, and I think 00:13:45.268 --> 00:13:50.032 - if anybody is guilty I'm I'm so guilty of asking James. Probably 00:13:50.032 --> 00:13:51.223 - the same question. 00:13:51.270 --> 00:13:55.146 - 5 five times over the couple years I've worked with them so. 00:13:57.740 --> 00:14:02.667 - And you know, in James, Credit is like you should just go check 00:14:02.667 --> 00:14:07.215 - the full installer guide that I spent several couple hours on at 00:14:07.215 --> 00:14:11.440 - least. So does anybody have any questions on documentation? So 00:14:11.440 --> 00:14:15.860 - far? I just wanted to add one thing, if you don't mind, I'll 00:14:15.860 --> 00:14:19.260 - keep it quick here. Just a friendly reminder that their 00:14:19.260 --> 00:14:22.320 - Easter eggs for dealing stackoverflow an there I can 00:14:22.320 --> 00:14:26.740 - tell you for sure there are more Easter eggs at 500 points on 00:14:26.740 --> 00:14:30.140 - stack overflow, so if you literally want to go document 00:14:30.140 --> 00:14:33.880 - things, I mean, as long as they're like real things, just 00:14:33.880 --> 00:14:36.600 - go. Documentum into stackoverflow. Is you asking a 00:14:36.600 --> 00:14:37.960 - question and answering it? 00:14:38.640 --> 00:14:43.151 - And um, ideally you know you want to see if somebody else is 00:14:43.151 --> 00:14:48.009 - already put it out there an if they have, you can add to it 00:14:48.009 --> 00:14:51.826 - too. You can answer questions, add questions, get you know, get 00:14:51.826 --> 00:14:55.643 - marked as having the right answers. Once you get to 500 00:14:55.643 --> 00:14:59.460 - points in Stackoverflow, there's a Easter egg there, and what I 00:14:59.460 --> 00:15:00.848 - mean by that is. 00:15:00.850 --> 00:15:04.963 - Uh, directly correlated to things that we all like. 00:15:05.790 --> 00:15:08.838 - It rises honey. 00:15:08.870 --> 00:15:14.505 - Um? Then there's the Sonny and Cher albums. 00:15:14.510 --> 00:15:18.058 - And then they get. 00:15:18.060 --> 00:15:21.770 - And then there's also, there's definitely another one at 1000, 00:15:21.770 --> 00:15:26.222 - and the same thing goes for nucla, know, uh, once you have 00:15:26.222 --> 00:15:30.303 - enough good articles, you know pieces of content in new clean. 00:15:30.303 --> 00:15:34.384 - Oh, there's some. Some are really good just by giving the 00:15:34.384 --> 00:15:37.352 - answer to something that's pretty challenging. I know 00:15:37.352 --> 00:15:41.804 - there's one in particular that we have that was pretty dry, but 00:15:41.804 --> 00:15:45.885 - it gave all the information needed to deal with a major 00:15:45.885 --> 00:15:48.482 - issue with DNN sharp compatibility with Seth. 00:15:48.550 --> 00:15:52.216 - And, uh, it was pretty concise, but it was the response from a 00:15:52.216 --> 00:15:53.908 - question that we asked to their 00:15:53.908 --> 00:15:57.911 - support team. And so, putting that out there, save some time 00:15:57.911 --> 00:16:02.295 - from people. Are going and finding that so anyway back over 00:16:02.295 --> 00:16:03.360 - the Chris yeah. 00:16:03.870 --> 00:16:05.950 - Well, I was going to. 00:16:06.490 --> 00:16:10.450 - So what, uhm? How would one identify something that's worth 00:16:10.450 --> 00:16:14.806 - making a, uh, a post about or some documentation about? Not 00:16:14.806 --> 00:16:19.558 - every little thing I would say. The thing that you found this 00:16:19.558 --> 00:16:23.518 - morning that you posted the development channel could be in 00:16:23.518 --> 00:16:25.894 - stack for sure. Or any anything 00:16:25.894 --> 00:16:29.642 - technically related. And I personally would say if you have 00:16:29.642 --> 00:16:33.074 - any question at all of whether or not you think it was helpful 00:16:33.074 --> 00:16:36.506 - or it was even just a question that you had, or you think 00:16:36.506 --> 00:16:38.882 - someone else might have, just put it out there. 00:16:39.520 --> 00:16:43.012 - Like I my personal opinion, I don't want you guys to like 00:16:43.012 --> 00:16:45.922 - spend your entire day writing documentation, but I think most 00:16:45.922 --> 00:16:47.668 - of these things are pretty cool 00:16:47.668 --> 00:16:51.564 - because like. You know other people on the team genuinely 00:16:51.564 --> 00:16:54.994 - will benefit from them, and they're gonna be like, yeah, 00:16:54.994 --> 00:16:59.453 - that was Heather, yes, she's the one who did all that. Wo your 00:16:59.453 --> 00:17:01.511 - Heather. Oh my gosh, good job 00:17:01.511 --> 00:17:03.939 - either. Like you said. 00:17:04.040 --> 00:17:08.288 - You're the Heather um or and Jesse. I know you've got some 00:17:08.288 --> 00:17:12.182 - that's been really, really helpful so, but I mean, even if 00:17:12.182 --> 00:17:16.784 - it's really simple, uhm, I think it can be worth it, and maybe 00:17:16.784 --> 00:17:21.740 - you just make a little To Do List. And like you know you can 00:17:21.740 --> 00:17:26.696 - add some documentation like once a week or at the end of the day. 00:17:26.700 --> 00:17:30.249 - And if you end up putting a lot of time into it because 00:17:30.249 --> 00:17:33.798 - you have a lot to share, you can get approval to make that 00:17:33.798 --> 00:17:36.528 - internal billable. Just let your manager know Ann, I mean, 00:17:36.528 --> 00:17:39.531 - as long as it's not like how to do underwater basket 00:17:39.531 --> 00:17:41.988 - weaving or something off topic, then all approve it. 00:17:43.150 --> 00:17:46.330 - I would say for the people that are more experienced and like 00:17:46.330 --> 00:17:49.245 - have like more tribal knowledge. The newer people then like if 00:17:49.245 --> 00:17:52.425 - you get questions a lot from like anyone like put that in 00:17:52.425 --> 00:17:55.340 - there. 'cause like if you've been asked, you know like many 00:17:55.340 --> 00:17:59.050 - times I'm sure people that are new or it's gonna ask you or the 00:17:59.050 --> 00:18:01.965 - other person or something like that. So if you get asked 00:18:01.965 --> 00:18:05.410 - questions a lot that you always have to help out with and that 00:18:05.410 --> 00:18:08.590 - could be something in there. Or if you're asking questions a lot 00:18:08.590 --> 00:18:11.240 - about something that can go in there too. Just anything. 00:18:12.520 --> 00:18:14.728 - Totally agree, awesome.