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

help-circle






  • 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 :/


  • Back in the day, that’s what I did ALOT on Windows. Specially because of piracy and my younger me having no idea what he was doing XD !

    Still happens on Linux with EndeavourOS but not for the same reasons ! There are millions times more ways to break stuff on Linux but I always learn Something new during the process.

    Story time:

    Learned the other day that some config files are loaded in a specific order and depending what display manager is installed. That was kinda eye opening to understand cause my system didn’t load .profile when .bash_profile was present and I didn’t understood why ! Thanks Archwiki !








  • I’m not very acquainted with any programming language so maybe I’m wrong here (or I didn’t get the joke? XD) but bash didn’t change much in the past few years, I even read some scripts more than 10 years still works because the syntax stays the same (or doesn’t change a lot …)

    Compared with the switch from python 2 -> python 3 I read a lot of people pulling their hair off xD




  • The only thing I don’t install via that way is Firefox addons.

    Any specific reason why? Yesterday I installed LibreWolf and saw at the same time a few addons in the AUR.

    Do you know what’s the difference from an AUR addon or the official Firefox addon repo?

    I guess It would be for security reasons because you never know if someone has tempered with the addon.