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

help-circle



  • Pyro@lemmy.worldtoProgramming@programming.devDead Man Switch
    link
    fedilink
    English
    arrow-up
    15
    ·
    3 months ago

    Thor from Pirate Software (a game studio) does this. He has his set up so that if he doesn’t log into a specific server for a year, the source code to his game will be automatically published.

    You could do the same thing. Just grab a super cheap server that checks the last login date and sends out emails.






  • Pyro@lemmy.worldtoProgrammer Humor@lemmy.mlHappened to me multiple times
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    4
    ·
    5 months ago

    I want to like Forgejo but the name is really terrible.

    Is it “forj-joe”? Nah, that double-J sound is way too awkward.
    Do you then merge the J sounds to make “forjo”? If so, why not just call it that?
    Is it maybe “for-geh-joe”? That seems the most likely to me, but then that ignores the “build < forge” marketing on their website.

    I know it’s pretty inconsequential, but it feels weird using a tool that you don’t even know how to pronounce the name of.






  • I would say finding that the bug is in a library is worse than finding it in your own code.

    If it’s your own code, you just fix it.

    If it’s in a library you then have to go and search for issues. If there isn’t one, you then go and spend time making one and potentially preparing a minimum reproducible example. Or if you don’t do that (or it’s just unmaintained) then you have to consider downgrading to a version that doesn’t have the bug and potentially losing functionality, or even switching to another library entirely and consequently rewriting all your code that used the old one to work with the new one.

    Yeah, I’d take my own bugs over library bugs any day.


  • Perhaps try making a simple web chat application. I recommend it for a myriad of reasons:

    • You’ll get to touch upon all the layers of a web app (DB/backend/frontend) in a manageably small way.
    • You’ll be able to make multiple choices to learn different technologies - like which database type to use (SQL/document), which message passing method to use (requests/sockets), which frontend framework to use (Solid/Svelte/HTMX/etc), and so on.
    • Getting a minimum working system is very fast. You can easily spend less than a day completing this, even as a novice.
    • Once completed, there are many extra goals you can set yourself. Try adding roles, commands, enable sending pictures, embedding metadata for links, etc. You need only look to your favourite chat app for your next idea!