 Pretty good. How's the conference so far? Yeah, good good. That is my second time in Dublin and let me tell you like someone doesn't want me to be here You know the first time I was joking with local people. It was during winter. It was like, oh, you call this a winter I'm from Canada. This is not winter and I caught a cold right after saying that like the day after I started to Cough and I'm like are you kidding me like I just like made a joke about the fact that it's not even cold for me and This time my luggage decided to stay in Canada. So I'm wearing the same clothes for the last four days It's not true. I went to do shopping. I changed my clothes, but still still anyway It's always a pleasure to be here. My name is Fred Fredrick Harper Why that thing is showing? I'm sorry We hide that Sorry about that I'm a director of developer relation of mindy and During the talk if you want to tweet about stuff take pictures of my ugly face Share good things bad things feedback questions that you don't want to ask in person or if you don't have the time to take a lot of questions Things that you disagree with feel free to do it on Twitter I spend way too much time there. My Twitter and goal is half Harper F. H. A. R. P. E. R. And I struggle saying my whole name. So today I'm gonna talk about developer documentation and the fact that it's your secret weapon I'm trying something new also this time if for whatever reasons you don't want to give me feedback In person you don't have time or you don't want to ask question Either you're too shy or you feel like you should not has this in public or it's really really mean feedback And you don't want to say it in my face. There's that link that I'm trying recently It's a ngl.link slash critic Harper. They didn't have have Harper available and you can send me anonymous question and Like anonymous question like there's no way for me to know Where it was sent or who sent it unless I pay like 60 bucks per month Which completely defeat the idea of like having something anonymous. So yeah, you can use that more than that P Yeah So in that note Okay, I need to bring the clicker we only have 45 minutes and I don't think I know people in the room But if you saw me in our other conferences, if you follow me online, you know, I talked a lot Actually, this is my job. I'm being paid to talk So 45 minutes for me is like not enough to talk about developer documentation So what I'm gonna try to do today is to give you as much of I'm any like many tips about developer documentation The importance of it how you can make a good developer documentation and how can it help your business or your company? Or your product to be or yourself to be more successful So the idea is like a bunch of tips and also guiding or guidelines to really give a better experience to your users so Let's start with a quote because every good presentation as a quote your developers documentation is an integral part of your product One cannot exist without the other I need to bring that And that person who said that is me. Yes, I'm quoting myself But joke aside one cannot exist without the other I'm a little bit Generating here like it's not totally true But still it's really part of like if you have you can have the best product out there You can have a wonderful product that solve all my problem or that helped me to be more productive Has a developer but if I go on your documentation and your documentation sucks, it's not good It's not interesting. It doesn't help me to do what I have to do or it's really difficult to understand or it's not a hub to date There's a chance. I don't like your product. There's a chance. I don't know how to use your product There's a chance that I will never use your product and just go see and use a competitor or use another product or under Software and other services out there. So documentation for developers for your product is critical. It's really really important So there is more than Like being successful overall. There is many opportunities that come with great documentation. Oh, yeah, that works so So the biggest thing is that Documentation is kind of like the foundation as I said of your product It is the one point of entry to your product that people will use so you want to Extinguish fire even before this start and your documentation will help you to do that So first thing first, you know when something is not working People will complain on Twitter people will try to contact customer support if you have great documentation you will minimize the number of people that will need to send you an email or contact customer support or Go in a forum or ask question on stack of her flow about your product if your documentation is well written You're gonna minimize the number of people that need support You're gonna minimize the number of customers that will complain about your product because we're all really quick specially developers We're really vocal when we don't like something on Twitter on different forums on slack on discord We are really good at that. I don't know for you me for you. I'm really really good about that I complain a lot of Twitter. Actually, I would say my Twitter is about 50 person cats and 49.9 percent shitpost. So that's basically what I do on Twitter and you know when something is not working people complain when people complain it means that they're not happy and Everybody is an influencer Not in there like oh, I'm an Instagram influencer influencers on the beach and taking pictures think kind of things But you know you always Influence something you all have a personal brand. So if I say Product X is not good. Maybe some of my follower will see that maybe some of my friend Maybe some of my co-worker will remember that the data want to use that product the product X and it will say You know what I'm never gonna try it Fred try it. He didn't like it But because I'm good or I'm better than other people It's just because we have a relation and if I'm complaining about something that may become the truth for those people So great documentation would minimize that. It's also gonna create a kind of like love effect So people will like better your product because they're gonna know how to use it That's gonna be faster for them to use it and on the contrary of people that are complaining They will become what I call virtual evangelists You know part of my job as a developer advocate is to help developer being successful And I do that by speaking at conferences creating contents online But the benefit was with having a community around your product with having people that love your product Is that at some point those people may start to think to talk about your product in a positive way? Either like I said just with people around them within their network or they're gonna write blog posts They're gonna create a video on YouTube's and is always hurt warming when people from the community does that It's always exciting when someone is vocal not for the negative stuff, but for the positive stuff That may save you money because again the time you spend to explain things to people the time Customers support insert the same exact question again It's not worth it. I actually it's worth it because for your customers but there is we for you to save money on that and a good things that I do example with the sales team is that if They ask often the same question. I have the sales team or the marketing team and my company like please Let me know and we're gonna update the documentation or we're gonna have a section So next time you won't have to explain this again. You can just send a link So documentation I see documentation as like a one link to rule them all like that should be the resource that That you send to people when they need help when they don't understand something or whether want to use your product Obviously also You know not everybody knows what you know and even not myself. I know what I know sometimes so you would be surprised how Often I go check my own documentation to know how to do something with my product because I just forget because there is many things Many tech stuff so that can be helpful for you too and by writing documentation yourself as developer I know I know most developers don't like to write documentation You just need to check source code to understand that we don't like to write documentation We don't like to write how things work, but as developer I think we're in the best place to create that documentation a great developer documentation for people and by doing that That's gonna help improve your communication skills Which is a soft skills that is not in most job posting But it's always something that hiring manager one even if you work in front of a computer Even if you are like I'm a developer like typical a little more introvert a little more shy type of developer You still need to communicate with people either with customers or with colleagues or with other stakeholders in the business and Because we work especially right now in a remote world you do a lot of text-based communication So writing documentation it seems far fetch, but that's gonna help you to be a better writer Which is gonna help you to be a better communicate communicator So it all start with the content It's documentation big surprise. Let's start with the content. So first thing first if You have a developer documentation and you don't have a search option for your documentation I want you to get out of that room and go ahead that search feature right now There is like stop stop listening to the talk go ahead the search feature There is nothing nothing more annoying then you go into documentation of a product a service And you don't exactly know what's the name of the feature and or the name of the classes or the object or whatever you need To order function you need to call, but you have an idea about what you want to do And there was no way for you to search that information So that is the first step even if your content is not good if you at least have a search bar That's gonna be useful for people. That's gonna be a great feature that you absolutely need to have One of the premises that I start when I need to write new documentation or update documentation or take the ownership of documentation Is that for documentation the details the devils in the details? Every little details count Every little things that you can make a little bit better every little typo that you can fix every little things that you Can just improving your documentation Is worth the time when it comes to the documentation because again Think about this as the foundation of your project or your product or your service Think about this as the first point of entry to your application The second part which is also important is how you organize the information Because you can have all the information again. You can even have the search bar But if it's difficult for me to see like a nice path to okay starting from the first part Which is probably like creating an account to the next step is probably I don't know Creating an api key because I'm gonna call it an api the next step is to try a kind of like hello world example If it's cater around in my documentation, it's not really clear that there is a true path from like Beginning to okay. Now I have a result. It may not be the result I want but I have something that is working It's not gonna be interesting for people. So let me show you an example What we've done in mindy so Again, you can go check the documentation. I think it's pretty good. I don't think it's perfect I think there is always a place to improve what we're doing But I'm pre-app where we are right now and if we check to the left Which is like the important part right now Is we have a lot of pages about a lot of things not that our product is complicated But we can do a lot of things with it. But if you notice this is gonna work No, it doesn't matter if you look at the top get started This is if you never use mindy. This is where I want you to start It's quite obvious get started. So where is it right at the top? So you have welcome to mindy. What is mindy set up your account make your first request And after that I'm going to do a platform tour because the first thing I want to do I don't know for you. I'm not the most patient people in her So when I want to try a service and application Whatever I want to try I want to try it and I want it to work right now Again, even if it's the simplest usage ever We have an api. I want to try the api I want to have an answer actually positive answer not an error from the api even if it's basic stuff So I know it's working and I know I know I know that I know how to use it So that is the first step But because it's in kind of like category of topics If you already use mindy, you don't care about getting started You can go to account and organization setting or you can go to the next step Oh The other thing I want you to do once you get started. I'm sweating like a pig It's super humid here. Actually, it's even cold this morning. What the hell, you know doubling this july Is it july harvest? I don't know Is it? Yeah, okay. I'm a little bit lost 20 20. Yeah, it's 20 20. Yeah Yeah, yeah, it's the third third years of 20 20 second year. Yeah Sorry about that. It's like 4am for me So the second thing you want to do I want you to do actually because I try to guide you in a process So once you get it started you create your account you get your api key You made your first call something real basic, but you make your first api api call Okay, now after you may want to set up your account How more information billing if you want to pay because we have a free offer But if you want to move to the next one, we don't force you but this but the other thing is that it's an api So you can use it whatever you want But what I really want you to do I'm not going to force you but what I really want you to do is to use her as decays And we're still building some so we're going to release like the java SDK and the ruby SDK Once I'm back from the conference But right now we have fight on the note and because it's the first thing I want you to do after Like I don't want you to code everything. I want to make your life easier And at the same time I want to make my life easier because if you use the SDK It's going to be way easier for me to help you if you have an issue Or uh to debug things or support you than if I have to support your own code So I'm going to put that right after and after that, you know, it's category and category and and and a lot of things So that was the closest pictures of John snow, which is not John snow that gave me the commercial copyright that I could use so one of the other Saying our premises that I write documentation when I write documentation or I update or I review documentation I need to think about John snow, you know nothing So write your documentation like if the person was going to read your documentation No, nothing about your product. No, nothing about the technology you're using You don't have to write everything, but at least you maybe you can point them to External resources like if you need for the SDK python SDK I need to do a pip install and maybe the person is not proficient in python or never use python I'm not going to rewrite how to use those tools But I may point to an external resources on the python documentation about how to do that But when it comes to my own software application, I'm going to write every little details Oh, you need to click next to go next button to go to the next window once you enter your username and login and password to connect and you need to Enter the api key in that field Why is that because again Not every developers has the same skills or expertise as you or has the previous person using your documentation So by doing that you're helping people that are new again to your technology or the technology you use But it's still going to be easy for someone who have a little more experience Or know your product to be able to just skip through The more interesting stuff for them. So always start with the promises that people just don't know what you're talking about So more details is better than not enough If you have pictures screenshot Images please please please put great quality one take great quality screenshot So the first thing is the text the text is the most important part of your documentation But I don't know the percentage but most people are visual. We are visual creature Put great screenshot put great images put high definition great quality There is nothing more depressing than like a well-written documentation Outside of not having the search bar to have like just crappy screenshot Even if I don't use them or I don't need them. It's just ugly And that gives the impression that you do not care about your documentation Or you do not care about the quality of what you put on your documentation And people are really quick to make one one plus one equal two Or three depending when you come from It's like yeah, okay, if you don't care about the documentation Maybe that person doesn't really care about their product. So it seems Obvious or it may seem stupid what I'm saying right now because I said a lot of stupid things in my life But it's really important because again, it's about the quality. It's about how people perceive Your documentation slash your product slash your service slash your company slash even yourself Try to also if you take screenshot try to focus on the information that the people need And when you take screenshot another important things that is really helping The accessibility or make your documentation accessible is that everything should be text based the screenshot Should be just another way to have the information that you already written So don't use the screenshot as something that is Needed absolutely needed for someone to use your product or to understand how to use your product So people who screen reader Will be able to still use people that are visual imper or people that have issue Like getting the content of your documentation people are really really slow Connection can still have access to the text based information And the images are just a plus another way to consume the information So try to put everything actually not try do it put everything text based and use the screenshot of picture just as an addition Not as a main part of the content in the sense that like if I remove the pictures I don't know how to use your product. I don't know how to use that feature to understand that feature that is super important But also as I said focus on the information. So, you know here um I have a part in Mindy platform where I can create an api key to access my api So real basic stuff you click on the button But still it's a whole page if you don't know the platform you're like, okay, there is a lot of button. There is a lot of links there So if I show that screenshot I'm like, okay. I'm not really pointing to what I want the user to do So what I'm gonna do uh first. Yeah, actually son of in dad that ugly black bar It's just ugly. It's just taking the focus like my eyes goes directly on the black bar That is hiding my api key and it's it is not where I want the user to focus So use great tools to take screenshot. There is a lot of tools out there Some freeze depending on the platform and you can do something a little bit nicer like this Actually, it's it's really simple. But is it nice like nobody's nobody's like. Yeah, that is so nice Yeah, oh, thank you. Thank you tough audience but That is I feel that is nicer, but that's just the first step the second step is like, okay I need you to create an api key. So yeah, I'm gonna put like a big red rectangle around it again Quite ugly if you want my taste so I can have something where I'm gonna Dim everything around the button now. Okay. I still have the focus now. I go right there. There is not that ugly red Rectangle around it. I can still see the rest of the screen But if you tell me your eyes didn't go right through creating a new api key when I change the slide Either you're a liar Or you're a liar your eyes went there. This is where I want you to have the focus and it's just a little bit nicer So again going back to the devils in the devil the devils is in the details when it comes to documentation Now I want you to go to the next app like next step would be even to okay. I don't need the full page Maybe I just want to show the section where I need to create the api key There are really need in the my documentation section about creating the api key to show all the page with all the option that will take the focus away That will people like me who have a really strong adhd Will focus on everything else except creating the api key or will focus on the creating the api key and oh, it's cruel It's cruel like a new option menu. So I'm going to click there. I'm going to forget what I'm going to do so by Taking a screenshot is more focus. That's going to help the user So a tool that I use I'm not getting paid to do that. I just really love it Actually, I paid to use that application. It's the paid one if you're using mac clean shot is really, really good But it's just one suggestion. I just really love it. He does everything that I've shown you you can take scrolling image video Whatever, but there's a lot of tools out there. Unfortunately, I'm not going to propose any more tools like in that talk Because I didn't try other tools since forever So I don't want to Like say oh use that tool is good. But anyway, you just check like screenshot tool You can even use like the basic tool that comes with your operating system But at the end of the day if you just go to take a better tool, there is a lot of open source one There is some that you have to pay really really cheaper and expensive And to give you the small option that really changed from like a boring All these screenshot to something nicer is with just the small options that I've shown you You know really able to focus hiding the information in the better way Focusing in a better way in the information and then you just go on google being whatever you use how to this stuff No, it's been forever And you search like you know screenshot tool for your OS. You're gonna find some One of the thing that people doesn't do Because once you wrote the documentation you're like, okay, I'm done. I'm tired like I already didn't want to write the documentation Yeah, no take the time to review your documentation and when I say review your documentation There's two things you can do first Read everything and do it step by step like if you were a new user So you have a page about creating in your account Don't do it because you know it read the documentation and create the new account Exactly how the documentation is written By doing that you're gonna see if you made a mistake if you had assumption because you know, you know your product The second thing is to try to get another person Someone that didn't write the documentation to review the documentation for you. That's going to be really helpful The other thing is that don't just review the text review the code And you would be surprised how often maybe it's just me but how often I look at the code and there's a way it looks good But like if I copy and paste so I don't write it down I don't look at it and write the same code. No, no I copy and paste select or if I have a copy button, I select the code I paste it in my hidey or whatever i'm using to run the code And I try it Because if I write it down, I may make mistakes. I may fix mistake now you really copy and paste the code and try it It's super important because again, uh, it's the basic on your documentation And you know what what I do I told you before what I do is like when I try a new product Even if I know the technology or even if I know the programming language use I'm still gonna copy and paste the code example of the documentation because first I'm lazy And secondly, I want to try it as fast as possible to see again if I can just have like the minimum Like return or whatever result that I'm looking for with the product So copy the code and try it and you're going to be surprised to see how little mistake we do many little mistakes we do It's like when we write code, you know, everything seems fine You try to write an application and like oh mistakes or the debugger give you like an error or something like that So it's the same thing with documentation I was like, why did I put that image? I have no idea. Yeah, I just remember now The second thing that is super important based on what I just said is how the small copy button Uh, it it seems stupid and it's really not complicated. You can there is like JavaScript library out there that does that that does does it for you or plugins Or depending what platform you use for your documentation. There is a lot of option to make it really easy Have that small copy button Because again lazy I want to go fast and Most of the time trying to select the code From documentation That does not always go well Sometimes you're going to get like the line number going to get the text before, you know, you know how it is It's not always Going super well and again. I want this to be fast. I want this to be easy Especially at the beginning when I'm evaluating your product. So had a copy button copy button I don't know how why I'm speaking kind of like in english accent If you want to have more information about documentation you want to balance ideas. This is the community you want to Go or be in write the docs. It's a conference, but it's also a slack community It's again a one link to rule them all write the docs.org There is a lot of resources on the website community. It's a lot of technical writers By profession but also a lot of people that have to deal with documentation And it's just like it's it's the place to be or to go for more information about documentation Great example of documentation Stripe really good one They do a good job with the api. They do a good job with uh overall documentation twilio is a really good one Get up as a great example with api documentation and just like like visual how to use the product documentation And uh, there's another one which is like really really good Oh come on this the last one really really good The second part is as important as the container So, you know you have your content But if the thing you use to display the content or to give the content to people is not good Uh, you're not going to have a great experience. So it needs to be fast. And again, you're like, hey, Fred Good job captain obvious Yeah, uh, you're going to say that to me, but like how how often you're going documentation is just slow It takes forever to load. So make it fast optimize the image. Uh, you can optimize Optimize the images without losing quality Like think about people that have slower connection because we're pretty lucky Many places in Europe many places in north america and different places in the world We have fast internet connection, but it's not always the case independent places when we have fast internet connection I don't know for you how many people are not from doblen But like if you travel just once or twice and you need hotel wi-fi, you know what i'm talking about So try to make those things fast Try to and i can't believe i need to say that in 2022 Make your documentation responsive And the funny thing is that i didn't know but there's developer that just like use their phone to check documentation for me I need a computer with like two monitors and like unless like without that i'm dying But people use their phone people even use their phone to code which i was like surprised and it's nice It's it's good. It's just not for me But i need to think about your users or i need to think about someone who just need to check something quick On their phone they don't have the laptop or there's an issue with the laptop whatever No, better the reasons your documentation should be able to be consumed in any type of platform with different viewport Make it easy to Manage made it easy to use so has a user Like i don't want to have create a username password to access your documentation I want to have like a nice menu with the nice organization So make that platform easy to use and make that platform also easy to maintain because i know we're developer we want to create things but When we think about stuff like documentation The goal of having documentation is to write the documentation to give the documentation to people The goal is not to maintain the container of the documentation So just reuse some things out there. There is a lot of great tools out there for the documentation Something that is nice too You can use get up or get a lab to have your documentation Make your documentation open source even if your product is not Anyway, documentation is public So put your documentation get up people will be able to submit pr That's going to be easier for you to follow up with different version Basically, it's file versioning. So that's going to be helpful for you And that's going to maybe have people help you with the documentation and it doesn't need to be on get up Like we use ring me It was not my choice But we use ring me and there is an option where people can suggest Modification of the documentation and we got people that we don't know that fix a typo for us Or had a little more information about something that we talked where clear But if they had that information it was not clear So try to empower your community to basically help you and help themself So there's a lot of great opportunity out there I usually suggest markdown as the main language because it's just easy to you just quite common I know on my python conference right now So, uh, but still I'm going to talk a little more about everything after but ring me It's a great platform if you're the only mostly the only one working at the documentation only one person Or you do minimum change once you wrote the big part of the documentation If you do too many modification too big of a modification It just goes a little bit crazy But they were working on something that's going to be closer to kind of like a get up PR type of process Body and the ear from what they told me It's a great platform still the chisorius. It's open source. It's really a good platform for you out there There's also read the docs, which is quite popular and you know any static site generator is good And uh, thank you for the water, but I'm not sweating because of that. I'm just like it's freaking humid python here RST restructured text Which are personally not a huge fine. I don't know if I should say that I prefer markdown Okay, you never heard me say that But you can use that with sphinct, which is quite a like the most popular Documentation generator out there if you put comments in your code. You're probably hard to know how to use rst So those are the tool that you can use to generate your documentation pretty easily Even with like, uh, uh, you know In your cicd pipeline or if your documentation is on get up or you release it as you can you want to generate the Documentation at the same time you can use get up action. So it's good for everything, but it's really well Working well with rst, especially as python developer. So in the end you know Documentation is important. So try to create great documentation Uh, and you may try to find The link between that image and what i'm just saying I really don't have no idea. Sometimes I put images. I should really put comments, uh, but I really don't know. Otherwise Oh, yeah, I didn't remember that's crazy I was going to say like you may you may I've listened to all the talk or keep yawning like mr. Dare was bored as as like was dying during my talk But that's a joke. Uh, it's fine if you were bored, but we're just tired Did you party last night? Yeah, nobody. Yeah, nobody knows who i'm talking to i'm talking to everybody who thinks that i'm not talking to So, uh, yeah, don't decide, uh, you know, you may you may finish the talk and say like oh fred Like everything you said was super obvious And i'm like, I agree. I agree. That's not the most like oh my god Like everything that fred said was like like mind blowing But now take your time take five minutes after my talk. Go check your documentation And see if you follow every tips that I said and let's talk again after to see if like everything I said was obvious uh, the other thing is like You know, uh, it's right now. It's a good time to build and to make your documentation better So after the conference try to invest a little bit of time like that or try to talk to the people that are responsible for your documentation to make it better Because it's really your superpower. As I said, it's the point of entry for your documentation It's the place where people get their first opinion after your marketing website about your product software or service So it's really your superpower if you do it well, but that can be your kryptonite if your documentation is not good Start writing Start writing yourself You're just going to get better. I know you may not like it But it's getting easier and easier the more you write the easier you get And maybe at some point you're even going to start to write blog posts You're even going to start to write more content to either help share your passion or your expertise Or just trying to help building your personal brand so One of the other things you can do if you don't want to do everything I just said right now Maybe hire Technical writer at your company or try to hire maybe a developer advocate Which part of the job will be to write the documentation? But don't think about the documentation has an afterthought. It's really it really should be part of your development process So on that note, my name is fred I know I speak way too much. I spoke way too much like usually So, uh, we still have one minute for a question. But if we don't have time Grab me in the conference Break room or whatever. Uh, send me an email fred at uh mindy.com I'm on twitter f rpr If you want to chat more about documentation and any other topic or even mind total illness You can book a coffee chat if we don't have time at conference at fred.dev slash coffee 30 minutes call on zoom For free like I'm just like sharing with people So any comment, uh Question and salt Awesome, thank you So I'm also a strong believer in documentation, but I also wanted to talk about the or ask about the elephant in the room And it takes a lot of of course effort to maintain it And to be honest, like if I was only doing this all day, I would probably shoot myself because it's not really like a It's a thankless job. So what would be your answer to? um Like api documentation or even ui documentation gets outdated very quickly So how to keep it up to date and not go crazy. What would be your answer to that? uh Yeah, it's sort of hard not to go crazy. No, but uh, uh, I would say I would say try to find a right middle So that may not be the perfect solution, but maybe try to generate your documentation from your api So try to document your code. So it's still writing stuff It won't be a step by step, but at least you're going to have like basic Like information about how to use the api. So I may not show you like how to create the api key on the web page things But at least I'm going to know how to Like use the api So I would say like that's the basic things you can do try to Merge like coding put a little bit of like information in your code comments and like generate the documentation Again using rst and spanks to generate the documentation. So again, not going to be perfect But it's going to be a good first step To help you and not like go crazy and I understand like I like writing blog posts Documentation is really not the things I like to write the most and it's why on my job The first person I hire in my team was a technical writer. So that could be another good solution I hire a technical writer Or use a freelance technical writer Which is going to help you to write the documentation at the beginning and after that you just have to maintain it But again, if like put it open source, so even like your community can help you maintain that thing So try to outsource Things That may help you Thanks for the question Hey friend, thanks for the solid talk was good You seem to have thought way more about documentation than I so I wonder What's your opinion on because most of your talk is about like kind of prose documentation high level stuff But there's also like reference docs for like api and whatnot. What do you think this is right balance? How do you know when you're done with one and you can focus on the other? How do you know it's good enough? Sorry, I missed the last part. How do you know it's it's good enough? How do you know whether you want to focus more on the reference documentation compared to the pros like the high level docs? When do you know you're done? I would say You know, it's good enough when Most people can use your product without asking you question I would say it's it's like at that point is good enough Or don't ask you basic question like if they have like a specific use case Like okay. Yeah, I'm not gonna document any like specific little use case But like if I would say 80 of the people or people can do 80 of the stuff I would say it's good enough But it's really like I just put this out of my mind right now. It's there is no statistic. No research about that It's just in my head. I'm like I would say it's it's good enough because again The devil's in the devil devil is in the details But at the same time like if you always try to improve the documentation there is no n So you need to find the right amount. I don't know if that answered the question. Yeah, okay. Awesome 10 We have three minutes. I also have to check if we have any remote questions Okay Thank you for the thank you for the presentation. I loved it So I had a question you mentioned mostly writing the documentation for the code you own you build Sometimes when you're working in in the larger team that means that it's a collaborative effort So I would like to hear any thoughts, tips, recommendations, dos and don'ts about collaboratively working on documentation Yeah, uh, I would say okay. Is there anyone working at read me here? Okay, don't use read me Because we had a lot of problems like it's a great platform But not if you do a lot of modification and you collaborate with a lot of people again They're coming I complained today and I had a meeting with their p.m. Whatever like they're gonna improve this stuff right now it's not there yet use a tool that make it easy and Just don't think about technical people, you know one of the things at the beginning when I arrived at mindy I was like, yeah, we're gonna move things and mark down putting on get up That's gonna be easier for me to review we're gonna be able to track better We're gonna be less dependent on read me and it was perfect for me and my technical writer But the less technical people that wanted to help with the documentation We're not about to Like use the process really easily and they they were thinking like you know reviewing pr and get up But there is a lot of text and it's not code. It's it can be difficult. So try to use a tool That's gonna make your life easier that is easy to use Technical or not technical people because the goal is not to be a developer when you do that the goal is to be a writer The second thing is like just just define the priorities Because there's always a lot of things to do. So what is the most important? What what will have the biggest impact? or the biggest negative impact if we have it or if we don't have it in the documentation and Try to have people review stuff because especially if you write documentation about your own stuff The things you build it's clearing your mind You may think it's clear when you write it down But try to have someone who didn't work on a product or that specific part of the product to review it That would be the quick like three four tips that I would have for you Yeah, try also maybe maybe the last thing also try to to without having like Forget how you name that but like a convention about a convention about like the tone and voice of the developer documentation Just try to have some basics about like how you should write You know like hey, we're gonna write in the terms of like Mindy has mindy not has like Fred who is writing the documentation Or we're gonna be like professional and make no jokes like just try to Have like fire six like basic like how documentation should be written So if there is multiple people different people writing the documentation doesn't seem like there is multiple people writing the documentation It seems like it's one person write the documentation because it's always written about the same way Perfect. Well, thank you. Thank you very much Thank you Thanks everyone have a great rest of the conference and By the way tonight for those of you that don't have to kept for the social event because it's it's full I'm gonna go to like Brewery 10 minutes from here. So just ping me on twitter If you want to join so i'm not drinking alone like an alcoholic. So yeah, thanks everyone