• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: December 28th, 2023

help-circle

  • Yeah ! Except in the dev/code realm… They seem very aggressive to each other, specially if you whisper something like: Rust is safer than C !

    I don’t really get it, but I find It very pleasant to read when passionate people write a whole essay I don’t even understand 1/10 of what they are writing… However, there seems some heated negativity in that community !





  • I think what happens to me is that I completely lack discipline about structure and will often decide to re-organize things.

    Haha ! Same boat here !

    One slightly more stable system I’ve had for my own code is to use the Issues tracker as a sort of documentation storage system.

    That’s a very nice tip, thank you ! That’s something I will explore.

    Thanks for sharing. :) I hope you don’t mind me saying this but it’s nice to see commits like “Just a commit test”. I also have these as part of learning git.

    Yeah that’s a bit embarrassing 🫠 ! Was playing around with some script to convert Obsidian markdown links to GitHub flavored markdown. Because a comment is necessary to push the commit I have always no idea what to put in there xDD.

    Sorry I couldn’t help you out more and hope you will find a workflow that works for you ! 👍


  • Is there any specific reason to keep the docs in the wiki section? Vs markdown documents right in the wiki itself?

    I don’t know sorry :/ I do use a document but only because I want more control over the TOC (Table of content), which is a bit strange in the wiki itself, but that’s just personal taste !

    I’m not a Dev so take everything I say with a grain of salt, but what I would do is add a comment in the code to specify the change and link to your documentation file for more details (if needed). That’s probably one of the advantage of having your documentation not in the wiki page.

    This would keep your code page clean while having proper documtation in the same repo ! However, I have never seen any project doing it like that (for a good reason probably?).

    Here is my codeberg documentation repo about anime encoding in av1. It’s probably not what you’re looking for but maybe this can give you any idea or see if this could fit your workflow?


  • I will have forgotten a lot; it might be a different system environment. I need to be able to re-learn everything at a later time. Simple solutions that are widely-compatible, and do not rely on my memory are preferred.

    I don’t know if you have already considered it, but you can use a git repository as documentation tool ! It’s a GitHub flavored markdown syntax though.

    Fork the project, upload it to your own git repo (self-hosted codeberg, codeberg, github… Pick your poison :p) and add your own wiki documentation about your changes in the code.

    The only thing you should keep an eye on is probably the license? But I’m not the right person to discuss about licensing :/






  • N0x0n@lemmy.mltoAsklemmy@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    9
    ·
    edit-2
    15 days ago

    Sorry you getting down voted this much ! Your account is relatively new so I assume it’s your first time on Lemmy.

    While this is a relatively innocent question, Lemmy user base is mostly arround open source, alternatives, degoogling…

    Your question would probably be better in Apple/iPhone community rather in a more “global” community like asklemmy.

    Hope you will still enjoy your stay :)

    Edit: Also read the community info rules !