• 1 Post
  • 8 Comments
Joined 4 months ago
cake
Cake day: July 6th, 2024

help-circle



  • ByteOnBikes@slrpnk.nettolinuxmemes@lemmy.worldIt do be like that
    link
    fedilink
    arrow-up
    15
    arrow-down
    1
    ·
    1 month ago

    I’m laughing way too hard at this.

    Honestly this is the best answer.

    Like, use the tools that work for your use case?

    I fucking hate macs but man using a video editor on windows was a pain back in the day. Where I would rather set up a server on Linux, than use whatever the hell windows servers operate.



  • as a chronic documentation reader, the best advice i can give is to document everything Anything that the user can and will potentially interact with, should be extensively documented, including syntax and behavior.

    I don’t know about that. I’ve read some terrible documentation that had everything under the sun. Right now in the library I’m using, the documentation has every available class, every single method, what it’s purpose.

    But how to actually use the damn thing? I have to look up blog posts and videos. I actually found someone’s website that had notes about various features that are better than the docs.

    There’s a delicate balance of signal vs noise.