• 0 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: July 21st, 2023

help-circle
  • I personally like to keep it on. Most of my messaging is with family and friends and it’s good to know if someone read or hasn’t read my message.

    Especially if things are time critical. Picking someone up? Asking if they need anything from the supermarket? If I see that they read the message I know that they are going to reply in a moment. If they didn’t even read the message I won’t have to wait around / can guess that they are currently in the car or wherever.

    Sometimes you also have a spotty connection, so the received + read receipt can tell you if they actually got your message.

    In general if someone sends me a message and I read it… I’m going to fucking reply to it (if I’m not super busy, and even then I might send a quick message back). I seriously don’t get people who just leave things on read and then forget about it.


  • But the NAS is in your house… which basically means if it gets flooded/burns down all your data is gone too.

    I already have my data on my PC, a second backup inside the same house isn’t worth that much. But instead of relying on a cloud service I just rent a virtual server (for various things) and use Seafile to keep my data in sync.

    PC breaks? House burns down? My data is on my own server in a datacenter. My server gets cancelled? My data is on my PCs.

    So even with your NAS you are 100% reliant on a cloud backup still, so why did you get the NAS when you already have a copy of your data on your devices?



  • Vlyn@lemmy.worldtoProgrammer Humor@lemmy.mlSounds great in theory
    link
    fedilink
    English
    arrow-up
    173
    arrow-down
    4
    ·
    11 months ago

    TDD is great when you have a very narrow use case, for example an algorithm. Where you already know beforehand: If I throw A in B should come out. If I throw B in C should come out. If I throw Z in an error should be thrown. And so on.

    For that it’s awesome, which is mostly algorithms.

    In real CRUD apps though? You have to write the actual implementation before the tests. Because in the tests you have to mock all the dependencies you used. Come up with fake test data. Mock functions from other classes you aren’t currently testing and so on. You could try TDD for this, but then you probably spend ten times longer writing and re-writing tests :-/

    After a while it boils down to: Small unit tests where they make sense. Then system wide integration tests for complex use-cases.




  • You don’t get it. Server settings are only one part of it, Discord also has their own account wide policies.

    For example I had a second account I used on Discord. Verified email, used it for years on and off every now and then. Last time I tried to login? No longer possible, I need to add a valid phone number and verify it. I couldn’t even get back into the account at all!

    No way around it, if Discord flags your account for whatever reason they log you out and force you to add a phone number. All it might take is you pressing logout once and next time you try to login you’re blocked. If even that.





  • It’s a language model, it can’t even do math reliably. Yes, it produces code that works sometimes, but it also hallucinates functions that don’t exist or can introduce bugs you won’t notice at first glance.

    And writing a script is different than extending an existing code base. How often do you really start a greenfield project?

    I wouldn’t even know how to input a code base into ChatGPT to extend, do you just throw in hundreds of files with a 100k+ lines of code?