• 0 Posts
  • 20 Comments
Joined 1 year ago
cake
Cake day: June 5th, 2023

help-circle
  • It was written as part of my work.

    check your contract, you might not own the code and your organization may have a process to determine how to license something.

    to your other questions (IANAL)

    1. prior work wont be licensed, meaning no one but the owner of the work is allowed to do anything with versions prior to the license
    2. you don’t have to, but i can’t see a reason why you should not.
    3. GPL might mean that other work depending on gpl licensed code has to be licensed in a gpl compatible way, depending on how exactly you depend on it and how you distribute your dependencies. MIT/BSD is easier here, if you don’t plan to license everything with the GPL anyway.



  • And no, I have not tested it because I don’t know how I’m actually supposed to do that.

    depends on what you backup and how.

    if it’s just “dumb” files (videos, music pictures etc.), just retrieve them from your backups and check if you can open the files.

    complex stuff? probably try to rebuild the complex stuff from a backup and check if it works as expected and is in the state you expect it to be in. how to do that really depends on the complex stuff.

    i’d guess for most people it’s enough to make sure to backup dumb files and configurations, so they can rebuild their stuff rather than being able to restore a complex system in exactly the same state it was in before bad things happened.



  • This is why i listen to audiobooks or radio plays to fall asleep to.

    They are engaging enough to stop the noise but i can still fall asleep listening.

    Works good for me, atleast most of the time*.

    *Damn you Will Patton for reading Stephen King novells in such a gripping way, you are banned from bedtime listening!


  • Most clients are web browsers and support for torrents in http is the same as for every other file.

    So that would only give us a use for torrents as a form of content distribution plattform to get the actual files closer to the client.

    In cases where we have actual non browser clients: i like to curate what i am distributing and don’t want to distribute anything i happen stumble upon or would you be willing to store and more importantly share everything you find on 4chan or that might show up in your mastodon feed?


  • I think i have roughly three categories for this.

    Needs: i need food/ my meds/ a train ticket to get to work

    Wants: stuff that i want for me beyond the needs, e.g. hobby stuff like a tripod if one is into photography or dinner in a nice restaurant from time to time

    Desires: stuff thats purely for pleasure. Like candy, or a new phone if the old one is still working or very expensive hobby related material, like that carbon tripod with all the bells and whistles, or material i allready own plenty of, like video games.

    Asking myself if something is still a want vs a desire stopped some impulse buys, but this desires very very tempting








  • Am a software developer, and in my experience we always find things that could be done different, spend hours tracking down the source of some fringe bug, or think of new features a product could benefit from, especially if we enjoy working on it.

    Things might be considered done, but i never was in a situation where one could not think of more things that could be done.



  • Best Love Letter version i have played so far.

    And it high jacked many board game nights, just because someone wanted to play “just another quick round”. The insanity mechanic really adds something.

    The only thing that sometimes annoys me is the high luck factor, but rounds are over so quick that a round lost to an unlucky insanity check or drawing cthulhu and the necronomicon at the same time is quickly forgotten.


  • I guess some lessons need to be learned through pain.

    • Commiting regulary.
    • Following the branch rules.
    • writing tests.
    • writing tests, that test the desired not the current behaviour
    • refactoring your code.
    • not refactoring code, you don’t understand nor have tests for.
    • actually reading code before merging a pr.
    • not pulling in 23 unmantained libraries to solve a simple problem.
    • keeping your dependencies up to date.
    • that dirty hack will make your life harder.

    Yes, all those hurt. They sometimes still do, most of us are not machines that turn caffeine into code and we are never as clever as we think we are.


  • https://jsommers.github.io/cbook/cbook.pdf

    Might be a good way for someone who is familiar with a higher level language.

    Than there is of course “The C Programming Language” by Ritchie and Kernighan and “advanced programming in the unix enviroment” by stevens and rago.

    So, i’d guess just get your feet wet with small stuff. Find out how to take arguments from the command line, or read a file, maybe programm a simple guess the number game. After you are more familiar with the syntax and so on you could look into using your c code in a higher level language. For python you’d have to look into ctypes for that.


  • Most of my coding happens on the monitor of an 15" thinkpad. No room for distracting stuff, atleast not visibly and missing emails or instant messages is way easier if they are just a single ping, thats drowned out by music, instead of a cascade of text scrolling by.

    The big monitor is for less focused work or the odd day i actually want to look at multiple things at once to find an odd quirk happening in a bigger system.