• 2 Posts
  • 81 Comments
Joined 2 years ago
cake
Cake day: February 19th, 2024

help-circle
  • The standard specify a ton features and formats. Thing like day if week so 2015-W4-1 would be the first day of the fourth week of 2015.

    But the you have can have periods like “P1Y2M10DT2H30M”, and you can specify start and end dates. So if you want to start an event that runs for 3 months, 20 days, and some time you could write it as “20220212T1133/P3M20DT7H15M”.

    And then there’s more like giving the year as an exponent, so 2015 can be written as Y-2.015E3S4.






  • I didn’t think much of what the “correct” location would be. But i have a general kinda everything share at /var/share/[music,books,video,user folders,repo]. And then any caching or config data sits in that dockers home folder under /etc/docker/[jellyfin,immich,kavita,etc] together with its docker-compose file. All docker services run under the group user so they all have access to the share.





  • i and I are acceptable in small loops. But it depends a lot on the language used. If you’re in C or bash maybe it’s fine. But if you’re in a higher level language like C# you usually have built on functions for iterating over something.

    For example you have a list of movies you want to get the rating from, instead of doing

    for (i = 0; i < movies.length; i++)
        var movie = movies[i]
        ....
    

    Its often more readable to do

    movies.forEach { movie -> 
        var rating = movie.rating
        ....
    }
    

    Also if you work with tables it can be very helpful to name your iteration variables as row and column.

    It’s all about making it readable, understandable, and correct. There’s no point having comments if you forget to update them when you change the code. And you better make sure the AI comments on the 2000 lines of three letter variables is correct!