Hey. Congratulations. Regarding the dogfooding remark... We do that as well, and here's something you may find useful... I notice a lot more crap when I record

Hey. Congratulations. Regarding the dogfooding remark... We do that as well, and here's something you may find useful... I notice a lot more crap when I record presentation videos of the product and now I regularly record presentation videos as a revealing agent. This is similar to what we do with written material. I generally write the presentation of the product before we develop it, how the things will work. Same with SDKs and APIs. I'll write how the API is to be used and ask teammates 'Does that make sense ? Is this easy to use ?' and then write the code to make that SDK visible. I remember giving a laptop and library documentation to non coders and ask them to follow it and use the library to do something. If they could, developers were more likely to. Now that we have a product, it is insane the amount of crap that becomes visible once we're in presentation mode. Really ? Do I have to do all these things just to get that going ? Note the issue, continue the recording, find another issue, etc. My recordings are full of swear words because things that became invisible thanks to learned helplessness becoming visible. We do that as well for deployment. Once in a while, we'll deploy it with fresh eyes and fresh, clean, environnements notices all the crap of manual steps, a huge README file to follow and out of date, etc. Then we'll fix that.