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

help-circle
  • Pretty sure that you get the benefit of the doubt if you had a feasible reason for adding/changing something about your food.

    For example, you could add a laxative to your food/drink and be totally in the clear as long as you labelled your container with your name and maintain that you’ve been constipated. It’s a totally valid reason, plus it was labelled with your name so there’s no reason for anyone else to be consuming it.



  • Pyro@lemmy.worldtoLemmy Shitpost@lemmy.worldLay them on me
    link
    fedilink
    English
    arrow-up
    36
    ·
    6 months ago

    I think they were more likely referring to how when the public eye is on something many companies will start churning out low-effort products to capitalise on the interest. The market would be flooded with cheap and inferior products in that niche, potentially threatening the smaller business that actually cared about making quality products for those hobbyists. I know this won’t apply to every hobby, but there are definitely a number of them that will.













  • Pyro@lemmy.worldtoProgrammer Humor@lemmy.mlHappened to me multiple times
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    4
    ·
    8 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.